From: Pierre Gondois <pierre.gondois@arm.com>
To: "zhenglifeng (A)" <zhenglifeng1@huawei.com>,
linux-kernel@vger.kernel.org
Cc: Jie Zhan <zhanjie9@hisilicon.com>,
Ionela Voinescu <ionela.voinescu@arm.com>,
Christian Loehle <christian.loehle@arm.com>,
sumitg@nvidia.com, "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.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>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@kernel.org>,
Saravana Kannan <saravanak@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 3/6] cpufreq: Centralize boost freq QoS requests
Date: Thu, 5 Feb 2026 14:58:46 +0100 [thread overview]
Message-ID: <12bcfd60-63f5-4804-b40f-b87ec1a8439e@arm.com> (raw)
In-Reply-To: <5cbc4987-f2b5-4dc4-8b90-c7aca60e6574@huawei.com>
On 1/31/26 05:11, zhenglifeng (A) wrote:
> On 2026/1/26 18:18, Pierre Gondois wrote:
>> policy_set_boost() calls the cpufreq set_boost callback.
>> Update the newly added boost_freq_req request from there:
>> - whenever boost is toggled
>> - to cover all possible paths
>>
>> Signed-off-by: Pierre Gondois<pierre.gondois@arm.com>
>> ---
>> drivers/cpufreq/cpufreq.c | 13 +++++++++++--
>> 1 file changed, 11 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
>> index c8fb4c6656e94..505da5b00e575 100644
>> --- a/drivers/cpufreq/cpufreq.c
>> +++ b/drivers/cpufreq/cpufreq.c
>> @@ -603,10 +603,19 @@ static int policy_set_boost(struct cpufreq_policy *policy, bool enable)
>> policy->boost_enabled = enable;
>>
>> ret = cpufreq_driver->set_boost(policy, enable);
>> - if (ret)
>> + if (ret) {
>> policy->boost_enabled = !policy->boost_enabled;
>> + return ret;
>> + }
>>
>> - return ret;
>> + ret = freq_qos_update_request(policy->boost_freq_req, policy->cpuinfo.max_freq);
>> + if (ret < 0) {
>> + policy->boost_enabled = !policy->boost_enabled;
>> + cpufreq_driver->set_boost(policy, !policy->boost_enabled);
> !policy->boost_enabled twice.
Yes indeed.
next prev parent reply other threads:[~2026-02-05 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 10:18 [PATCH 0/6] cpufreq: Introduce boost frequency QoS Pierre Gondois
2026-01-26 10:18 ` [PATCH 1/6] cpufreq: Remove per-CPU QoS constraint Pierre Gondois
2026-01-31 3:28 ` zhenglifeng (A)
2026-02-05 13:59 ` Pierre Gondois
2026-02-06 7:17 ` zhenglifeng (A)
2026-01-26 10:18 ` [PATCH 2/6] cpufreq: Add boost_freq_req QoS request Pierre Gondois
2026-01-31 4:00 ` zhenglifeng (A)
2026-02-05 13:58 ` Pierre Gondois
2026-01-26 10:18 ` [PATCH 3/6] cpufreq: Centralize boost freq QoS requests Pierre Gondois
2026-01-31 4:11 ` zhenglifeng (A)
2026-02-05 13:58 ` Pierre Gondois [this message]
2026-01-26 10:18 ` [PATCH 4/6] cpufreq: Update .set_boost() callbacks to rely on boost_freq_req Pierre Gondois
2026-01-26 10:18 ` [PATCH 5/6] cpufreq: Set policy->min and max as real QoS constraints Pierre Gondois
2026-01-29 6:02 ` kernel test robot
2026-01-29 9:52 ` kernel test robot
2026-01-26 10:18 ` [RFC PATCH 6/6] cpufreq/freq_table: Allow decreasing cpuinfo.max_freq Pierre Gondois
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=12bcfd60-63f5-4804-b40f-b87ec1a8439e@arm.com \
--to=pierre.gondois@arm.com \
--cc=christian.loehle@arm.com \
--cc=gautham.shenoy@amd.com \
--cc=ionela.voinescu@arm.com \
--cc=lenb@kernel.org \
--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=saravanak@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=sumitg@nvidia.com \
--cc=viresh.kumar@linaro.org \
--cc=zhanjie9@hisilicon.com \
--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
all inboxes | Powered by JetHome®