Re: [PATCH 0/2] Fix per-policy boost behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On 2/28/24 07:36, Jie Zhan wrote:
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?

In the existing code, per-policy flags doesn't have any impact i.e.
if cpufreq_driver boost is enabled and one or more of the per-policy
boost is disabled, the cpufreq driver will behave as if boost is
enabled. The second issue was just book keeping, meaning some drivers
enable boost by default, however the per-policy boost flags are set
as disabled during boot.



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]:


you can also have a look at ^^ thread for more info.

Sibi Sankar (2):
   cpufreq: Fix per-policy boost behavior on SoCs using
   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(-)

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [Linux for Sparc]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux