[PATCH 3/3] usb: use ep-specific pwrgood delay

Steffen Trumtrar s.trumtrar at pengutronix.de
Thu Aug 30 10:12:27 EDT 2012


Hi Eric,

>On Thu, Aug 30, 2012 at 03:59:32PM +0200, Eric Bénard wrote:
> Hi Steffen,
> 
> Le Thu, 30 Aug 2012 15:26:31 +0200,
> Steffen Trumtrar <s.trumtrar at pengutronix.de> a écrit :
> > Where does your 50ms come from? From the debug messages of the usb-tool?
> from a printf of bPwrOn2PwrGood
> 
> > It has the same factor of times 2.
> yes, so in the end the hub is supposed to need 100ms to enable power.

Okay. So you have an equal setting like me.

> 
> > Have you tried hardcoding mdelay(100)?
> yes -> doesn't work (see previous patch I sent 2 days ago on the same
> subject).

Ah, okay.

> > I first thought about doing it the same way linux does it and use
> > max(pwrgood, 100). But 100ms minimum wouldn't help you either.
> > I don't really like the idea of just guessing a value. But if necessary,
> > I'm surely willing to change this patch.
> 
> with Linux's 100ms that works fine on the same board (under Linux). So
> I'll check the if the mdelay(100) in barebox is really a 100ms timing
> because the problem's root may be here !

As both, barebox and linux, reset the hub and wait, it seems like the root
of the problem, yes.

Greetings
Steffen


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



More information about the barebox mailing list