On 06/12/2015 01:37 PM, Valentin Longchamp wrote: > On 06/08/2015 01:46 PM, Valentin Longchamp wrote: >> On 06/06/2015 02:17 PM, Sebastian Hesselbarth wrote: >>> On 05.06.2015 17:19, Andrew Lunn wrote: >>>> On Fri, Jun 05, 2015 at 04:34:54PM +0200, Valentin Longchamp wrote: >>>>> I am currently bringing up the USB 2.0 Host controller of the Bobcat's (98DX4122 >>>>> Marvell switch) internal kirkwood CPU on a variation of Keymile's km_kirwood >>>>> hardware (kirkwood-km_kirkwood.dts). >>>>> >>>>> When the driver registers its hcd, it fails with a timemout as it can be seen in >>>>> the below log: >>>>> >>>>>> root@kmcoge5un:~# dmesg -n 8 >>>>>> root@kmcoge5un:~# insmod ehci-orion.ko >>>>>> ehci-orion: EHCI orion driver >>>>>> Initializing Orion-SoC USB Host Controller >>>>>> orion-ehci f1050000.ehci: EHCI Host Controller >>>>>> orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1 >>>>>> orion-ehci f1050000.ehci: reset hcs_params 0x10011 dbg=0 ind cc=0 pcc=0 ordered ports=1 >>>>>> orion-ehci f1050000.ehci: reset hcc_params 0006 thresh 0 uframes 256/512/1024 park >>>>>> orion-ehci f1050000.ehci: park 0 >>>>>> orion-ehci f1050000.ehci: reset command 0080002 (park)=0 ithresh=8 period=1024 Reset HALT >>>>>> orion-ehci f1050000.ehci: can't setup >>>>>> orion-ehci f1050000.ehci: USB bus 1 deregistered >>>>>> orion-ehci f1050000.ehci: init f1050000.ehci fail, -110 >>>>>> orion-ehci: probe of f1050000.ehci failed with error -110 >>>>> >>>>> This is very similar to this problem, except that it always happens: >>>>> https://lkml.org/lkml/2012/6/4/381 >>>>> >>>>> I have cornered it out to the last handshake() call of the ehci_halt() call, >>>>> that should set the controller in the HALT state. If I comment this handshake() >>>>> call out, the registration is fine and the controller then looks OK (I don't >>>>> have a hardware with a real USB bus to further test it yet). >>> >>> Valentin, >>> >>> can you specify what "real USB bus" means? Does your current hardware >>> support USB host or device with anything connected to it? >> >> No. The current hardware I am testing on does not support USB since the USB bus >> is not "wired" at all, there is no phy present (this maybe causes a problem ?). >> What I test is if the ehci-orion USB host driver is able to register with and >> configure the USB host controller present in the SoC, in order to prepare things >> for when the hardware is available. >> >> Hopefully I get some new hardware prototypes where the USB bus is complete this >> week so that I can test on the real setup. >> > > We have now received the hardware prototype and the behavior is exactly the > same: ETIMEOUT in ehci_halt(). If the last handshake() call is removed, the EHCI > host controller is correctly initialized and the device on the bus is detected > and works correctly. > > I thus tend to think that this is an IP (or Bobcat) internal problem and is not > really related with the hardware nor a PHY. > One final update on this topic: the kernel config was missing the CONFIG_USB_EHCI_ROOT_HUB_TT option. It turns out that the USB IP embeded a Transaction Translator and there is a check in ehci_halt() that aborts the routine in case of a Transaction Translator in the ehci controller. The check however only works in the above option is enabled. Thanks for the support Valentin -- 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
