diff options
| author | Emmanuel Grumbach <emmanuel.grumbach@intel.com> | 2015-12-20 09:45:40 +0300 |
|---|---|---|
| committer | Emmanuel Grumbach <emmanuel.grumbach@intel.com> | 2016-01-07 20:01:09 +0300 |
| commit | a1cdb1c59c8c203de2731fc6910598ed19c97e41 (patch) | |
| tree | d1d80f978cfd5c40c69b0564baf9049c4dd71890 /tools/hv | |
| parent | e5d15cb530082cc13a6c9457eddd6f75b0f4de65 (diff) | |
| download | linux-a1cdb1c59c8c203de2731fc6910598ed19c97e41.tar.xz | |
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
CC: <stable@vger.kernel.org> [4.3+]
Reported-by: Bogdan Bogush <bogdan.s.bogush@gmail.com>
Fixes=fa9f3281cbb1 ("iwlwifi: pcie: lock start_hw / start_fw / stop_device")
Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Diffstat (limited to 'tools/hv')
0 files changed, 0 insertions, 0 deletions