tree 801ae03ac461b85af2011baa205baf1e9c073377
parent a3f668d218f381ffb36a6334425ba09ef5a33b7f
author Michal Kazior <michal.kazior@tieto.com> 1414660965 -0700
committer Ke Dong <kedong@google.com> 1414717374 -0700

Michal Kazior michal.kazior at tieto.com
Wed Apr 9 06:48:48 EDT 2014

Each WMI management Tx consumes 1 HTC Tx credit
and doesn't replenish it until the frame is
actually transmitted out of firmware's Tx queues.

If associated client was asleep and has gone out
of range then unicast frames won't be released for
FW/HW queues for a while (10 seconds per
observation). This means that if more management
frames are queued then HTC Tx credits are drained
to 0 and no other commands can be submitted
including beacons and peer removal.

This could in turn result in clients disconnecting
due to their beacon loss and may trigger spurious
sta kickouts because wmi peer removal command may
never reach firmware during disassociation.

This could happen, e.g. when disconnecting
client (hostapd inactivity) that has gone away
while asleep when acting as AP.

As a workaround flush frames that can potentialy
get stuck in FW Tx queues.

Change-Id: I3a80c1ec4bab346197d398fc3bc7376da2e35f15
Signed-off-by: Michal Kazior <michal.kazior at tieto.com>