[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f9433f1-a826-4198-b4aa-9089f566916f@huawei.com>
Date: Tue, 21 Jan 2025 14:22:59 +0800
From: "zhenglifeng (A)" <zhenglifeng1@...wei.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
CC: <rafael@...nel.org>, <linux-pm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linuxarm@...wei.com>,
<jonathan.cameron@...wei.com>, <zhanjie9@...ilicon.com>,
<lihuisong@...wei.com>, <fanghao11@...wei.com>
Subject: Re: [PATCH v2 2/4] cpufreq: Introduce a more generic way to set
default per-policy boost flag
On 2025/1/21 12:20, Viresh Kumar wrote:
> On 21-01-25, 09:45, zhenglifeng (A) wrote:
>> On 2025/1/20 17:01, Viresh Kumar wrote:
>>> On 17-01-25, 18:14, Lifeng Zheng wrote:
>>>> + /* Let the per-policy boost flag mirror the cpufreq_driver boost during init */
>>>> + if (policy->boost_enabled != cpufreq_boost_enabled()) {
>>>> + policy->boost_enabled = cpufreq_boost_enabled();
>>>> + ret = cpufreq_driver->set_boost(policy, policy->boost_enabled);
>>>
>>> I though you agreed to do some optimization here ?
>>
>> Sorry. Do I miss something here?
>
> https://lore.kernel.org/all/17c7ed77-21f1-4093-91fc-f3eaa863d312@huawei.com/
>
I think I already done that, isn't it?
Powered by blists - more mailing lists