>From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of >Woodruff, Richard >Sent: Sunday, October 12, 2008 8:22 AM >To: David Brownell; Steve Sakoman >Cc: Anand Gadiyar; linux-omap@xxxxxxxxxxxxxxx >Subject: RE: [patch 2.6.27-rc8-omap 0/7] resend of pending TWL patches > > >> owner@xxxxxxxxxxxxxxx] On Behalf Of David Brownell > >> > Turns out it is this one in omap_start_ehc: >> > >> > /* Wait for TLL to be Active */ >> > while ((cm_read_mod_reg(CORE_MOD, OMAP2430_CM_IDLEST3) & >> > (1 << OMAP3430ES2_ST_USBTLL_SHIFT))); >> >> Fishy ... TLL == TransceiverLess Link, which is used with >> on-board links that don't need to be morphed to use signals >> that go over cables as defined in the USB spec. I would >> think you'd want ULPI. > >TLL block does get used for some cases for non-tll (phy) mode use. In particular, clocking mode used for EHCI on omap34xx is input clocking mode. This means OMAP feeds the 60Mhz clock and TLL module is used to generate the 60Mhz clock. So irrespective of TLL or ULPI-PHY mode, TLL block has to be kept up. > Recently there was some low >fixes for non-tll mode in which tll block handling was important. This was specifically in ohci >configuration. > >Anand (in copy) did make some fix which changed ordering of clock enables which were necessary to get >usb bus suspend/resume working. With the other ordering you would get an abort when accessing that >blocks registers. > >Regards, >Richard W. > >-- >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 -- 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
