From: balbi@kernel.org (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422
Date: Fri, 07 Oct 2016 10:42:21 +0300 [thread overview]
Message-ID: <87y420wqoy.fsf@linux.intel.com> (raw)
In-Reply-To: <1475771380.22019.5.camel@mniewoehner.de>
Hi,
Michael Niew?hner <linux@mniewoehner.de> writes:
>> The clocks are same across working/non-working.
>> Is it possible to bisect the commit that's causing hang for 4.8x ?
>
>
> [c499ff71ff2a281366c6ec7a904c547d806cbcd1] usb: dwc3: core: re-factor init and exit paths
> This patch causes both the hang on reboot and the lsusb hang.
How to reproduce? Why don't we see this on x86 and TI boards? I'm
guessing this is failed bisection, as I can't see anything in that
commit that would cause reboot hang. Also, that code path is *NOT*
executed when you run lsusb.
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161007/291447b6/attachment.sig>
next prev parent reply other threads:[~2016-10-07 7:42 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
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 [this message]
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=87y420wqoy.fsf@linux.intel.com \
--to=balbi@kernel.org \
--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).