Re: [PATCH 1/2] cpufreq: allow cpuinfo max to decrease when boost is disabled

Dmitry Baryshkov <[email protected]> Thu, 6 Aug 2026 12:28:47 +0300
Newsgroups org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-kernel,org.kernel.vger.linux-pm
Message-ID <35it74zycctxhpnbsuvp6a6aazrjavarhq43fqgruafjv7xkt2@recuceutrqrn>
On Thu, Aug 06, 2026 at 10:12:29AM +0530, Sibi Sankar wrote:
> From: Ananthu C V <[email protected]>
> 
> Commit 538b0188da46 ("cpufreq: ACPI: Set cpuinfo.max_freq directly
> if max boost is known") guarded cpuinfo max updates to only allow
> increases, preserving values set directly by drivers above the freq
> table maximum. This prevents cpuinfo max from decreasing on boost
> disable, leaving policy max pinned at the boost ceiling.

Why is this bad?

> 
> Remove the guard so cpuinfo max is always derived from the frequency
> table scan. Drivers that correctly flag boost entries are unaffected
> since the scan already excludes them when boost is off.
> 
> Fixes: 538b0188da46 ("cpufreq: ACPI: Set cpuinfo.max_freq directly if max boost is known")
> Signed-off-by: Ananthu C V <[email protected]>
> Signed-off-by: Sibi Sankar <[email protected]>
> ---
>  drivers/cpufreq/freq_table.c | 7 +------
>  1 file changed, 1 insertion(+), 6 deletions(-)
> 

-- 
With best wishes
Dmitry