On Thu, Nov 28, 2013 at 9:51 AM, <anaumann@xxxxxxxxxxxxxx> wrote: > From: Andreas Naumann <anaumann@xxxxxxxxxxxxxx> > > This is a hard to reproduce problem which leads to non-functional > USB-OTG port in 0.1%-1% of all boots. Tracked it down to commit > e25bec160158abe86c276d7d206264afc3646281, which introduces save/restore > of OTG_INTERFSEL over suspend. > Since the resume function is also called early in driver init, it uses a > non-initialized value (which is 0 and a non-supported setting in DM37xx > for INTERFSEL). Shortly after the correct value is set. Apparently this > works most time, but not always. > > The fix is to initialize the value, BEFORE being written in the resume > function. Nice find, I think I'm also affected by this. However this crashes on OMAP3530 pandora because you now access INTERFSEL before interface clock is enabled.. This is not a problem on DM37xx because it uses different interconnects. You should probably use "context_valid" variable in omap2430_glue or similar to decide to write to register or not. Gražvydas -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
