From: Mario Limonciello <mario.limonciello@amd.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>
Subject: amd-pstate fixes for 6.13 (12/11/24)
Date: Wed, 11 Dec 2024 11:25:01 -0600 [thread overview]
Message-ID: <63f03935-a73c-45f2-b152-29d08cb300b5@amd.com> (raw)
Hi,
The following changes since commit
fac04efc5c793dccbd07e2d59af9f90b7fc0dca4:
Linux 6.13-rc2 (2024-12-08 14:03:39 -0800)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git
tags/amd-pstate-v6.13-2024-12-11
for you to fetch changes up to 2993b29b2a98f2bc9d55dfd37ef39f56a2908748:
cpufreq/amd-pstate: Use boost numerator for upper bound of
frequencies (2024-12-10 10:17:43 -0600)
----------------------------------------------------------------
Fix a problem where systems without preferred cores were
misdetecting preferred cores.
Fix issues with with boost numerator handling leading to
inconsistently programmed CPPC max performance values.
----------------------------------------------------------------
K Prateek Nayak (1):
cpufreq/amd-pstate: Detect preferred core support before driver
registration
Mario Limonciello (2):
cpufreq/amd-pstate: Store the boost numerator as highest perf
again
cpufreq/amd-pstate: Use boost numerator for upper bound of
frequencies
Documentation/admin-guide/pm/amd-pstate.rst | 4 +---
drivers/cpufreq/amd-pstate.c | 50
++++++++++++++++++++++++++------------------------
2 files changed, 27 insertions(+), 27 deletions(-)
next reply other threads:[~2024-12-11 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 17:25 Mario Limonciello [this message]
2024-12-18 14:46 ` amd-pstate fixes for 6.13 (12/11/24) Rafael J. Wysocki
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=63f03935-a73c-45f2-b152-29d08cb300b5@amd.com \
--to=mario.limonciello@amd.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.