On Wed, 29 Mar 2006 [EMAIL PROTECTED] wrote: > Hi Alan, > > Thanks for the prompt response. > > When an overcurrent condition occurs on a port, to which a device is > connected, my understanding is that power on that port will be turned > off and hence the device is disconnected. My query is whether khubd, > handles this device disconnect event as a USB_PORT_STAT_C_CONNECTION > feature? Looking at the current code, it is not very clear, whether > khubd handles this condition like an unplug. > > Pl. correct me if I'm wrong and clarify whether khubd treats it like an > unplug.
In response to USB_PORT_STAT_C_OVERCURRENT, khubd does nothing but clear the overcurrent-change feature and turn the port power back on. The hub should also report a connect-change status, which khubd will handle as an unplug. This is pretty theoretical. I don't know of anyone who has tested the code by actually creating an overcurrent situation. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
