Hi All Adding Vivek Gautam. On 29 August 2016 at 16:35, Michael Niewöhner <linux@xxxxxxxxxxxxxx> wrote: > Hi Mathias, > On Mo, 2016-08-29 at 13:59 +0300, Mathias Nyman wrote: >> On 29.08.2016 10:28, Felipe Balbi wrote: >> > >> > >> > Hi, >> > >> > Michael Niewöhner <linux@xxxxxxxxxxxxxx> writes: >> > > >> > > [1.] One line summary of the problem: >> > > DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422 >> > > >> > > [2.] Full description of the problem/report: >> > > No usb 3.0 devices are being detected when attached while USB 2.0 >> > > devices work on the same port. >> > > USB 3.0 works after applying patches [9.1] and [9.2], but seems >> > > to be >> > > buggy. The usb hub is redetected every time an usb device is >> > > attached. >> > >> > dwc3 is host, which means it's actually XHCI :-) >> > >> > Adding Mathias >> > >> > > >> > > dmesg: >> > > [ 192.287080] usb 3-1.2: USB disconnect, device number 7 >> > > [ 210.370699] hub 3-1:1.0: hub_ext_port_status failed (err = >> > > -71) >> >> Looks like the hub GetPortStatus request fails with protocol error. >> >> Reading xhci root hub port status is mostly just register reads and >> writes. It >> shouldn't include any actual transfers that could return -EPROTO >> >> So this is not the root hub? but a external or integrated on your >> board, right? >> >> The protocol error -71 is returned at transfer errors or if device >> stalled. >> >> Adding more xhci debugging options could show something: >> echo -n 'module xhci_hcd =p' > >> /sys/kernel/debug/dynamic_debug/control >> >> > >> > > >> > > [9.] Other notes, patches, fixes, workarounds: >> > > [9.1] https://lkml.org/lkml/2014/4/28/234 >> > > [9.2] https://lkml.org/lkml/2015/2/2/259 >> >> The additional patches that makes things somehow work involve tuning >> the PHY, >> this is an area I'm not familiar with >> >> -Mathias >> > > > I'm sorry, I should have said that this is the dmesg output with the > patches applied. Without them there is no output at all when I attach > an usb 3.0 device. > > Michael There are two dwc3 ports in the SoC : one for Gbit Ethernet another one for on-board GL3521 USB 3.0 hub controller. 3.10.x kernel odroid@odroid:~$ lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=s5p-ehci/3p, 480M 4.x kernel odroid@odroid:~$ lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M |__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M |__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M I fell that Ethernet driver r8152 is not getting registered to xhci-hcd to bus port 06 which lead to other ports to miss configure, some time the Ethernet port get register to bus port 04 Their is also a possibility that all the port are not getting proper power from the S2MPS11 PMIC and possible some reset of the phy is needed to reconfigure the exynos USB HSIC controller. Best Regards -Anand Moon -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |