mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-28 11:18:45 +07:00
a1cdb1c59c
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> |
||
---|---|---|
.. | ||
agn.h | ||
calib.c | ||
calib.h | ||
commands.h | ||
debugfs.c | ||
dev.h | ||
devices.c | ||
led.c | ||
led.h | ||
lib.c | ||
mac80211.c | ||
main.c | ||
Makefile | ||
power.c | ||
power.h | ||
rs.c | ||
rs.h | ||
rx.c | ||
rxon.c | ||
scan.c | ||
sta.c | ||
tt.c | ||
tt.h | ||
tx.c | ||
ucode.c |