From: "Mario Limonciello (AMD)" <superm1@kernel.org>
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, Mario Limonciello <superm1@kernel.org>
Subject: [PATCH v3 0/3] Zen6 client CPPC
Date: Thu, 24 Sep 2026 11:00:49 -0500 [thread overview]
Message-ID: <20260924160052.2858456-1-superm1@kernel.org> (raw)
From: Mario Limonciello <superm1@kernel.org>
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.
v3:
* rebase on linux-pm/bleeding-edge to pick up
"ACPI: CPPC: Fix register access and lifetime bugs"
v2:
Link: https://lore.kernel.org/linux-pm/20260901215913.3042182-1-mario.limonciello@amd.com/
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 | 166 ++++++++++++++++++++++-----------
drivers/cpufreq/acpi-cpufreq.c | 17 ++--
drivers/cpufreq/amd-pstate.c | 20 ++--
include/acpi/cppc_acpi.h | 14 ++-
4 files changed, 143 insertions(+), 74 deletions(-)
--
2.53.0
next reply other threads:[~2026-09-24 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 16:00 Mario Limonciello (AMD) [this message]
2026-09-24 16:00 ` [PATCH v3 1/3] ACPI: CPPC: Refactor boost ratio handling Mario Limonciello (AMD)
2026-09-24 16:00 ` [PATCH v3 2/3] cpufreq/acpi-cpufreq: Use amd_get_boost_ratio() Mario Limonciello (AMD)
2026-09-24 16:00 ` [PATCH v3 3/3] cpufreq/amd-pstate: Get Highest Freq for a CPU Mario Limonciello (AMD)
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=20260924160052.2858456-1-superm1@kernel.org \
--to=superm1@kernel.org \
--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
all inboxes | Powered by JetHome®