I haev some questions concerning usb_physical_reset_device :
* Why isn't this function exported like usb_reset_device is ?
The fourth patch of that short series of mine exports it, but renames it "__usb_reset_device" to match most other locked/unlocked call pairs in Linux.
* Why does the use of the semaphore locks kernel inside this
function before the usb_set_address command ? Is there a patch for
it ?
Only one device may have address 0 on a bus at a time, and that lock is what makes sure that's true.
Why are you even noticing that lock? The third of those patches reduced its scope so that it's never held during probe() calls. That's important for deadlock removal.
And that fourth patch shrank the lock scope even further, so only hub_port_init() even sees it.
- Dave
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
