diff options
| author | Daniel Gabay <[email protected]> | 2024-10-10 11:05:03 +0000 |
|---|---|---|
| committer | Johannes Berg <[email protected]> | 2024-10-25 15:53:29 +0000 |
| commit | 9715246ca0bfc9feaec1b4ff5b3d38de65a7025d (patch) | |
| tree | 8f7a8d24b9010eea9632cd9671e3c1cbbed58b4c /drivers/net/wireless/intel/iwlwifi/mvm/d3.c | |
| parent | wifi: iwlwifi: mvm: really send iwl_txpower_constraints_cmd (diff) | |
| download | kernel-9715246ca0bfc9feaec1b4ff5b3d38de65a7025d.tar.gz kernel-9715246ca0bfc9feaec1b4ff5b3d38de65a7025d.zip | |
wifi: iwlwifi: mvm: Use the sync timepoint API in suspend
When starting the suspend flow, HOST_D3_START triggers an _async_
firmware dump collection for debugging purposes. The async worker
may race with suspend flow and fail to get NIC access, resulting in
the following warning:
"Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff)"
Fix this by switching to the sync version to ensure the dump
completes before proceeding with the suspend flow, avoiding
potential race issues.
Signed-off-by: Daniel Gabay <[email protected]>
Signed-off-by: Miri Korenblit <[email protected]>
Link: https://patch.msgid.link/20241010140328.9aae318cd593.I4b322009f39489c0b1d8893495c887870f73ed9c@changeid
Signed-off-by: Johannes Berg <[email protected]>
Diffstat (limited to 'drivers/net/wireless/intel/iwlwifi/mvm/d3.c')
| -rw-r--r-- | drivers/net/wireless/intel/iwlwifi/mvm/d3.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/d3.c b/drivers/net/wireless/intel/iwlwifi/mvm/d3.c index 49a6aff42376..244ca8cab9d1 100644 --- a/drivers/net/wireless/intel/iwlwifi/mvm/d3.c +++ b/drivers/net/wireless/intel/iwlwifi/mvm/d3.c @@ -1398,7 +1398,9 @@ int iwl_mvm_suspend(struct ieee80211_hw *hw, struct cfg80211_wowlan *wowlan) iwl_mvm_pause_tcm(mvm, true); + mutex_lock(&mvm->mutex); iwl_fw_runtime_suspend(&mvm->fwrt); + mutex_unlock(&mvm->mutex); return __iwl_mvm_suspend(hw, wowlan, false); } |