summaryrefslogtreecommitdiffstats
path: root/net/bluetooth/a2mp.c
diff options
context:
space:
mode:
authorRafael J. Wysocki2017-02-28 00:05:01 +0100
committerRafael J. Wysocki2017-02-28 13:55:52 +0100
commitc3a49c8991212e1ef795c7a46881ac5cc7766993 (patch)
treefc5e53d4c1700681df745dfc9c45afc93f3fb8f3 /net/bluetooth/a2mp.c
parentcpufreq: qoriq: clean up unused code (diff)
downloadkernel-qcow2-linux-c3a49c8991212e1ef795c7a46881ac5cc7766993.tar.gz
kernel-qcow2-linux-c3a49c8991212e1ef795c7a46881ac5cc7766993.tar.xz
kernel-qcow2-linux-c3a49c8991212e1ef795c7a46881ac5cc7766993.zip
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>
Diffstat (limited to 'net/bluetooth/a2mp.c')
0 files changed, 0 insertions, 0 deletions