cpufreq: omap: don't initialize part of policy set by core
Many common initializations of struct policy are moved to core now and hence this driver doesn't need to do it. This patch removes such code. Most recent of those changes is to call ->get() in the core after calling ->init(). Cc: Santosh Shilimkar <santosh.shilimkar@ti.com> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
This commit is contained in:
parent
d31a4a9ae0
commit
1857a25cd3
|
@ -171,8 +171,6 @@ static int omap_cpu_init(struct cpufreq_policy *policy)
|
|||
goto fail_ck;
|
||||
}
|
||||
|
||||
policy->cur = omap_getspeed(policy->cpu);
|
||||
|
||||
if (!freq_table)
|
||||
result = opp_init_cpufreq_table(mpu_dev, &freq_table);
|
||||
|
||||
|
@ -188,8 +186,6 @@ static int omap_cpu_init(struct cpufreq_policy *policy)
|
|||
if (result)
|
||||
goto fail_table;
|
||||
|
||||
policy->cur = omap_getspeed(policy->cpu);
|
||||
|
||||
/*
|
||||
* On OMAP SMP configuartion, both processors share the voltage
|
||||
* and clock. So both CPUs needs to be scaled together and hence
|
||||
|
|
Loading…
Reference in New Issue