diff options
author | Johannes Berg <johannes.berg@intel.com> | 2017-04-25 13:41:20 +0200 |
---|---|---|
committer | Luca Coelho <luciano.coelho@intel.com> | 2017-06-22 23:13:01 +0200 |
commit | 326477e4858cd6b1e0e067ecf2d6a8252ef41994 (patch) | |
tree | 89dc6cdc403c4ada71301f0ea6d54fc5f5214111 /drivers/net/ieee802154 | |
parent | iwlwifi: mvm: don't warn in queue sync on RF-kill (diff) | |
download | linux-326477e4858cd6b1e0e067ecf2d6a8252ef41994.tar.xz linux-326477e4858cd6b1e0e067ecf2d6a8252ef41994.zip |
iwlwifi: pcie: don't report RF-kill enabled while shutting down
When toggling the RF-kill pin quickly in succession, the driver can
get rather confused because it might be in the process of shutting
down, expecting all commands to go through quickly due to rfkill,
but the transport already thinks the device is accessible again,
even though it previously shut it down. This leads to bugs, and I
even observed a kernel panic.
Avoid this by making the PCIe code only report that the radio is
enabled again after the higher layers actually decided to shut it
off.
This also pulls out this common RF-kill checking code into a common
function called by both transport generations and also moves it to
the direct method - in the internal helper we don't really care
about the RF-kill status anymore since we won't report it up until
the stop anyway.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Diffstat (limited to 'drivers/net/ieee802154')
0 files changed, 0 insertions, 0 deletions