diff options
| author | Doug Smythies <dsmythies@telus.net> | 2023-08-20 13:46:49 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-09-13 09:42:26 +0200 |
| commit | 63f1117db59001a4e1734fba8fc6db6f3540ecdd (patch) | |
| tree | 9e9fe9ccb5822851f922e6b34ae34155e8347a99 /crypto | |
| parent | c50fdd53344810b2ca977f4d4979fb1dec811627 (diff) | |
| download | linux-63f1117db59001a4e1734fba8fc6db6f3540ecdd.tar.gz linux-63f1117db59001a4e1734fba8fc6db6f3540ecdd.tar.bz2 linux-63f1117db59001a4e1734fba8fc6db6f3540ecdd.zip | |
cpufreq: intel_pstate: set stale CPU frequency to minimum
commit d51847acb018d83186e4af67bc93f9a00a8644f7 upstream.
The intel_pstate CPU frequency scaling driver does not
use policy->cur and it is 0.
When the CPU frequency is outdated arch_freq_get_on_cpu()
will default to the nominal clock frequency when its call to
cpufreq_quick_getpolicy_cur returns the never updated 0.
Thus, the listed frequency might be outside of currently
set limits. Some users are complaining about the high
reported frequency, albeit stale, when their system is
idle and/or it is above the reduced maximum they have set.
This patch will maintain policy_cur for the intel_pstate
driver at the current minimum CPU frequency.
Reported-by: Yang Jie <yang.jie@linux.intel.com>
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217597
Signed-off-by: Doug Smythies <dsmythies@telus.net>
[ rjw: White space damage fixes and comment adjustment ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Keyon Jie <yang.jie@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions