* Felipe Balbi <balbi@xxxxxx> [120607 00:39]: > Hi, > > On Thu, Jun 07, 2012 at 12:31:13AM -0700, Tony Lindgren wrote: > > * Paul Walmsley <paul@xxxxxxxxx> [120606 23:26]: > > > From: Tero Kristo <t-kristo@xxxxxx> > > > > > > Add a custom reset function for the usb_host_fs/fsusb IP block, and > > > connect it to the OMAP4 FSUSB block. > > > > > > This is the first of two fixes required to get rid of the boot > > > warning: > > > > > > omap_hwmod: usb_host_fs: _wait_target_disable failed > > > > > > and to allow the module to idle. > > > > > > It may be necessary to use this reset method for OMAP2xxx SoCs as > > > well; this is left for a future patch. > > > > Here too I think driver like features like this should live in the > > driver init for omap OHCI driver. In the likely case that FS OHCI is > > not in use on the board, the OHCI glue can just reset it. > > this I don't agree. It means we will have to add some OHCI code even > when OHCI is disabled. That's because the bus level code alone is not enough for the reset and driver features are needed to reset it. Nothing wrong with the code itself, it should be just something that's part of the driver rather than the bus level code. It could be always built in for sure even if it lives under drivers. Tony -- 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
