> -----Original Message----- > From: Balbi, Felipe > Sent: Friday, September 17, 2010 4:12 PM > To: Shilimkar, Santosh > Cc: Menon, Nishanth; linux-omap@xxxxxxxxxxxxxxx; linux-arm- > kernel@xxxxxxxxxxxxxxxxxxx; Nayak, Rajendra > Subject: Re: [PATCH 14/14] omap4: Fix bootup crash observed with higher > CPU clocks > > hi, > > On Fri, Sep 17, 2010 at 05:30:30AM -0500, Shilimkar, Santosh wrote: > >Second your thought. Infact I wasn't ok to push this patch to start > >with but it's needed till the timer hwmod gets merged > > to me, it just looks like "omap_test_timeout()" is timing out and that > function is omap_dm_timer_set_source() is returning with a > still-disabled clock. > > could you check if you get "cm: Module associated with clock > gpt<blablabla> didn't enabled in 100000 tries" message on your dmesg ?? > On OMAP4 specifically, the wait IDLEST support isn't there in the clock framework. This is taken care now in hwmod framework. With that we see that we don't need this delay anymore. The delay change is there for some time. May be there were issue with wait IDLEST. Regards, Santosh -- 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
