[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240228050703.lixqywrtxravegc6@vireshk-i7>
Date: Wed, 28 Feb 2024 10:37:03 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Sibi Sankar <quic_sibis@...cinc.com>
Cc: dietmar.eggemann@....com, marcan@...can.st, sven@...npeter.dev,
alyssa@...enzweig.io, rafael@...nel.org, xuwei5@...ilicon.com,
zhanjie9@...ilicon.com, sudeep.holla@....com,
cristian.marussi@....com, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, quic_rgottimu@...cinc.com,
linux-arm-kernel@...ts.infradead.org, asahi@...ts.linux.dev,
linux-pm@...r.kernel.org
Subject: Re: [PATCH 0/2] Fix per-policy boost behavior
On 27-02-24, 22:23, Sibi Sankar wrote:
> Fix per-policy boost behavior by incorporating per-policy boost flag
> in the policy->max calculation and setting the correct per-policy
> boost_enabled value on devices that use cpufreq_enable_boost_support().
I don't see the problem explained anywhere and the patches look
incorrect too. The drivers aren't supposed to update the
policy->boose_enabled value.
--
viresh
Powered by blists - more mailing lists