diff options
| author | Arik Nemtsov <arik@wizery.com> | 2012-11-27 06:44:56 (GMT) |
|---|---|---|
| committer | Luciano Coelho <coelho@ti.com> | 2012-12-05 07:43:32 (GMT) |
| commit | b50a62bb39c66e6ed5f1f581bb32644936f08cf3 (patch) | |
| tree | 94d4d0d33107af0140b68fdd6642e61dc54c768e | |
| parent | 583f81644ab34a1314827a1dffc7fc8fbad7dc0f (diff) | |
| download | linux-b50a62bb39c66e6ed5f1f581bb32644936f08cf3.tar.xz | |
wlcore: initialize per-link FW freed blocks correctly
When a link is allocated, sometimes the "freed packets" counter in FW
is non zero, but we always assumed it is. This caused us to incorrectly
account FW allocated blocks in some cases.
When operating in AP mode, this bug caused some stations to never
come back from PSM.
Signed-off-by: Arik Nemtsov <arik@wizery.com>
Signed-off-by: Luciano Coelho <coelho@ti.com>
| -rw-r--r-- | drivers/net/wireless/ti/wlcore/cmd.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/drivers/net/wireless/ti/wlcore/cmd.c b/drivers/net/wireless/ti/wlcore/cmd.c index 38243aa..e00d64b 100644 --- a/drivers/net/wireless/ti/wlcore/cmd.c +++ b/drivers/net/wireless/ti/wlcore/cmd.c @@ -322,6 +322,10 @@ int wl12xx_allocate_link(struct wl1271 *wl, struct wl12xx_vif *wlvif, u8 *hlid) __set_bit(link, wl->links_map); __set_bit(link, wlvif->links_map); spin_unlock_irqrestore(&wl->wl_lock, flags); + + /* take the last "freed packets" value from the current FW status */ + wl->links[link].prev_freed_pkts = + wl->fw_status_2->counters.tx_lnk_free_pkts[link]; *hlid = link; return 0; } |