On Tuesday 12 April 2005 2:53 pm, [EMAIL PROTECTED] wrote: > > I notice that ehci-hcd.c only waits up to 25ms after setting CMD_RESET > in the EHCI command register before timing out and giving up.
It should be waiting up to 250 msec, not just 25 msec ... > Is that 25ms based on observation, or is it actually specified > somewhere? I couldn't find anything in the EHCI 1.0 spec that says how > long a controller can take to finish a reset, and I've got a controller > that seems to be taking a little bit longer than that. I think the original idea was to pick something so ridiculously long that no hardware would want to get anywhere near that limit... :) Taking more than 250 msec to reset seems likely to reflect some kind of issue that needs fixing, either in hardware or software. It's an operation that shouldn't really take more than a couple milliseconds. - Dave ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
