Dave:
What do you think of the idea of taking all the code to create and
register root hub devices out of all the HCDs and centralizing it in
usb_add_hcd? It could go right after the call to hcd->driver->start().
On the face of it this should be a simple change. But there are two
aspects I'm not certain about:
Both ehci-hcd.c and ohci-hcd.c include the root-hub code in
two different pathways. It appears that the restart paths
(every time except the first) can pretty much ignore the
root hub. Is that correct? (But then why does ehci-hcd set
udev->state to USB_STATE_CONFIGURED?)
ohci-hcd and sl811-hcd include a call to hub_set_power_budget.
It's not clear where the call should end up. Should the
power-budget value be stored in the struct usb_hcd, where
usb_add_hcd will be able to see it?
Alan Stern
-------------------------------------------------------
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
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
