diff options
| author | Emmanuel Grumbach <emmanuel.grumbach@intel.com> | 2022-01-28 14:30:56 +0200 |
|---|---|---|
| committer | Kalle Valo <kvalo@kernel.org> | 2022-02-03 10:24:50 +0200 |
| commit | 7cf800f46e07e6b75a43036c4389d6ca717fd017 (patch) | |
| tree | b737d8fc6f4b2042033d818ae82aeba3df8876cb /crypto/sha3_generic.c | |
| parent | 44bf7c4667efe10390aa59eda39833a9a0439b5b (diff) | |
| download | linux-7cf800f46e07e6b75a43036c4389d6ca717fd017.tar.gz | |
iwlwifi: mvm: don't feed the hardware RFKILL into iwlmei
iwlmei can trigger a hardware RFKILL when the CSME firmware
does not want the host to touch the device.
But then, iwlmvm reports RFKILL which makes cfg80211 update
iwlmvm about RFKILL. iwlmvm then thinks there is a change in
the _software_ rfkill and it calls rfkill_blocked() to fetch
the RFKILL state. This returns that RFKILL is blocked (because
of iwlmei) and iwlmvm tells iwlmei that _software_ RFKILL is
asserted.
This is a bug of course.
Fix this by checking explicitly the software RFKILL state and
not the overall RFKILL state.
Fixes: 7ce1f2157e14 ("iwlwifi: mvm: read the rfkill state and feed it to iwlmei")
Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Fixes: 7ce1f2157e14 ("iwlwifi: mvm: read the rfkill state and feed it to iwlmei")
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Signed-off-by: Kalle Valo <kvalo@kernel.org>
Link: https://lore.kernel.org/r/iwlwifi.20220128142706.f293861a3f92.I9553d27df1de6fd5756a43ea5f8b89d06fa1a6f2@changeid
Diffstat (limited to 'crypto/sha3_generic.c')
0 files changed, 0 insertions, 0 deletions