public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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: Mon, 01 Jul 2013 10:41:53 -0600	[thread overview]
Message-ID: <51D1B151.4010806@wwwdotorg.org> (raw)
In-Reply-To: <CAFp+6iF_9zAi1htWyJWnSrFom-=yYQfCJjtN63wHa+n=ieYGbw@mail.gmail.com>

On 07/01/2013 07:49 AM, Vivek Gautam wrote:
> Hi Marek,
> 
> 
> On Sun, Jun 30, 2013 at 10:08 PM, Marek Vasut <marex@denx.de> wrote:
>> Dear Stephen Warren,
>>
>>> (Sorry to those on to/cc; I'm resending this so it goes to the correct
>>> mailing list)
> 
> Dear Stephen,
> sorry for the delay in responding to this.
> 
>>>
>>> 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!
>>
>> BUMP? Vivek, any ideas? Otherwise I'm reverting this.
...
> There's one BUG that i could see in " 0bf796f " commit.
> Now that we parallelized the sequence to power cycle ports, so if
> get_port_status for any port failed,
> it returns from hub_power_on() and not power-on any of the port.
> 
> Below is the change i suggest.
...
> can you please confirm if you problem is related to this BUG in the
> sequence of power-cycling the ports.

I applied that change, and it does not solve the problem on Tegra, nor
do I see any of the messages that were changed from debug to printf.
Below is the log:

U-Boot 2013.04-00281-g0e8ef51 (Jul 01 2013 - 10:33:36)

TEGRA20
Board: NVIDIA Seaboard
DRAM:  1 GiB
NAND:  512 MiB
MMC:   Tegra SD/MMC: 0, Tegra SD/MMC: 1
In:    tegra-kbc
Out:   lcd
Err:   lcd
Net:   Net Initialization Skipped
No ethernet found.
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
USB1:   USB EHCI 1.00
scanning bus 1 for devices... 2 USB Device(s) found
USB2:   lowlevel init failed
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices...
Warning: asx0 using MAC address from net device
1 Ethernet Device(s) found
Hit any key to stop autoboot:  0


Tegra20 (SeaBoard) # usb start
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
USB1:   USB EHCI 1.00
scanning bus 1 for devices... 1 USB Device(s) found

(there's a much longer pause when scanning this bus every time except
the very first)

USB2:   lowlevel init failed
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found


Tegra20 (SeaBoard) # usb start
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
USB1:   USB EHCI 1.00
scanning bus 1 for devices... 1 USB Device(s) found
USB2:   lowlevel init failed
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found

  reply	other threads:[~2013-07-01 16:41 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 ` [U-Boot] Regression due to 020bbcb "usb: hub: Power-cycle on root-hub ports" Stephen Warren
2013-06-30 16:38   ` Marek Vasut
2013-07-01 13:49     ` Vivek Gautam
2013-07-01 16:41       ` Stephen Warren [this message]
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=51D1B151.4010806@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