diff options
author | Lan Tianyu <tianyu.lan@intel.com> | 2013-08-13 10:07:28 +0800 |
---|---|---|
committer | MyungJoo Ham <myungjoo.ham@samsung.com> | 2013-11-15 13:52:52 +0900 |
commit | a4e537485cd11c8645b403db3853bbc10fffce60 (patch) | |
tree | cc63a1c7f19f63a530ce0b54831a462c07a09815 /security/device_cgroup.c | |
parent | 3bbc1028565351fbddc62843a3aa16cc49286d8c (diff) | |
download | linux-3.10-a4e537485cd11c8645b403db3853bbc10fffce60.tar.gz linux-3.10-a4e537485cd11c8645b403db3853bbc10fffce60.tar.bz2 linux-3.10-a4e537485cd11c8645b403db3853bbc10fffce60.zip |
Thermal/cpu_cooling: Return directly for the cpu out of allowed_cpus in the cpufreq_thermal_notifier()
cpufreq_thermal_notifier() is to change the cpu's cpufreq in the allowed_cpus mask
when associated thermal-cpufreq cdev's cooling state is changed. It's a cpufreq policy
notifier handler and it will be triggered even if those cpus out of allowed_cpus has
changed freq policy.
cpufreq_thermal_notifier() checks the policy->cpu. If it belongs to allowed_cpus,
change max_freq(default to 0) to the desire cpufreq value and pass 0 and max_freq
to cpufreq_verify_within_limits() as cpufreq scope. But if not, do nothing and
max_freq will remain 0. This will cause the cpufreq scope to become 0~0. This
is not right. This patch is to return directly after finding cpu not belonging
to allowed_cpus.
Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
Signed-off-by: Zhang Rui <rui.zhang@intel.com>
Diffstat (limited to 'security/device_cgroup.c')
0 files changed, 0 insertions, 0 deletions