[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9423f959-6d93-4908-ac2a-a9e23c69f2db@huawei.com>
Date: Thu, 16 Jan 2025 10:08:20 +0800
From: "zhenglifeng (A)" <zhenglifeng1@...wei.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>
CC: <viresh.kumar@...aro.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 0/2] cpufreq: Introduce a more generic way to boost when
cpu is going online
On 2025/1/15 20:53, Rafael J. Wysocki wrote:
> On Wed, Jan 15, 2025 at 11:01 AM Lifeng Zheng <zhenglifeng1@...wei.com> wrote:
>>
>> Since commit f37a4d6b4a2c ("cpufreq: Fix per-policy boost behavior on
>> SoCs using cpufreq_boost_set_sw()") and commit 102fa9c4b439 ("cpufreq:
>> Allow drivers to advertise boost enabled"), per-policy boost flag has
>> already been set to mirror the cpufreq_driver boost during
>> initialization. However, the current implementation doesn't work for all
>> cpufreq drivers and may fail in certain situation. A more generic
>> implementation is needed.
>
> Can you please be more specific here?
>
> What happens, why it happens and why do you think the way to go is to
> reimplement this?
I've explained this in commit log of patch 2. But if you think it is better
to palce here too, I'll do that in v2.
Powered by blists - more mailing lists