cpufreq: Do not clear real_cpus mask on policy init
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>
Mon, 13 Feb 2017 12:44:57 +0000 (13:44 +0100)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Wed, 15 Feb 2017 23:57:42 +0000 (00:57 +0100)
commitf451014692ae34e587b00de6745e16661cf734d8
tree6f3e747e1a4c2de894d5bf7aa6e10a0a28170fed
parent051bd84bb45bc994b7d762467f60b3bd0c7aa6bc
cpufreq: Do not clear real_cpus mask on policy init

If new_policy is set in cpufreq_online(), the policy object has just
been created and its real_cpus mask has been zeroed on allocation,
and the driver's ->init() callback should not touch it.

It doesn't need to be cleared again, so don't do that.

Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
drivers/cpufreq/cpufreq.c