On Tue, Nov 28, 2017 at 02:59:32PM -0500, Alan Stern wrote: > On Tue, 28 Nov 2017, Ladislav Michl wrote: > > > On Tue, Nov 28, 2017 at 01:09:45PM -0500, Alan Stern wrote: > > > The EHCI debugging files require CONFIG_DYNAMIC_DEBUG to be enabled. > > > Oddly enough, the OHCI debugging files do not have the same > > > requirement. I don't know the reason for this difference. > > > > I see, thanks for suggestion. > > > > USB cable unplugged: > > $ cat /sys/kernel/debug/usb/ehci/48064800.ehci/registers > > bus platform, device 48064800.ehci > > EHCI Host Controller > > EHCI 1.00, rh state running > > structural params 0x00001313 > > capability params 0x00000016 > > status 0000 > > command 0010005 (park)=0 ithresh=1 period=512 RUN > > intrenable 37 IAA FATAL PCD ERR INT > > uframe 0000 > > port:1 status 001000 0 ACK POWER sig=se0 > > port:2 status 001000 0 ACK POWER sig=se0 > > port:3 status 001000 0 ACK POWER sig=se0 > > irq normal 0 err 0 iaa 0 (lost 0) > > complete 0 unlink 0 > > > > Plugged: > > $ cat /sys/kernel/debug/usb/ehci/48064800.ehci/registers > > bus platform, device 48064800.ehci > > EHCI Host Controller > > EHCI 1.00, rh state running > > structural params 0x00001313 > > capability params 0x00000016 > > status 0000 > > command 0010005 (park)=0 ithresh=1 period=512 RUN > > intrenable 37 IAA FATAL PCD ERR INT > > uframe 0000 > > port:1 status 001000 0 ACK POWER sig=se0 > > port:2 status 001000 0 ACK POWER sig=se0 > > port:3 status 001000 0 ACK POWER sig=se0 > > irq normal 0 err 0 iaa 0 (lost 0) > > complete 0 unlink 0 > > So no change at all. In particular, no change to the port statuses. > This suggests the hardware isn't configured properly; maybe a phy isn't > detecting the new connection. > > I don't know anything about the phy drivers, however. You should bring > this to the attention of the maintainer for whichever phy is on your > board. Thanks for suggestion, there's USB3326 ULPI PHY with nEN_USB_PWR connected to TWL4030 LEDA output. > By the way, the behavior when you plug in a device with CONFIG_PM=n > should be just about the same as the behavior with CONFIG_PM=y when you > plug in a _second_ device. Have you tried doing that, say with two > flash drives? (I'm assuming your board has more than one EHCI port > available.) Unfortunately there's only one EHCI port, however your suggestions are enough to start debugging. Thank you, ladis -- 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
