From: Alexey Orishko Date: Wed, 14 Mar 2012 04:00:24 +0000 (+0000) Subject: usbnet: use netif_tx_wake_queue instead of netif_start_queue X-Git-Tag: v3.4-rc1~177^2~44 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=1aa9bc5b2f4cf8c48944fb9a607bf1dd674e2c10;p=profile%2Fivi%2Fkernel-adaptation-intel-automotive.git usbnet: use netif_tx_wake_queue instead of netif_start_queue If host is going to autosuspend function with two interfaces and if IP packet has arrived in-between of two usbnet_suspend() callbacks, i.e usbnet_resume() is called in-between, tx data flow is stopped. When autosuspend timer expires and device is put to autosuspend again, tx queue is waked up and data can be sent again. This behavior might be repeated several times in a row. Tested on Intel/ARM. Reviewed-by: Sjur Brændeland Tested-by: Dmitry Tarnyagin Signed-off-by: Alexey Orishko Acked-by: Oliver Neukum Signed-off-by: David S. Miller --- diff --git a/drivers/net/usb/usbnet.c b/drivers/net/usb/usbnet.c index 83dcc53..5394b4e 100644 --- a/drivers/net/usb/usbnet.c +++ b/drivers/net/usb/usbnet.c @@ -1535,7 +1535,7 @@ int usbnet_resume (struct usb_interface *intf) if (test_bit(EVENT_DEV_OPEN, &dev->flags)) { if (!(dev->txq.qlen >= TX_QLEN(dev))) - netif_start_queue(dev->net); + netif_tx_wake_all_queues(dev->net); tasklet_schedule (&dev->bh); } }