From: Eduardo Valentin <[email protected]> This patch fix the sequence inside omap_target while setting a frequency for OMAP3 devices.
Previously any frequency was set, even if out of range. Now the range set by the governor is also checked for OMAP3. Signed-off-by: Eduardo Valentin <[email protected]> --- arch/arm/plat-omap/cpu-omap.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/arch/arm/plat-omap/cpu-omap.c b/arch/arm/plat-omap/cpu-omap.c index a69b557..0674405 100644 --- a/arch/arm/plat-omap/cpu-omap.c +++ b/arch/arm/plat-omap/cpu-omap.c @@ -88,7 +88,7 @@ static int omap_target(struct cpufreq_policy *policy, struct cpufreq_freqs freqs; #endif #if defined(CONFIG_ARCH_OMAP3) && !defined(CONFIG_OMAP_PM_NONE) - unsigned long freq = target_freq * 1000; + unsigned long freq; #endif int ret = 0; @@ -114,6 +114,7 @@ static int omap_target(struct cpufreq_policy *policy, ret = clk_set_rate(mpu_clk, freqs.new * 1000); cpufreq_notify_transition(&freqs, CPUFREQ_POSTCHANGE); #elif defined(CONFIG_ARCH_OMAP3) && !defined(CONFIG_OMAP_PM_NONE) + freq = target_freq * 1000; if (opp_find_freq_ceil(OPP_MPU, &freq)) omap_pm_cpu_set_freq(freq); #endif -- 1.7.0.2 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
