From b3649f3bbfdb2686eceb40a629cef8d4d257f5fa Mon Sep 17 00:00:00 2001 From: Vitaly Kuzmichev Date: Fri, 11 Feb 2011 18:18:31 +0300 Subject: USB-CDC: handle interrupt after dropped pullup Disconnecting USB gadget with pending interrupt may cause its wrong handling in the next time when interface will be started again (especially actual for RNDIS). This interrupt may force the gadget to queue unexpected response before setup stage. Despite the fact that such interrupt handled after dropped pullup also may add pending response, this will not bring to any issues due to usb_ep_disable (which clears the queue) called on gadget unregistering. Signed-off-by: Vitaly Kuzmichev --- drivers/usb/gadget/ether.c | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'drivers/usb/gadget') diff --git a/drivers/usb/gadget/ether.c b/drivers/usb/gadget/ether.c index 6384869..0e7549d 100644 --- a/drivers/usb/gadget/ether.c +++ b/drivers/usb/gadget/ether.c @@ -1928,6 +1928,13 @@ void usb_eth_halt(struct eth_device *netdev) return; usb_gadget_disconnect(dev->gadget); + + /* Clear pending interrupt */ + if (dev->network_started) { + usb_gadget_handle_interrupts(); + dev->network_started = 0; + } + usb_gadget_unregister_driver(ð_driver); } -- cgit v1.1