From: Pierre Gondois <pierre.gondois@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-kernel@vger.kernel.org,
Christian Loehle <christian.loehle@arm.com>,
Ionela Voinescu <ionela.voinescu@arm.com>,
zhenglifeng1@huawei.com, Jie Zhan <zhanjie9@hisilicon.com>,
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>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 2/3] cpufreq: Centralize boost freq QoS requests
Date: Mon, 12 Jan 2026 16:04:14 +0100 [thread overview]
Message-ID: <5beee62b-7b96-4a0e-b85c-400246256aa6@arm.com> (raw)
In-Reply-To: <p4t3tvjiew7hmeibwz36h6htt3kkpv5c44b3thcdygltatubsa@jxjwycjzbnyt>
On 1/8/26 06:10, Viresh Kumar wrote:
> On 08-12-25, 11:59, 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 | 12 ++++++++++--
>> 1 file changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
>> index 942416f2741b0..65ef0fa70c388 100644
>> --- a/drivers/cpufreq/cpufreq.c
>> +++ b/drivers/cpufreq/cpufreq.c
>> @@ -603,10 +603,18 @@ 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;
> what about calling set_boost() as well on failure to reverse prev change ?
Yes right indeed
>
>> + return ret;
>> + }
>> +
>> + return 0;
>> }
>>
>> static ssize_t store_local_boost(struct cpufreq_policy *policy,
>> --
>> 2.43.0
next prev parent reply other threads:[~2026-01-12 15:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 10:59 [PATCH v2 0/3] cpufreq: Introduce boot frequency QoS Pierre Gondois
2025-12-08 10:59 ` [PATCH v2 1/3] cpufreq: Add boost_freq_req QoS request Pierre Gondois
2025-12-10 3:01 ` zhenglifeng (A)
2025-12-17 16:21 ` Pierre Gondois
2025-12-08 10:59 ` [PATCH v2 2/3] cpufreq: Centralize boost freq QoS requests Pierre Gondois
2026-01-08 5:10 ` Viresh Kumar
2026-01-12 15:04 ` Pierre Gondois [this message]
2025-12-08 10:59 ` [PATCH v2 3/3] cpufreq: Update set_boost callbacks to rely on boost_freq_req Pierre Gondois
2025-12-10 9:26 ` zhenglifeng (A)
2025-12-17 16:22 ` Pierre Gondois
2025-12-20 10:29 ` zhenglifeng (A)
2025-12-23 8:15 ` zhenglifeng (A)
2026-01-12 15:02 ` Pierre Gondois
2026-01-13 1:30 ` Viresh Kumar
2026-01-13 12:20 ` Rafael J. Wysocki
2026-01-15 3:41 ` zhenglifeng (A)
2026-01-08 4:37 ` [PATCH v2 0/3] cpufreq: Introduce boot frequency QoS 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=5beee62b-7b96-4a0e-b85c-400246256aa6@arm.com \
--to=pierre.gondois@arm.com \
--cc=christian.loehle@arm.com \
--cc=gautham.shenoy@amd.com \
--cc=ionela.voinescu@arm.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=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®