On Thu, Dec 3, 2009 at 9:29 AM, Dasgupta, Romit <ro...@ti.com> wrote: > > >> > Signed-off-by: Romit Dasgupta <ro...@ti.com> >> > --- >> > 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); >> >> This patch leads to hang with current PM branch, SRF and CPU IDLE enabled >> on OMAP3525 rev C. > Verified this to work on Zoom2 + SRF + CPUidle. Can you give some debug info > if possible? > Well, that looks like false alarm - I tried clean tree without local patches, and it seems to work.
However, without this line removed, my system boots faster. Is it possible to limit initial speed for unstable setups, but to boot as fast as possible? Thanks a lot, S. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
