On Tue, 2013-04-09 at 14:28 -0300, Fabio Estevam wrote: > On Mon, Apr 8, 2013 at 9:09 PM, Fabio Estevam <festevam@xxxxxxxxx> wrote: > > >> I know that I have to use the driver ULPI but with my configuration, I > >> get these errors : > >> " > >> ehci-mxc: Freescale On-Chip EHCI Host driver > >> mxc-ehci mxc-ehci.0: initializing i.MX USB Controller > >> timeout polling for ULPI device > >> mxc-ehci mxc-ehci.0: unable to init transceiver, probably missing > > Just tested mx31pdk on a 3.8.6 kernel and I got: > > ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > ehci-mxc: Freescale On-Chip EHCI Host driver > mxc-ehci mxc-ehci.0: initializing i.MX USB Controller > ULPI transceiver vendor/product ID 0x04cc/0x1504 > Found NXP ISP1504 ULPI transceiver. > ULPI integrity check: passed. > mxc-ehci mxc-ehci.0: EHCI Host Controller > mxc-ehci mxc-ehci.0: new USB bus registered, assigned bus number 1 > mxc-ehci mxc-ehci.0: irq 53, io mem 0x43f88000 > mxc-ehci mxc-ehci.0: USB 2.0 started, EHCI 1.00 > hub 1-0:1.0: USB hub found > hub 1-0:1.0: 1 port detected > mxc-ehci mxc-ehci.2: initializing i.MX USB Controller > timeout polling for ULPI device > mxc-ehci mxc-ehci.2: unable to init transceiver, probably missing Any updates on this? I'm facing the same kind of issue with an SMSC3340 phy connected to an imx.27: After some minutes in power-off state, the first boot fails to detect the ULPI device connected to USBOTG-Pins, no matter if host- or device-mode is configured. But the strange thing is that then, after a reboot or reset the phy gets detected. Could this be related to the following errata? http://www.freescale.com/files/32bit/doc/errata/MCIMX27CE.pdf Number: bo58229 Module Affected: USB Title: A remote wake-up can be interpreted as a disconnect Description: In Host mode in the ULPI core, a remote wake-up can be interpreted as a disconnect. This issue involves the latency when asserting in synchronous mode. In some instances, the host will not properly latch the K state. When this occurs, the core wakes up to a J state. Eventually the host will not resume, and will show an SE0 and assume a disconnect occurred. What seems to workaround the problem is when you do a reset of the phy by a GPIO line right before USB initialization. But guess what, here is normally no reset-line connected to the smsc3340. Thanks -- Christoph -- 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
