FAILED: patch "[PATCH] iwlwifi: dvm: fix WoWLAN" failed to apply to 4.4-stable tree
Subsystems (2)
[email protected]
maintainerThe patch below does not apply to the 4.4-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
Quoted 1 line
From
a1cdb1c59c8c203de2731fc6910598ed19c97e41Mon Sep 17 00:00:00 2001
From: Emmanuel Grumbach <[email protected]>
Date: Sun, 20 Dec 2015 08:45:40 +0200
Subject: [PATCH] iwlwifi: dvm: fix WoWLAN
My commit below introduced a mutex in the transport to prevent concurrent operations. To do so, it added a flag (is_down) to make sure the transport is in the right state. This uncoverred an bug that didn't cause any harm until
now: iwldvm calls stop_device and then starts the firmware without calling start_hw in between. While this flow is fine from the device configuration point of view (register, etc...), it is now forbidden by the new is_down flag.
This led to this error to appear:
iwlwifi 0000:05:00.0: Can't start_fw since the HW hasn't been started and the suspend would fail.
This fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=109591
Fixes=fa9f3281cbb1 ("iwlwifi: pcie: lock start_hw / start_fw / stop_device")
drivers/net/wireless/intel/iwlwifi/dvm/lib.c +3 -0
@@ -1154,6 +1154,9 @@ int iwlagn_suspend(struct iwl_priv *priv, struct cfg80211_wowlan *wowlan) priv->ucode_loaded = false;iwl_trans_stop_device (priv->trans); + ret =iwl_trans_start_hw (priv->trans); +if (ret) + goto out; priv->wowlan = true;