On Thu, 2011-08-11 at 11:07 +0300, Ohad Ben-Cohen wrote: > > Any clues? > > Reverting 665d001338b494d6d62810aa99b4c0fa1a0884b9 "OMAP2+: hwmod: > Follow the recommended PRCM module enable sequence" fixes this for me. > > More specifically, this hunk alone seems to do the trick: > > diff --git a/arch/arm/mach-omap2/clock44xx_data.c b/arch/arm/mach-omap2/clock44x > index 2af0e3f..12d22a8 100644 > --- a/arch/arm/mach-omap2/clock44xx_data.c > +++ b/arch/arm/mach-omap2/clock44xx_data.c > @@ -3379,7 +3379,6 @@ int __init omap4xxx_clk_init(void) > } > > clk_init(&omap2_clk_functions); > - omap2_clk_disable_clkdm_control(); > > for (c = omap44xx_clks; c < omap44xx_clks + ARRAY_SIZE(omap44xx_clks); > c++) > > I'm not suggesting this is anyway near a real fix, but hopefully it > will help pin-point the problem (clock44xx_data.c changes ?). This solves (or works around?) the problem for me too. Thanks, Ohad! -- Cheers, Luca. -- 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
