All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] usb: hub: fix power good delay timing
Date: Sun, 1 Jun 2014 19:20:18 +0200	[thread overview]
Message-ID: <201406011920.18729.marex@denx.de> (raw)
In-Reply-To: <5387A5CC.60509@wwwdotorg.org>

On Thursday, May 29, 2014 at 11:25:32 PM, Stephen Warren wrote:
> On 05/19/2014 02:21 PM, Stephen Warren wrote:
> > From: Stephen Warren <swarren@nvidia.com>
> > 
> > usb_hub_power_on() currently waits for the maximum of (a) the hub port's
> > power output to become good, (b) the max time the USB specification
> > allows a device to take to connect.
> > 
> > However, these two operations must occur in series rather than in
> > parallel. First, the power supply ramps up to the level required to
> > power the USB device, and then the device may take a certain amount of
> > time to connect (assert D+/D- pullups).
> > 
> > Related, the maximum time that a device has to assert pullups is 1s not
> > 100ms.
> > 
> > This is explained in "Connect Timing ECN.pdf", itself part of
> > usb_20_042814.zip from www.usb.org.
> 
> Marek, does this series look OK?

Applied both, thanks!

Best regards,
Marek Vasut

      reply	other threads:[~2014-06-01 17:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 20:21 [U-Boot] [PATCH 1/2] usb: hub: fix power good delay timing Stephen Warren
2014-05-19 20:21 ` [U-Boot] [PATCH 2/2] usb: hub: remove CONFIG_USB_HUB_MIN_POWER_ON_DELAY Stephen Warren
2014-06-03 16:17   ` Tim Harvey
2014-06-03 16:38     ` Stephen Warren
2014-06-03 17:38       ` Marek Vasut
2014-06-03 18:11       ` Tim Harvey
2014-05-29 21:25 ` [U-Boot] [PATCH 1/2] usb: hub: fix power good delay timing Stephen Warren
2014-06-01 17:20   ` Marek Vasut [this message]

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=201406011920.18729.marex@denx.de \
    --to=marex@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.