diff options
| author | Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> | 2016-04-04 05:42:11 +0300 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2016-04-05 04:37:13 +0300 |
| commit | 30a3915385f124a6e3c81df4070f531d4f84299b (patch) | |
| tree | 157f23f9ae570cef26efc99120d7ca0eab858f34 /drivers/cpufreq/cpufreq-dt.c | |
| parent | febce40febcff3ccdb33f63456ffc4cfc61640c8 (diff) | |
| download | linux-30a3915385f124a6e3c81df4070f531d4f84299b.tar.xz | |
cpufreq: intel_pstate: fix inconsistency in setting policy limits
When user sets performance policy using cpufreq interface, it is possible
that because of policy->max limits, the actual performance is still
limited. But the current implementation will silently switch the
policy to powersave and start using powersave limits. If user modifies
any limits using intel_pstate sysfs, this is actually changing powersave
limits.
The current implementation tracks limits under powersave and performance
policy using two different variables. When policy->max is less than
policy->cpuinfo.max_freq, only powersave limit variable is used.
This fix causes the performance limits variable to be used always when
the policy is performance.
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/cpufreq-dt.c')
0 files changed, 0 insertions, 0 deletions