"Woodruff, Richard" <r-woodruff2@xxxxxx> writes: >> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- >> owner@xxxxxxxxxxxxxxx] On Behalf Of Niilo Minkkinen >> Sent: Monday, May 18, 2009 9:54 AM > >> Omap3 MUSB AUTOIDLE functionality configured through OTG_SYSCONFIG >> register prevents the device from going into retention. >> This is a workaround (by Richard Woodruff/TI), as his comment : >> > A new MUSB bug which is a match to data below was identified very >> > recently (on hardware and in simulation). >> > This bug is in 3430 and not 3630. >> > As a priority test (and as new default) you should have engineers >> > disable autoidle for MUSB block. >> > This is the workaround which will show up in next errata. >> >> Signed-off-by: Niilo Minkkinen <ext-niilo.1.minkkinen@xxxxxxxxx> > > Signed-off-by: Richard Woodruff <r-woodruff2@xxxxxx> > > Yes this is needed for 34xx. Side note is this cost around 1mW of power during active mode of MUSB. When device is not active cost is not significant. System impact depends on duty cycle of MUSB in usecase. > While this makes its way upstream, I'll pull into PM branch. Kevin -- 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
