iwlwifi: mvm: fix WoWLAN RF-kill bug
The RF-kill wakeup trigger flag is set in the wrong command, which means it won't work. Also fix the comment in the TCP wakeup trigger code -- the firmware was changed to look at all the different trigger flags. Reviewed-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
This commit is contained in:
parent
b926926234
commit
6039f3e196
1 changed files with 3 additions and 7 deletions
|
@ -866,17 +866,13 @@ int iwl_mvm_suspend(struct ieee80211_hw *hw, struct cfg80211_wowlan *wowlan)
|
||||||
cpu_to_le32(IWL_WOWLAN_WAKEUP_PATTERN_MATCH);
|
cpu_to_le32(IWL_WOWLAN_WAKEUP_PATTERN_MATCH);
|
||||||
|
|
||||||
if (wowlan->rfkill_release)
|
if (wowlan->rfkill_release)
|
||||||
d3_cfg_cmd.wakeup_flags |=
|
wowlan_config_cmd.wakeup_filter |=
|
||||||
cpu_to_le32(IWL_WOWLAN_WAKEUP_RF_KILL_DEASSERT);
|
cpu_to_le32(IWL_WOWLAN_WAKEUP_RF_KILL_DEASSERT);
|
||||||
|
|
||||||
if (wowlan->tcp) {
|
if (wowlan->tcp) {
|
||||||
/*
|
/*
|
||||||
* The firmware currently doesn't really look at these, only
|
* Set the "link change" (really "link lost") flag as well
|
||||||
* the IWL_WOWLAN_WAKEUP_LINK_CHANGE bit. We have to set that
|
* since that implies losing the TCP connection.
|
||||||
* reason bit since losing the connection to the AP implies
|
|
||||||
* losing the TCP connection.
|
|
||||||
* Set the flags anyway as long as they exist, in case this
|
|
||||||
* will be changed in the firmware.
|
|
||||||
*/
|
*/
|
||||||
wowlan_config_cmd.wakeup_filter |=
|
wowlan_config_cmd.wakeup_filter |=
|
||||||
cpu_to_le32(IWL_WOWLAN_WAKEUP_REMOTE_LINK_LOSS |
|
cpu_to_le32(IWL_WOWLAN_WAKEUP_REMOTE_LINK_LOSS |
|
||||||
|
|
Loading…
Reference in a new issue