From: Prashant Malani <pmalani@google.com>
To: open list <linux-kernel@vger.kernel.org>,
"open list:CPU FREQUENCY SCALING FRAMEWORK"
<linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: Beata Michalska <beata.michalska@arm.com>,
Prashant Malani <pmalani@google.com>
Subject: [PATCH 0/2] cpufreq: CPPC: Avoid cur frequency modification on governor start
Date: Sat, 23 Aug 2025 00:17:46 +0000 [thread overview]
Message-ID: <20250823001937.2765316-1-pmalani@google.com> (raw)
This is a short series that handles an issue where, on CPPC-based systems,
the cpu frequency was getting unintentionally set to the wrong value on
governor start ( and overriding the existing policy frequency) because of
unreliable AMU/CPPC counters.
This adds a governor flag that avoids the check against the CPPC AMU-based
frequency when the governor starts. It then modifies the CPPC CPU freq
driver to opt in to using this flag.
Prashant Malani (2):
cpufreq: Add driver flag to avoid initial frequency verification
cpufreq: CPPC: Don't verify cur frequency on governor start
drivers/cpufreq/cppc_cpufreq.c | 3 ++-
drivers/cpufreq/cpufreq.c | 3 ++-
include/linux/cpufreq.h | 10 ++++++++++
3 files changed, 14 insertions(+), 2 deletions(-)
--
2.51.0.rc2.233.g662b1ed5c5-goog
next reply other threads:[~2025-08-23 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 0:17 Prashant Malani [this message]
2025-08-23 0:17 ` [PATCH 1/2] cpufreq: Add driver flag to avoid initial frequency verification Prashant Malani
2025-08-25 4:56 ` Viresh Kumar
2025-08-25 7:49 ` Beata Michalska
2025-08-23 0:17 ` [PATCH 2/2] cpufreq: CPPC: Don't verify cur frequency on governor start Prashant Malani
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=20250823001937.2765316-1-pmalani@google.com \
--to=pmalani@google.com \
--cc=beata.michalska@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.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®