diff options
author | Emmanuel Grumbach <emmanuel.grumbach@intel.com> | 2017-08-06 13:19:05 +0300 |
---|---|---|
committer | Luca Coelho <luciano.coelho@intel.com> | 2017-08-18 16:10:44 +0300 |
commit | 114db230d35442e6d3382adc8ac34c944b5cd0eb (patch) | |
tree | 3ab6f521965a043f21e99da318c7e23071f9e8f4 /drivers/net/wireless/intel/iwlwifi/mvm/debugfs.c | |
parent | 3edfb5f44b942f04b4fbbddb24d8866bbfb5d1a4 (diff) | |
download | linux-114db230d35442e6d3382adc8ac34c944b5cd0eb.tar.gz linux-114db230d35442e6d3382adc8ac34c944b5cd0eb.tar.bz2 linux-114db230d35442e6d3382adc8ac34c944b5cd0eb.zip |
iwlwifi: mvm: don't send BAR on flushed frames
When we flush a queue, the packets will have a 'failed'
status but we shouldn't send a BAR. This check was missing.
Because of that, when we got an ampdu_action with
IEEE80211_AMPDU_TX_STOP_FLUSH, we started the following
ping pong with the firmware:
1) Set the station as 'draining'
2) Get a failed Tx status (DRAINED)
3) Send a BAR because of the failed Tx status
(loop of 2 and 3)
This loop wasn't endless since the BAR isn't sent on a
queue that would trigger a "nested" BAR.
Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Diffstat (limited to 'drivers/net/wireless/intel/iwlwifi/mvm/debugfs.c')
0 files changed, 0 insertions, 0 deletions