summaryrefslogtreecommitdiffstats
path: root/drivers/cpufreq/elanfreq.c
diff options
context:
space:
mode:
authorViresh Kumar <viresh.kumar@linaro.org>2013-04-01 12:57:43 +0000
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-04-02 15:10:48 +0200
commit746b3df98b2edc0e0844537a247e820ac6503031 (patch)
treefacb9d766dcbdb30603540a9550a6720459f8591 /drivers/cpufreq/elanfreq.c
parent3a7818e62751a4dda40d6ea0bdb0022d56aee3c1 (diff)
downloadblackbird-op-linux-746b3df98b2edc0e0844537a247e820ac6503031.tar.gz
blackbird-op-linux-746b3df98b2edc0e0844537a247e820ac6503031.zip
cpufreq: cpufreq-cpu0: No need to check cpu number in init()
It is not possible for init() to be called for any cpu other than cpu0. During bootup whatever cpu is used to boot system will be assigned as cpu0. And later on policy->cpu can only change if we hotunplug all cpus first and then hotplug them back in different order, which isn't possible (system requires atleast one cpu to be up always :)). Though I can see one situation where policy->cpu can be different then zero. - Hot-unplug cpu 0. - rmmod cpufreq-cpu0 module - insmod it back - hotplug cpu 0 again. Here, policy->cpu would be different. But the driver doesn't have any dependency on cpu0 as such. We don't mind which cpu of a system is policy->cpu and so this check is just not required. Remove it. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Acked-by: Shawn Guo <shawn.guo@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/elanfreq.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud