On Thu, 23 Mar 2006, David Brownell wrote: > On Monday 20 March 2006 8:59 am, Alan Stern wrote: > > There are other times when the UDC driver might not disable endpoints, > > however. For example, when the cable is unplugged (a disconnect event). > > The gadget API doesn't specify whether endpoints are automatically > > disabled by the UDC driver when a disconnect occurs... > > Actually, that's implicit in the usb_ep_enable() writeup: > > while it is enabled, an > endpoint may be used for i/o until the driver receives a disconnect() from > the host or until the endpoint is disabled.
I would say that it's not even implicit here that the UDC driver has to disable endpoints when a disconnect occurs. But I agree that rewording would help. > Though that could stand to be re-worded, since it's not actually the host > which provides the disconnect notification, it's the transceiver (which > detects VBUS dropping below a threshold of 0.2V or somesuch). And more to the point, the gadget driver doesn't receive its disconnect() call from the host, the transceiver, or any other piece of hardware. The call comes from the device controller driver. 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
