From: Mario Limonciello <mario.limonciello@amd.com>
To: "Rafael J . Wysocki" <rafael@kernel.org>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-pm@vger.kernel.org>,
K Prateek Nayak <kprateek.nayak@amd.com>, <x86@kernel.org>,
Vishal Badole <Vishal.Badole@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH 0/3] Zen6 client CPPC
Date: Mon, 31 Aug 2026 14:44:25 -0500 [thread overview]
Message-ID: <20260831194428.2287055-1-mario.limonciello@amd.com> (raw)
Zen6 client platforms use CPPC differently than previous platforms
and knowing maximum frequency for a core type is needed for capacity
calculations.
Newer versions of the ACPI will introduce a proper interface
for getting this information, but for now hardcode values so that
these systems perform as intended and to unblock future scheduler
work while we continue to wait.
Mario Limonciello (3):
ACPI: CPPC: Refactor boost ratio handling
cpufreq/acpi-cpufreq: Use amd_get_boost_ratio()
cpufreq/amd-pstate: Get Highest Freq for a CPU
arch/x86/kernel/acpi/cppc.c | 174 ++++++++++++++++++++++-----------
drivers/cpufreq/acpi-cpufreq.c | 17 ++--
drivers/cpufreq/amd-pstate.c | 22 +++--
include/acpi/cppc_acpi.h | 14 ++-
4 files changed, 154 insertions(+), 73 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-31 19:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 19:44 Mario Limonciello [this message]
2026-08-31 19:44 ` [PATCH 1/3] ACPI: CPPC: Refactor boost ratio handling Mario Limonciello
2026-09-01 4:41 ` K Prateek Nayak
2026-09-01 15:26 ` Mario Limonciello
2026-09-01 9:31 ` K Prateek Nayak
2026-09-01 15:28 ` Mario Limonciello
2026-09-01 16:34 ` Rafael J. Wysocki (Intel)
2026-09-01 16:44 ` Mario Limonciello
2026-08-31 19:44 ` [PATCH 2/3] cpufreq/acpi-cpufreq: Use amd_get_boost_ratio() Mario Limonciello
2026-08-31 19:44 ` [PATCH 3/3] cpufreq/amd-pstate: Get Highest Freq for a CPU Mario Limonciello
2026-09-01 9:36 ` [PATCH 0/3] Zen6 client CPPC K Prateek Nayak
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=20260831194428.2287055-1-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=Vishal.Badole@amd.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=x86@kernel.org \
/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).