[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <91118802-eb8c-6225-3610-05e16270b3c4@hisilicon.com>
Date: Wed, 28 Feb 2024 10:06:17 +0800
From: Jie Zhan <zhanjie9@...ilicon.com>
To: Sibi Sankar <quic_sibis@...cinc.com>
CC: <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>,
<dietmar.eggemann@....com>, <marcan@...can.st>, <sven@...npeter.dev>,
<alyssa@...enzweig.io>, <rafael@...nel.org>, <viresh.kumar@...aro.org>,
<xuwei5@...ilicon.com>
Subject: Re: [PATCH 0/2] Fix per-policy boost behavior
Hi Sibi,
Thanks for pointing this issue out.
However, I can't clearly see how the existing code fails.
cpufreq_frequency_table_cpuinfo() checks cpufreq_boost_enabled(),
and that should be already set in cpufreq_boost_trigger_state() before
calling cpufreq_boost_set_sw(), so presumably cpufreq_boost_set_sw()
is supposed to work as expected.
Can you explain this a bit further?
Cheers,
Jie
On 28/02/2024 00:53, 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().
>
> Logs reported-by Dietmar Eggemann [1]:
>
> [1] https://lore.kernel.org/lkml/265e5f2c-9b45-420f-89b1-44369aeb8418@arm.com/
>
> Sibi Sankar (2):
> cpufreq: Fix per-policy boost behavior on SoCs using
> cpufreq_boost_set_sw
> cpufreq: apple-soc: Align per-policy and global boost flags
>
> drivers/cpufreq/apple-soc-cpufreq.c | 1 +
> drivers/cpufreq/cpufreq.c | 15 +++++++++------
> drivers/cpufreq/freq_table.c | 2 +-
> 3 files changed, 11 insertions(+), 7 deletions(-)
>
Powered by blists - more mailing lists