Hi Keshava, On Mon, Jul 16, 2012 at 07:01:06PM +0530, Keshava Munegowda wrote: > The TLL (Transceiver Less Link) is an separate IP block, independent of > the host controller. Basically this TLL operates like USB PHY which allows > the user to connect two USB transceiver interfaces together directly > without the use of differential transceivers in omap3 and later chips. > The TLL configuration is removed from the UHH driver and implemented as > a seperate platform driver. Now, the UHH driver configures the TLL > through API's exported by the TLL platform driver. > > Signed-off-by: Keshava Munegowda <keshava_mgowda@xxxxxx> > > In v4: > - rebased on top of linux kernel version 3.5.rc7 > - reworked as per the comments given by Paul Walmsley <paul@xxxxxxxxx> > > In v3: > - rebased on top V3 of Russ dill's patch > 'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue' > fixes an issue where the ULPI PHYs were not held in reset > while initializing the EHCI controller > http://permalink.gmane.org/gmane.linux.usb.general/65988 > > - rebased on top of patch > OMAP: USB : Fix the EHCI enumeration and core retention issue > http://permalink.gmane.org/gmane.linux.usb.general/66239 > > In V2: > - covered review comments from linux omap and usb community > - rebased on top Russ dill's patch > 'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue' > fixes an issue where the ULPI PHYs were not held in reset > while initializing the EHCI controller > > Keshava Munegowda (5): > ARM: OMAP: Add the USB TLL clocks device name > ARM: OMAP: USB: HOST TLL platform driver > ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver > ARM: OMAP: USB: Remove TLL specific code from USB HS core driver > ARM: OMAP: Remove older device name of the USB TLL clocks All 5 patches applied now. I had to manually apply patches #1 and #5. Could you please check that it's looking good to you ? Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ -- 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
