aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>2016-09-20 04:22:07 -0400
committerKalle Valo <kvalo@qca.qualcomm.com>2016-09-28 05:47:14 -0400
commitb63b33ecafa5d00edbbb438c7e208392d5f4de23 (patch)
tree45f3e4aed494b37fd3419fb05beecae91f16188b
parent931eb6b7fee31f63d33fd5e1e62a60375fa6fb32 (diff)
ath10k: Ignore SWBA event for a vif if its marked for no beacon
Ignore processing further in SWBA event scheduled for a vif, if mac80211 has marked the particular vif for stop beaconing and brought the vdev down in 'ath10k_control_beaconing'. This should potentially avoid ath10k warning/error messages while running continuous wifi down/up with max number of vaps configured. Found this change during code walk through and going through other beacon configuration related functions in ath10k Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
-rw-r--r--drivers/net/wireless/ath/ath10k/wmi.c6
1 files changed, 6 insertions, 0 deletions
diff --git a/drivers/net/wireless/ath/ath10k/wmi.c b/drivers/net/wireless/ath/ath10k/wmi.c
index 38993d72f5e6..54df425bb0fc 100644
--- a/drivers/net/wireless/ath/ath10k/wmi.c
+++ b/drivers/net/wireless/ath/ath10k/wmi.c
@@ -3514,6 +3514,12 @@ void ath10k_wmi_event_host_swba(struct ath10k *ar, struct sk_buff *skb)
3514 continue; 3514 continue;
3515 } 3515 }
3516 3516
3517 /* mac80211 would have already asked us to stop beaconing and
3518 * bring the vdev down, so continue in that case
3519 */
3520 if (!arvif->is_up)
3521 continue;
3522
3517 /* There are no completions for beacons so wait for next SWBA 3523 /* There are no completions for beacons so wait for next SWBA
3518 * before telling mac80211 to decrement CSA counter 3524 * before telling mac80211 to decrement CSA counter
3519 * 3525 *