On Tue, Apr 17, 2012 at 00:57:40, Paul Walmsley wrote:
> On Mon, 16 Apr 2012, Hiremath, Vaibhav wrote:
>
> > Doesn't this impact OMAP3x family?
> > The interface clocks will be enabled in omap_hwmod_enable(),
> > only if you set OCPIF_SWSUP_IDLE flag.
>
> In the autoidle case, the interface clock should be enabled by the call to
> omap_hwmod_setup_one() earlier in the same function.
>
You are right Paul, iclk is getting enabled in omap_hwmod_setup_one() -
static void __init _setup_iclk_autoidle(struct omap_hwmod *oh)
{
...
if (os->flags & OCPIF_SWSUP_IDLE) {
/* XXX omap_iclk_deny_idle(c); */
} else {
/* XXX omap_iclk_allow_idle(c); */
clk_enable(os->_clk);
}
...
}
Thanks,
Vaibhav
>
>
> - Paul
>
--
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
