Hi Jon, On Tue, 31 Jul 2012, Jon Hunter wrote: > Sorry for all the emails. However, I wanted to get this out to you as > I am due to be out for a couple weeks. > > So I have updated your patch [1] with the following changes ... > > 1. Re-based on top of your omap3 clock domain fix [2] > 2. Modified the above change I mentioned to check for > CLKDM_MISSING_IDLE_REPORTING in omap_pm_clkdms_setup() instead of > the omap2_clkdm_clk_enable(). This is to prevent the clock domain > being placed in HW_AUTO on boot if enabled early. > 3. Made the other change I mentioned earlier [3]. > > This is now working well for me on OMAP3/4. Your changes look good to me. Do you have a strong preference as to whether that patch should go in as part of 3.6-rc or 3.7? I'd be inclined to queue it for 3.7 based on the size of the patch. - Paul -- 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
