From: linux@mniewoehner.de (Michael Niewöhner)
To: linux-arm-kernel@lists.infradead.org
Subject: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422
Date: Mon, 29 Aug 2016 13:05:30 +0200 [thread overview]
Message-ID: <1472468730.4925.3.camel@mniewoehner.de> (raw)
In-Reply-To: <57C41582.1030604@linux.intel.com>
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@mniewoehner.de> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 630 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160829/c0397bee/attachment.sig>
next prev parent reply other threads:[~2016-08-29 11:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 20:04 PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422 Michael Niewöhner
2016-08-29 7:28 ` Felipe Balbi
2016-08-29 10:59 ` Mathias Nyman
2016-08-29 11:05 ` Michael Niewöhner [this message]
2016-08-30 5:02 ` Anand Moon
2016-09-20 21:19 ` Michael Niewöhner
2016-10-03 13:08 ` Michael Niewöhner
2016-10-04 6:02 ` Vivek Gautam
[not found] ` <1475578687.1912.28.camel@mniewoehner.de>
2016-10-04 12:02 ` Vivek Gautam
2016-10-04 15:09 ` Anand Moon
2016-10-05 4:45 ` Vivek Gautam
2016-10-05 7:48 ` Anand Moon
2016-10-06 16:29 ` Michael Niewöhner
2016-10-07 7:42 ` Felipe Balbi
2016-10-07 20:26 ` Michael Niewöhner
2016-10-16 14:19 ` Michael Niewöhner
2016-10-17 8:08 ` Felipe Balbi
2016-10-17 9:51 ` Vivek Gautam
2016-10-18 12:20 ` Michael Niewöhner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1472468730.4925.3.camel@mniewoehner.de \
--to=linux@mniewoehner.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).