wlcore: fix occasional AP TX stop after recovery
authorVictor Goldenshtein <victorg@ti.com>
Sun, 12 May 2013 09:35:31 +0000 (12:35 +0300)
committerLuciano Coelho <coelho@ti.com>
Mon, 17 Jun 2013 09:14:29 +0000 (12:14 +0300)
commit5cbba2d48ac3d493d2337414806c718370edcf8a
tree679694f3366a7b6d1bba7970243ca44759480b0e
parent2baf53c6e35ea25aaa21486dab023eb3d901611e
wlcore: fix occasional AP TX stop after recovery

The fw_status wasn't zeroed during allocation, resulting
in uninitialized var usage, and finally causing AP
traffic stop after recovery.

The wrong value in fw_status_2->counters.tx_lnk_free_pkts
led to a bad lnk->allocated_pkts calculation in
wlcore_fw_status(), causing wl18xx_lnk_low_prio() to return
FALSE (lnk->allocated_pkts > thold).
This eventually blocked the link in wlcore_tx_work_locked(),
as wl1271_skb_dequeue() continuously returned NULL.

Fix it by zeroing wl->fw_status_1/2 during allocation.

Signed-off-by: Victor Goldenshtein <victorg@ti.com>
Signed-off-by: Eliad Peller <eliad@wizery.com>
Signed-off-by: Luciano Coelho <coelho@ti.com>
drivers/net/wireless/ti/wlcore/main.c