From: Felipe Balbi <balbi@kernel.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc\@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Kukjin Kim <kgene@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [BUG] Regression, usb-dwc3 not working, Odroid XU3, usb 3.0
Date: Mon, 04 Jul 2016 14:33:31 +0300 [thread overview]
Message-ID: <87shvpljsk.fsf@linux.intel.com> (raw)
In-Reply-To: <577A47D3.7020900@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
Hi,
Krzysztof Kozlowski <k.kozlowski@samsung.com> writes:
> Hi,
>
>
> Since three recent next releases (first on 20160630), on Odroid XU3 board
> the USB 3.0 host port (the only one) stopped working.
>
> This is a "samsung,exynos5250-dwusb3" (drivers/usb/dwc3/dwc3-exynos.c).
>
> Two issues here:
> 1. The port does not show up as USB 3.0 device.
> This one device is missing:
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>
> 2. The port does not work even for 2.0 devices (I didn't test 1.0).
>
>
> config: exynos_defconfig (ARM)
> DTS: exynos5422-odroidxu3.dts
apply [1] and try again. That commit is already in greg/usb-testing [2]
and it should trickle down to usb-next shortly.
[1] https://marc.info/?l=linux-usb&m=146728795330915&w=2
[2] https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/?h=usb-testing&id=322832f2f19e04c866a0ce4bdac8cff8e695f2b3
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-07-04 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 11:26 [BUG] Regression, usb-dwc3 not working, Odroid XU3, usb 3.0 Krzysztof Kozlowski
2016-07-04 11:33 ` Felipe Balbi [this message]
2016-07-04 11:39 ` Krzysztof Kozlowski
2016-07-04 11:43 ` Felipe Balbi
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=87shvpljsk.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.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).