| commit | c3a49c8991212e1ef795c7a46881ac5cc7766993 | |
| author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | |
| Mon, 27 Feb 2017 23:05:01 +0000 (28 00:05 +0100) | ||
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | |
| Tue, 28 Feb 2017 12:55:52 +0000 (28 13:55 +0100) | ||
| tree | fc5e53d4c1700681df745dfc9c45afc93f3fb8f3 | treesnapshot (tar.gz zip) |
| parent | 17b4eaf475684bd12aeecf358a7ea6e3bec871a5 | commitdiff |
cpufreq: intel_pstate: Fix limits issue with operation mode switching
There is a problem with intel_pstate operation mode switching
introduced by commit fb1fe1041c04 (cpufreq: intel_pstate: Operation
mode control from sysfs), because the global sysfs limits are
preserved across operation modes while per-policy limits are
reinitialized from scratch on a mode switch and both sets of limits
may get out of sync this way.
Fix that by always reinitializing the global limits upon the
registration of the driver.
Fixes: fb1fe1041c04 (cpufreq: intel_pstate: Operation mode control from sysfs)
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
There is a problem with intel_pstate operation mode switching
introduced by commit fb1fe1041c04 (cpufreq: intel_pstate: Operation
mode control from sysfs), because the global sysfs limits are
preserved across operation modes while per-policy limits are
reinitialized from scratch on a mode switch and both sets of limits
may get out of sync this way.
Fix that by always reinitializing the global limits upon the
registration of the driver.
Fixes: fb1fe1041c04 (cpufreq: intel_pstate: Operation mode control from sysfs)
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
| drivers/cpufreq/intel_pstate.c | diffblobblamehistory |