-
- Downloads
cpufreq: Save user policy min/max instead of policy min/max during hotplug
When a CPU is hotplugged off, various fields of the policy are saved so that they can be restored when the CPU is hotplugged back in. The existing code saves the policy min/max field during hotplug remove and restores it into user policy min/max during hotplug add. This results in the loss of the user policy min/max values across a hotplug remove/add. Fix it by saving the user policy min/max instead of policy min/max during hotplug remove. During a hotplug add, after user policy min/max is restored, the policy min/max is already recomputed. So, there's no risk of going beyound any limits imposed by the CPUFREQ_ADJUST/INCOMPATIBLE notifiers. Bug: 17889870 Change-Id: Ib8e09fa324c1f80f095c5754b5dcf2685e8e4a66 Signed-off-by:Saravana Kannan <skannan@codeaurora.org> Signed-off-by:
Naveen Ramaraj <nramaraj@codeaurora.org>
Loading
Please register or sign in to comment