diff options
| author | Golan Ben Ami <golan.ben.ami@intel.com> | 2016-12-11 17:12:47 +0200 |
|---|---|---|
| committer | Luca Coelho <luciano.coelho@intel.com> | 2017-02-08 17:54:21 +0200 |
| commit | 2b18824a5d1eae58946e3c8a60d48f0b1ff32265 (patch) | |
| tree | 2660ad752a3dae7935fb4ca55a5182621b9ff862 /include/scsi | |
| parent | 43d59a4ce78b6460b32076ec7ac821fd8678cdc2 (diff) | |
iwlwifi: pcie: set STATUS_RFKILL immediately after interrupt
Currently, when getting a RFKILL interrupt, the transport enters a flow
in which it stops the device, disables other interrupts, etc. After
stopping the device, the transport resets the hw, and sleeps. During
the sleep, a context switch occurs and host commands are sent by upper
layers (e.g. mvm) to the fw. This is possible since the op_mode layer
and the transport layer hold different mutexes.
Since the STATUS_RFKILL bit isn't set, the transport layer doesn't
recognize that RFKILL was toggled on, and no commands can actually be
sent, so it enqueues the command to the tx queue and sets a timer on
the queue.
After switching context back to stopping the device, STATUS_RFKILL is
set, and then the transport can't send the command to the fw.
This eventually results in a queue hang.
Fix this by setting STATUS_RFKILL immediately when
the interrupt is fired.
Signed-off-by: Golan Ben-Ami <golan.ben.ami@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Diffstat (limited to 'include/scsi')
0 files changed, 0 insertions, 0 deletions