From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Huang Rui <ray.huang@amd.com>,
"Gautham R. Shenoy" <gautham.shenoy@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Perry Yuan <perry.yuan@amd.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Lifeng Zheng <zhenglifeng1@huawei.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 05/15] cpufreq: amd: Set policy->boost_supported
Date: Fri, 24 Jan 2025 14:28:09 +0530 [thread overview]
Message-ID: <e16c06d4b8ffdb20e802ffe648f14dc515e60426.1737707712.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1737707712.git.viresh.kumar@linaro.org>
With a later commit, the cpufreq core will call the ->set_boost()
callback only if the policy supports boost frequency. The
boost_supported flag is set by the cpufreq core if policy->freq_table is
set and one or more boost frequencies are present.
For other drivers, the flag must be set explicitly.
The policy->boost_enabled flag is set by the cpufreq core once the
policy is initialized, don't set it anymore.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
drivers/cpufreq/amd-pstate.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
index d7630bab2516..8d3cc494c92c 100644
--- a/drivers/cpufreq/amd-pstate.c
+++ b/drivers/cpufreq/amd-pstate.c
@@ -995,7 +995,7 @@ static int amd_pstate_cpu_init(struct cpufreq_policy *policy)
policy->cpuinfo.min_freq = min_freq;
policy->cpuinfo.max_freq = max_freq;
- policy->boost_enabled = READ_ONCE(cpudata->boost_supported);
+ policy->boost_supported = READ_ONCE(cpudata->boost_supported);
/* It will be updated by governor */
policy->cur = policy->cpuinfo.min_freq;
@@ -1480,7 +1480,7 @@ static int amd_pstate_epp_cpu_init(struct cpufreq_policy *policy)
policy->min = policy->cpuinfo.min_freq;
policy->max = policy->cpuinfo.max_freq;
- policy->boost_enabled = READ_ONCE(cpudata->boost_supported);
+ policy->boost_supported = READ_ONCE(cpudata->boost_supported);
/*
* Set the policy to provide a valid fallback value in case
--
2.31.1.272.g89b43f80a514
next prev parent reply other threads:[~2025-01-24 8:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 8:58 [PATCH 00/15] cpufreq: simplify boost handling Viresh Kumar
2025-01-24 8:58 ` [PATCH 01/15] cpufreq: staticize cpufreq_boost_trigger_state() Viresh Kumar
2025-01-24 8:58 ` [PATCH 02/15] cpufreq: Export cpufreq_boost_set_sw() Viresh Kumar
2025-01-24 8:58 ` [PATCH 03/15] cpufreq: Introduce policy->boost_supported flag Viresh Kumar
2025-01-24 8:58 ` [PATCH 04/15] cpufreq: acpi: Set policy->boost_supported Viresh Kumar
2025-01-24 8:58 ` Viresh Kumar [this message]
2025-01-30 9:15 ` [PATCH 05/15] cpufreq: amd: " Dhananjay Ugwekar
2025-01-24 8:58 ` [PATCH 06/15] cpufreq: cppc: " Viresh Kumar
2025-02-06 3:58 ` zhenglifeng (A)
2025-02-06 5:27 ` Viresh Kumar
2025-02-06 6:27 ` zhenglifeng (A)
2025-01-24 8:58 ` [PATCH 07/15] cpufreq: Restrict enabling boost on policies with no boost frequencies Viresh Kumar
2025-01-24 8:58 ` [PATCH 08/15] cpufreq: apple: Set .set_boost directly Viresh Kumar
2025-01-24 8:58 ` [PATCH 09/15] cpufreq: loongson: " Viresh Kumar
2025-01-24 8:58 ` [PATCH 10/15] cpufreq: powernv: " Viresh Kumar
2025-01-24 8:58 ` [PATCH 11/15] cpufreq: scmi: " Viresh Kumar
2025-01-28 11:27 ` Sudeep Holla
2025-01-24 8:58 ` [PATCH 12/15] cpufreq: dt: " Viresh Kumar
2025-01-24 8:58 ` [PATCH 13/15] cpufreq: qcom: " Viresh Kumar
2025-01-24 8:58 ` [PATCH 14/15] cpufreq: staticize policy_has_boost_freq() Viresh Kumar
2025-01-24 8:58 ` [PATCH 15/15] cpufreq: Remove cpufreq_enable_boost_support() Viresh Kumar
2025-01-24 11:05 ` [PATCH 00/15] cpufreq: simplify boost handling Rafael J. Wysocki
2025-01-27 3:32 ` Viresh Kumar
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=e16c06d4b8ffdb20e802ffe648f14dc515e60426.1737707712.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perry.yuan@amd.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=vincent.guittot@linaro.org \
--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