Op 2 mei 2012, om 12:38 heeft Raja, Govindraj het volgende geschreven: > On Wed, May 2, 2012 at 2:17 PM, Russ Dill <Russ.Dill@xxxxxx> wrote: >> On Mon, Mar 19, 2012 at 6:34 AM, Raja, Govindraj <govindraj.raja@xxxxxx> wrote: >>> On Mon, Mar 19, 2012 at 12:12 PM, Keshava Munegowda >>> <keshava_mgowda@xxxxxx> wrote: >>>> From: Keshava Munegowda <Keshava_mgowda@xxxxxx> >>>> >>>> It is observed that the echi ports of 3430 sdp board >>>> are not working due to the random timing of programming >>>> the associated GPIOs of the ULPI PHYs of the EHCI for reset. >>>> If the PHYs are reset at during usbhs core driver, host ports will >>>> not work because EHCI driver is loaded after the resetting PHYs. >>>> The PHYs should be in reset state while initializing the EHCI >>>> controller. >>>> The code which does the GPIO pins associated with the PHYs >>>> are programmed to reset is moved from the USB host core driver >>>> to EHCI driver. >>> >>> I tested on beagle xm where gpio nreset is requested from >>> board file. >>> (Basic enumertaion after gpio nreset seems to work fine, >>> Hub and smsc lan chip get detected afetr boot up) >>> >> >> What base did you test this on top of? my xM is failing USB-wise when >> I apply this on v3.3.3 (with the UART mux fix patch) and where it is >> applied within master (3.4-rc4, again, with the UART mux fix patch). >> Additionally, reverting this patch from 3.4-rc5 causes rc5 to work >> properly. >> > > Works for me be on 3.4-rc5 Beagle-XM even without reverting the patch > > Logs as in here [1]. >From your log: [ 1.705291] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 3.726593] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller Why is the ehci stuff taking more than 2 seconds? regards, Koen-- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
