From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Regression due to 020bbcb "usb: hub: Power-cycle on root-hub ports"
Date: Thu, 13 Jun 2013 16:03:31 -0600 [thread overview]
Message-ID: <51BA41B3.5070900@wwwdotorg.org> (raw)
In-Reply-To: <51BA3ECA.3070101@wwwdotorg.org>
(Sorry to those on to/cc; I'm resending this so it goes to the correct
mailing list)
Commit 020bbcb "usb: hub: Power-cycle on root-hub ports" causes a
regression on Tegra systems.
The first time "usb start" is executed, it appears to work correctly.
However, any subsequent time it is executed, it takes a long time, and
eventually fails to find any USB devices.
This situation can happen quite often; for example, if the user forgets
to plug in a USB device before booting, runs "usb start", realizes that,
then plugs it in and runs "usb start" again. This is compounded on at
least one of the Tegra boards, since CONFIG_PREBOOT is set to "usb
start" on systems (laptops/clamshells) which have built-in USB keyboards.
If I simply revert this patch, then everything works again. (Yes,
reverting requires fixing a small merge conflict.)
Do you have any idea what the problem can be? I'm tempted to simply ask
for the patch to be reverted since it causes a regression.
Thanks for any idea how to fix this!
next parent reply other threads:[~2013-06-13 22:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51BA3ECA.3070101@wwwdotorg.org>
2013-06-13 22:03 ` Stephen Warren [this message]
2013-06-30 16:38 ` [U-Boot] Regression due to 020bbcb "usb: hub: Power-cycle on root-hub ports" Marek Vasut
2013-07-01 13:49 ` Vivek Gautam
2013-07-01 16:41 ` Stephen Warren
2013-07-02 17:01 ` Vivek Gautam
2013-07-08 13:03 ` Marek Vasut
2013-07-08 13:25 ` Vivek Gautam
2013-07-08 15:58 ` Stephen Warren
2013-07-08 17:03 ` Marek Vasut
2013-07-08 18:03 ` Stephen Warren
2013-07-08 18:25 ` Marek Vasut
2013-07-08 18:28 ` Stephen Warren
2013-07-08 19:50 ` Marek Vasut
2013-07-08 19:53 ` Stephen Warren
2013-07-09 7:46 ` Vivek Gautam
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=51BA41B3.5070900@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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