Coverage is handled by modifying firmware state, and the driver stores
the values the first time it is set. When we reset this state might be lost
so it will be reloaded from the firmware. We set the coverage back to 0
so the reloaded value will be the default again.
We also remove a check which can fail incorrectly.
* A scan, especially if we have to do both active and passive, essentially mutes
the radio to AREDN traffic for 10-20 seconds, which isn't good. If the radio is completely
deaf then it doesn't matter, but particularly on the 9K radios we do this when
things are looking a bit dodgy, though not deaf.
* Provide hook to reset ath9k from userspace. This hook is attributed to:
Linus Lüssing <ll@simonwunderlich.de>
* User /sys reset hooks rather than iw scan
For some reason, there was code in the driver to block the setting of
the coverage when a previous setting wasn't a particular value.
It's unclear what this was trying to achieve or prevent, but it stopped AC
devices operating efficiently (by a factor of 10x or more).
There's a bug where 2.4GHz channels will associate incorrectly with other 2.4 channels
even though they are on different frequencies. The problem appears to be triggered during
scans when scan probes are sent and received on many different frequencies, but are then
reported as as they arrive as if they come from the selected frequency of the device, causing
incorrect stations to be created. This can only occur for IBSS (adhoc) mode, when the
IBSS frequency is fixed, and when the SSID is also fixed. We do all this for AREDN.
Fortunately these probe contains (but *only* on 2.4 GHz) the actual frequency of the sending
device, so we can avoid incorrectly creating stations which are not really a match.
This situation does not seem to happen on 5GHz channels.
e Please enter the commit message for your changes. Lines starting