Thank you for your time to guide me through. Julie. > -----Original Message----- > From: Alan Stern [mailto:stern@xxxxxxxxxxxxxxxxxxx] > Sent: Friday, June 12, 2009 12:25 PM > To: Julie Zhu > Cc: USB list > Subject: RE: periodic schedule enabled during usb_disconnect > > On Fri, 12 Jun 2009, Julie Zhu wrote: > > > Hi, Alan, > > > > I am sorry, I do not see why qh_completions() has anything to do with > > usb_disconnect(). > > It's a subtle connection. > > usb_disconnect() calls usb_disable_device(), which calls > usb_disable_endpoint() for every possible endpoint in the device. > > That routine calls usb_hcd_flush_endpoint(), which calls unlink1(), > which calls hcd->driver->urb_dequeue() -- which in this case is > ehci_urb_dequeue(). > > For interrupt endpoints, that routine calls intr_deschedule() followed > by qh_completions(). Voila! > > Alan Stern > This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
