From: Pierre Gondois <pierre.gondois@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-kernel@vger.kernel.org, Jie Zhan <zhanjie9@hisilicon.com>,
Lifeng Zheng <zhenglifeng1@huawei.com>,
Ionela Voinescu <ionela.voinescu@arm.com>,
Sumit Gupta <sumitg@nvidia.com>,
Christian Loehle <christian.loehle@arm.com>,
"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>,
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 v5 3/6] cpufreq: Centralize boost freq QoS requests
Date: Tue, 17 Mar 2026 11:28:41 +0100 [thread overview]
Message-ID: <29045913-845b-4e04-aea3-3d680d456ceb@arm.com> (raw)
In-Reply-To: <uggew5u2bjhgfxt5tlt3bjqg7aks7oab3iqnlayol2f26otchn@2xlt74ywbln4>
On 3/13/26 10:22, Viresh Kumar wrote:
> On 25-02-26, 09:49, 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 50467b938668a..42de32488f422 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);
>> + return ret;
>> + }
>> +
>> + return 0;
> This can be:
>
> return ret;
Actually the caller expects 0 for success and
freq_qos_update_request() can return a positive value for success, so
the code above should be used I think.
> and you can then drop 'return ret' from the if block.
>
> And yes, merge with prev patch as Rafael suggested.
>
next prev parent reply other threads:[~2026-03-17 10:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 8:49 [PATCH v5 0/6] cpufreq: Introduce boost frequency QoS Pierre Gondois
2026-02-25 8:49 ` [PATCH v5 1/6] cpufreq: Remove per-CPU QoS constraint Pierre Gondois
2026-03-13 8:57 ` Viresh Kumar
2026-03-13 14:28 ` Pierre Gondois
2026-03-16 14:45 ` Pierre Gondois
2026-03-16 19:25 ` Rafael J. Wysocki
2026-03-17 8:42 ` zhenglifeng (A)
2026-02-25 8:49 ` [PATCH v5 2/6] cpufreq: Add boost_freq_req QoS request Pierre Gondois
2026-03-11 13:52 ` Rafael J. Wysocki
2026-03-11 13:57 ` Rafael J. Wysocki
2026-03-13 14:28 ` Pierre Gondois
2026-03-13 15:31 ` Rafael J. Wysocki
2026-03-13 15:33 ` Pierre Gondois
2026-03-13 9:17 ` Viresh Kumar
2026-02-25 8:49 ` [PATCH v5 3/6] cpufreq: Centralize boost freq QoS requests Pierre Gondois
2026-03-11 16:11 ` Rafael J. Wysocki
2026-03-13 9:22 ` Viresh Kumar
2026-03-13 14:28 ` Pierre Gondois
2026-03-17 10:28 ` Pierre Gondois [this message]
2026-02-25 8:49 ` [PATCH v5 4/6] cpufreq: Update .set_boost() callbacks to rely on boost_freq_req Pierre Gondois
2026-03-11 16:19 ` Rafael J. Wysocki
2026-03-13 9:38 ` Viresh Kumar
2026-03-13 11:43 ` Rafael J. Wysocki
2026-03-13 14:28 ` Pierre Gondois
2026-02-25 8:49 ` [PATCH v5 5/6] cpufreq: Set policy->min and max as real QoS constraints Pierre Gondois
2026-02-25 8:49 ` [RFC PATCH v5 6/6] cpufreq/freq_table: Allow decreasing cpuinfo.max_freq Pierre Gondois
2026-03-11 16:24 ` Rafael J. Wysocki
2026-03-13 14:28 ` Pierre Gondois
2026-03-13 8:13 ` [PATCH v5 0/6] cpufreq: Introduce boost frequency QoS Viresh Kumar
2026-03-13 14:27 ` 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=29045913-845b-4e04-aea3-3d680d456ceb@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