This patch fixes an issue with rx processing function where we were
decrementing rx_pending count twice.

Patch also queues correct main_work item when rx_pending count reaches
low watermark.

Signed-off-by: Avinash Patil <[email protected]>
Signed-off-by: Cathy Luo <[email protected]>
---
 drivers/net/wireless/mwifiex/main.c | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/drivers/net/wireless/mwifiex/main.c 
b/drivers/net/wireless/mwifiex/main.c
index be52189..d5070c4 100644
--- a/drivers/net/wireless/mwifiex/main.c
+++ b/drivers/net/wireless/mwifiex/main.c
@@ -130,7 +130,6 @@ static int mwifiex_process_rx(struct mwifiex_adapter 
*adapter)
 {
        unsigned long flags;
        struct sk_buff *skb;
-       bool delay_main_work = adapter->delay_main_work;
 
        spin_lock_irqsave(&adapter->rx_proc_lock, flags);
        if (adapter->rx_processing || adapter->rx_locked) {
@@ -145,10 +144,9 @@ static int mwifiex_process_rx(struct mwifiex_adapter 
*adapter)
        while ((skb = skb_dequeue(&adapter->rx_data_q))) {
                atomic_dec(&adapter->rx_pending);
                if (adapter->delay_main_work &&
-                   (atomic_dec_return(&adapter->rx_pending) <
-                    LOW_RX_PENDING)) {
+                   (atomic_read(&adapter->rx_pending) < LOW_RX_PENDING)) {
                        adapter->delay_main_work = false;
-                       queue_work(adapter->rx_workqueue, &adapter->rx_work);
+                       queue_work(adapter->workqueue, &adapter->main_work);
                }
                mwifiex_handle_rx_packet(adapter, skb);
        }
@@ -156,8 +154,6 @@ static int mwifiex_process_rx(struct mwifiex_adapter 
*adapter)
        adapter->rx_processing = false;
        spin_unlock_irqrestore(&adapter->rx_proc_lock, flags);
 
-       if (delay_main_work)
-               queue_work(adapter->workqueue, &adapter->main_work);
 exit_rx_proc:
        return 0;
 }
-- 
1.8.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to