From: Sudeep Holla <sudeep.holla@arm.com>
To: Robert Moore <robert.moore@intel.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
devel@acpica.org
Subject: [PATCH 0/3] ACPI: Add support for PCC Operation Region
Date: Tue, 2 Nov 2021 18:25:39 +0000 [thread overview]
Message-ID: <20211102182542.3460787-1-sudeep.holla@arm.com> (raw)
Hi,
This series adds support for ACPI PCC OpRegion added in ACPI 6.3
I understand that the ACPICA changes need to go via different route,
but I am posting it together to give complete narative/picture for
the review/discussion.
Regards,
Sudeep
Sudeep Holla (3):
ACPICA: Fix wrong interpretation of PCC address
ACPICA: Add support for PCC Opregion special context data
ACPI: PCC: Implement OperationRegion handler for the PCC Type 3 subtype
drivers/acpi/Kconfig | 5 ++
drivers/acpi/Makefile | 1 +
drivers/acpi/acpica/evregion.c | 11 ++++
drivers/acpi/acpica/exfield.c | 7 +--
drivers/acpi/bus.c | 1 +
drivers/acpi/pcc_opregion.c | 111 +++++++++++++++++++++++++++++++++
include/acpi/actypes.h | 8 +++
include/linux/acpi.h | 6 ++
8 files changed, 144 insertions(+), 6 deletions(-)
create mode 100644 drivers/acpi/pcc_opregion.c
--
2.25.1
next reply other threads:[~2021-11-02 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 18:25 Sudeep Holla [this message]
2021-11-02 18:25 ` [PATCH 1/3] ACPICA: Fix wrong interpretation of PCC address Sudeep Holla
2021-11-02 18:25 ` [PATCH 2/3] ACPICA: Add support for PCC Opregion special context data Sudeep Holla
2021-11-02 18:25 ` [PATCH 3/3] ACPI: PCC: Implement OperationRegion handler for the PCC Type 3 subtype Sudeep Holla
2021-11-05 14:58 ` [PATCH 0/3] ACPI: Add support for PCC Operation Region Rafael J. Wysocki
2021-11-22 17:59 ` 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=20211102182542.3460787-1-sudeep.holla@arm.com \
--to=sudeep.holla@arm.com \
--cc=devel@acpica.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robert.moore@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;
as well as URLs for NNTP newsgroup(s).