summaryrefslogtreecommitdiff
path: root/drivers/cpufreq/dbx500-cpufreq.c
diff options
context:
space:
mode:
authorViresh Kumar <viresh.kumar@linaro.org>2013-04-11 12:04:53 +0400
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-04-12 00:50:09 +0400
commite4969ebac83fdea78d89c779331396728a4e6199 (patch)
treea3ed54f86c50628e08eba962d2a137d9c2871976 /drivers/cpufreq/dbx500-cpufreq.c
parentd1b6848590af407c5d2354929ac683052d631830 (diff)
downloadlinux-e4969ebac83fdea78d89c779331396728a4e6199.tar.xz
cpufreq: Call __cpufreq_governor() with correct policy->cpus mask
__cpufreq_governor() must be called with a correct policy->cpus mask. In __cpufreq_remove_dev() we initially clear policy->cpus with cpumask_clear_cpu() and then call __cpufreq_governor(policy, CPUFREQ_GOV_POLICY_EXIT). If the governor is doing some per-cpu stuff in EXIT callback, this can create uncertain behavior. Generic governors in drivers/cpufreq/ doesn't do any per-cpu stuff in EXIT callback and so we don't face any issues currently. But its better to keep the code clean, so we don't face any issues in future. Now, we call cpumask_clear_cpu() only when multiple cpus are managed by policy. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/dbx500-cpufreq.c')
0 files changed, 0 insertions, 0 deletions