From: Sumit Gupta <sumitg@nvidia.com>
To: <rafael@kernel.org>, <viresh.kumar@linaro.org>,
<pierre.gondois@arm.com>, <christian.loehle@arm.com>,
<ionela.voinescu@arm.com>, <zhenglifeng1@huawei.com>,
<zhanjie9@hisilicon.com>, <lenb@kernel.org>, <ray.huang@amd.com>,
<mario.limonciello@amd.com>, <perry.yuan@amd.com>,
<kprateek.nayak@amd.com>, <maciej.wieczor-retman@intel.com>,
<pawel.chmielewski@intel.com>, <linux-pm@vger.kernel.org>,
<linux-acpi@vger.kernel.org>, <acpica-devel@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>
Cc: <treding@nvidia.com>, <jonathanh@nvidia.com>, <vsethi@nvidia.com>,
<ksitaraman@nvidia.com>, <sanjayc@nvidia.com>, <mochs@nvidia.com>,
<bbasu@nvidia.com>, <sumitg@nvidia.com>
Subject: [PATCH v10 0/3] ACPI / cpufreq: CPPC: Add ospm_nominal_perf support
Date: Tue, 10 Nov 2026 01:23:57 +0530 [thread overview]
Message-ID: <20261109195400.3600561-1-sumitg@nvidia.com> (raw)
This series adds support for the OSPM Nominal Performance register
(ACPI 6.6, Section 8.4.6.1.2.6) to the CPPC ACPI and cpufreq drivers.
Unlike the read-only Nominal Performance register, OSPM Nominal
Performance is writable and lets OSPM request a nominal level below
the platform-reported nominal. The platform treats performance above
this level as boost and below as throttle.
- Patch 1: adds ACPI helpers to write the register and to check that
the platform supports it.
- Patch 2: adds the per-policy ospm_nominal_freq attribute in kHz. The
value is kept across CPU hotplug and suspend/resume. The register
cannot be read back, so a read returns the last value written.
- Patch 3: uses the OSPM nominal as the maximum frequency while boost
is off. Lowering the nominal creates a boost range on a platform
that has none, and boost can then be enabled.
These are patches 6-8 of v9. Patches 1-5 of v9 are queued in for 7.5,
and this series applies on top of them.
v9 -> v10:
- Drop v9 patches 1-5, as they are queued for 7.5.
- Patch 1: when the register shares an access unit with Performance
Limited, keep it reserved in the SystemMemory overlap validation, as
it is write-only. (Sashiko)
Sumit Gupta (3):
ACPI: CPPC: Add ospm_nominal_perf support
cpufreq: CPPC: Add ospm_nominal_freq attribute
cpufreq: CPPC: Reflect the OSPM nominal in boost and limits
.../ABI/testing/sysfs-devices-system-cpu | 31 ++++
drivers/acpi/cppc_acpi.c | 56 ++++++
drivers/cpufreq/cppc_cpufreq.c | 173 +++++++++++++++++-
include/acpi/cppc_acpi.h | 10 +
4 files changed, 260 insertions(+), 10 deletions(-)
v8: https://lore.kernel.org/lkml/20261030172745.2045743-1-sumitg@nvidia.com/
v9: https://lore.kernel.org/lkml/20261106193304.3347374-1-sumitg@nvidia.com/
base-commit: 22f2a52b46d52df66cf0a5efe4d22296810cbcee
--
2.34.1
next reply other threads:[~2026-11-09 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 19:53 Sumit Gupta [this message]
2026-11-09 19:53 ` [PATCH v10 1/3] ACPI: " Sumit Gupta
2026-11-09 19:53 ` [PATCH v10 2/3] cpufreq: CPPC: Add ospm_nominal_freq attribute Sumit Gupta
2026-11-09 20:13 ` [PATCH v10 3/3] cpufreq: CPPC: Reflect the OSPM nominal in boost and limits Sumit Gupta
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=20261109195400.3600561-1-sumitg@nvidia.com \
--to=sumitg@nvidia.com \
--cc=acpica-devel@lists.linux.dev \
--cc=bbasu@nvidia.com \
--cc=christian.loehle@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=jonathanh@nvidia.com \
--cc=kprateek.nayak@amd.com \
--cc=ksitaraman@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=mario.limonciello@amd.com \
--cc=mochs@nvidia.com \
--cc=pawel.chmielewski@intel.com \
--cc=perry.yuan@amd.com \
--cc=pierre.gondois@arm.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=sanjayc@nvidia.com \
--cc=treding@nvidia.com \
--cc=viresh.kumar@linaro.org \
--cc=vsethi@nvidia.com \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@huawei.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
all inboxes | Powered by JetHome®