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 <vkuzmichev@mvista.com>

diff --git a/drivers/usb/gadget/ether.c b/drivers/usb/gadget/ether.c
index 638486998d177f68ea5b128db64c351979a0e079..0e7549d6b163ca5691fcae2aadcf77b3f83d5d59 100644 (file)
--- 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(&eth_driver);
 }