diff options
author | Luciano Coelho <luciano.coelho@intel.com> | 2014-01-13 17:43:00 (GMT) |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2014-02-04 20:48:06 (GMT) |
commit | 66e01cf99e0a9d0cbff21b0288c049654d5acf3e (patch) | |
tree | 260f0faa7f500757b98049ace42b7d34ab002a77 /arch/xtensa/mm | |
parent | b58e81e96a81c80886011ad87cdbe73585dec4f7 (diff) | |
download | linux-66e01cf99e0a9d0cbff21b0288c049654d5acf3e.tar.xz |
mac80211: only set CSA beacon when at least one beacon must be transmitted
A beacon should never have a Channel Switch Announcement information
element with a count of 0, because a count of 1 means switch just
before the next beacon. So, if a count of 0 was valid in a beacon, it
would have been transmitted in the next channel already, which is
useless. A CSA count equal to zero is only meaningful in action
frames or probe_responses.
Fix the ieee80211_csa_is_complete() and ieee80211_update_csa()
functions accordingly.
With a CSA count of 0, we won't transmit any CSA beacons, because the
switch will happen before the next TBTT. To avoid extra work and
potential confusion in the drivers, complete the CSA immediately,
instead of waiting for the driver to call ieee80211_csa_finish().
To keep things simpler, we also switch immediately when the CSA count
is 1, while in theory we should delay the switch until just before the
next TBTT.
Additionally, move the ieee80211_csa_finish() function to cfg.c,
where it makes more sense.
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Acked-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'arch/xtensa/mm')
0 files changed, 0 insertions, 0 deletions