wilc1000: use wait_for_completion_interruptible_timeout for completion

The default driver implementation blocks the TXQ task until the upper
layer posts Tx packet. If the interface is idle, the thread will be
in waiting state forever which makes the kernel to think that the
task is hung.

Use wait_for_completion_interruptible_timeout() inplace of
wait_for_completion_timeout() to solve this issue.

Signed-off-by: Ajay Singh <ajay.kathat@microchip.com>
Signed-off-by: Sripad Balwadgi <Sripad.Balwadgi@microchip.com>

Author: ajaykathat

drivers/staging/wilc1000/netdev.c

@@ -37,22 +37,23 @@ static int debug_thread(void *arg)
 
 	while (1) {
 		int srcu_idx;
+		int ret;
 
 		if (!wl->initialized && !kthread_should_stop()) {
 			msleep(1000);
 			continue;
 		} else if (!wl->initialized) {
 			break;
 		}
-
-		if (wait_for_completion_timeout(&wl->debug_thread_started,
-						msecs_to_jiffies(6000))) {
+		ret = wait_for_completion_interruptible_timeout(
+			&wl->debug_thread_started, msecs_to_jiffies(6000));
+		if (ret > 0) {
 			while (!kthread_should_stop())
 				schedule();
 			pr_info("Exit debug thread\n");
 			return 0;
 		}
-		if (!debug_running)
+		if (!debug_running || ret == -ERESTARTSYS)
 			continue;
 
 		pr_debug("%s *** Debug Thread Running ***cnt[%d]\n", __func__,
@@ -393,7 +394,8 @@ static int wilc_txq_task(void *vp)
 		struct net_device *ndev = vif->ndev;
 
 		PRINT_INFO(ndev, TX_DBG, "txq_task Taking a nap\n");
-		wait_for_completion(&wl->txq_event);
+		if (wait_for_completion_interruptible(&wl->txq_event))
+			continue;
 		PRINT_INFO(ndev, TX_DBG, "txq_task Who waked me up\n");
 		if (wl->close) {
 			complete(&wl->txq_thread_started);