summaryrefslogtreecommitdiff
path: root/include/uapi/linux
diff options
context:
space:
mode:
authorSudeep Holla <sudeep.holla@kernel.org>2026-09-22 15:42:59 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2026-09-25 18:08:21 +0200
commit888dab4b04ea8725168c6d50d0bfb8057fccca18 (patch)
treefd32ecd41076d241df562bf3716b16becc0b1c45 /include/uapi/linux
parentdbb3d99ee95c32711950850ddd33eb22a6042eb2 (diff)
downloadlinux-next-888dab4b04ea8725168c6d50d0bfb8057fccca18.tar.gz
linux-next-888dab4b04ea8725168c6d50d0bfb8057fccca18.zip
ACPICA: Fix PCC OperationRegion command offsets
ACPI 6.3, section 5.5.2.4.7.3, states that the PCC Operation Region is associated with the region of shared memory that follows the PCC signature. The generic and extended PCC shared memory layouts include the 4-byte signature at offset 0, so their raw shared memory COMMAND fields are at offsets 4 and 12 respectively. Since AML field offsets for the PCC OperationRegion are relative to the region after that signature, ACPICA must look for those COMMAND fields at OperationRegion offsets 0 and 8. Adjust the generic and master subspace command checks to use those OperationRegion-relative offsets. Otherwise writes to the COMMAND field can fail to invoke the PCC address space handler at the offset described by the PCC OperationRegion definition. Link: https://github.com/open-acpica/acpica/pull/1205 Fixes: aa6ec56b574d ("ACPICA: ACPI 6.3: add PCC operation region support for AML interpreter") Signed-off-by: Sudeep Holla <sudeep.holla@kernel.org> [ rjw: Fixed the Fixes: tag ] Link: https://patch.msgid.link/20260922144302.3847593-2-sudeep.holla@kernel.org Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'include/uapi/linux')
0 files changed, 0 insertions, 0 deletions