[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gPMGg2ZvjOmvmfj9W6L9wKT2+ToFgDpi-1pcg_zc+Z2g@mail.gmail.com>
Date: Wed, 15 Jan 2025 13:53:03 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Lifeng Zheng <zhenglifeng1@...wei.com>
Cc: rafael@...nel.org, 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 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?
Powered by blists - more mailing lists