From: Sudeep Holla <sudeep.holla@kernel.org>
To: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Sudeep Holla <sudeep.holla@kernel.org>,
acpica-devel@lists.linux.dev,
"Rafael J . Wysocki" <rafael@kernel.org>,
Saket Dumbre <saket.dumbre@intel.com>
Subject: [PATCH 0/4] ACPI/PCC: Correct PCC OperationRegion handling
Date: Fri, 17 Jul 2026 09:10:01 +0100 [thread overview]
Message-ID: <20260717081005.470013-1-sudeep.holla@kernel.org> (raw)
Hi,
This series corrects the handling of PCC OperationRegions and their
shared memory.
ACPI 6.3 states that a PCC OperationRegion describes the shared memory
following the PCC signature. Consequently, COMMAND fields at raw shared
memory offsets 4 and 12 appear at OperationRegion offsets 0 and 8.
The first patch corrects those offsets in ACPICA. This change has already
been submitted upstream:
https://github.com/acpica/acpica/pull/1205
The ACPICA patch is included here only to document the complete
dependency and aid review and testing. It must enter the kernel through
the ACPICA pull/import process and will not be merged directly through
the Linux ACPI tree.
The remaining Linux patches:
- Preserve the platform-populated PCC signature when copying
OperationRegion data.
- Release the mailbox channel and region context when ACPICA
deactivates an OperationRegion.
- Compute and cache the command timeout during channel setup.
There is no strict build dependency in case ACPICA and other 3 changes
need to be merged at different timeline or via different branch.
Regards,
Sudeep
Sudeep Holla (4):
ACPICA: Fix PCC OperationRegion command offsets
ACPI: PCC: Preserve shared memory signature in OpRegion handler
ACPI: PCC: Free channel on OpRegion deactivation
ACPI: PCC: Cache OpRegion command timeout
drivers/acpi/acpi_pcc.c | 55 ++++++++++++++++++++++++++---------
drivers/acpi/acpica/exfield.c | 11 +++----
2 files changed, 48 insertions(+), 18 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-17 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 8:10 Sudeep Holla [this message]
2026-07-17 8:10 ` [PATCH 1/4] ACPICA: Fix PCC OperationRegion command offsets Sudeep Holla
2026-07-17 8:10 ` [PATCH 2/4] ACPI: PCC: Preserve shared memory signature in OpRegion handler Sudeep Holla
2026-07-17 8:10 ` [PATCH 3/4] ACPI: PCC: Free channel on OpRegion deactivation Sudeep Holla
2026-07-17 8:10 ` [PATCH 4/4] ACPI: PCC: Cache OpRegion command timeout Sudeep Holla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260717081005.470013-1-sudeep.holla@kernel.org \
--to=sudeep.holla@kernel.org \
--cc=acpica-devel@lists.linux.dev \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=saket.dumbre@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox