Romit Dasgupta <romit@xxxxxx> writes: > It is seen that the OMAP specific cpufreq initialization code tries to > scale the MPU frequency to the highest possible without taking care of > the voltage level. On power on reset the power IC does not provide the > necessary voltage for the highest available MPU frequency (that would > satisfy all Si families). This potentially is an window of opportunity > for things to go wrong. > > Signed-off-by: Romit Dasgupta <romit@xxxxxx> Looks good. Pulling into PM branch, and queing in pm-fixes for .33-rc series. Kevin > --- > diff --git a/arch/arm/plat-omap/cpu-omap.c b/arch/arm/plat-omap/cpu-omap.c > index 449b6b6..f94df20 100644 > --- a/arch/arm/plat-omap/cpu-omap.c > +++ b/arch/arm/plat-omap/cpu-omap.c > @@ -149,8 +149,6 @@ static int __init omap_cpu_init(struct cpufreq_policy *policy) > VERY_HI_RATE) / 1000; > } > > - clk_set_rate(mpu_clk, policy->cpuinfo.max_freq * 1000); > - > policy->min = policy->cpuinfo.min_freq; > policy->max = policy->cpuinfo.max_freq; > policy->cur = omap_getspeed(0); -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
