Hi, On Fri, Sep 17, 2010 at 05:14:59AM -0500, Menon, Nishanth wrote:
@@ -581,7 +581,7 @@ int omap_dm_timer_set_source(struct omap_dm_timer *timer, int source) * When the functional clock disappears, too quick writes seem * to cause an abort. XXX Is this still necessary? */ - __delay(150000); + __delay(300000);What is the rationale for this increase? Lets say we have a CPU bumped up to 1GHz or something will we have weird numbers again?
yeah, I thought the _omap2_module_wait_ready() should handle that ?? -- balbi -- 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
