On Wed, 24 Jun 2009, Pandita, Vikram wrote: > >-----Original Message----- > >From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Kevin > >Hilman > > > >Rather than simply setting force-idle mode on boot, do a reset of the > >OTG module. This really ensures that any bootloader/bootstrap code > >that leaves it active will not prevent future retention. After reset, > >OTG module will be in force-idle, force-standby mode. > > > >In addition, ensure that the iclk is enabled before attempting a write > >to the module SYSCONFIG register. > > This patch solves MUSB issue, but is not generic for all IP blocks on omap. > > ROM code or u-boot could leave the module sysconfig in a non-idle state. > > I recommend just like CONFIG_OMAP_RESET_CLOCKS for clocks, same could be > done generically for all SYSCONFIG registers in some prcm code and not > driver specific. I agree. Please contribute to the development of the omap_hwmod patchset, which does this (among other things). - 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
