[PATCH 1/2] cpufreq: allow cpuinfo max to decrease when boost is disabled
Sibi Sankar <[email protected]> Thu, 6 Aug 2026 10:12:29 +0530
| Newsgroups | org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-kernel,org.kernel.vger.linux-pm |
|---|---|
| Message-ID | <[email protected]> |
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. 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(-) diff --git a/drivers/cpufreq/freq_table.c b/drivers/cpufreq/freq_table.c index ea994647abc8..791118466ca4 100644 --- a/drivers/cpufreq/freq_table.c +++ b/drivers/cpufreq/freq_table.c @@ -50,12 +50,7 @@ int cpufreq_frequency_table_cpuinfo(struct cpufreq_policy *policy) } policy->cpuinfo.min_freq = min_freq; - /* - * If the driver has set its own cpuinfo.max_freq above max_freq, leave - * it as is. - */ - if (policy->cpuinfo.max_freq < max_freq) - policy->cpuinfo.max_freq = max_freq; + policy->cpuinfo.max_freq = max_freq; if (min_freq == ~0) return -EINVAL; -- 2.34.1