iwlwifi: mvm: handle async temperature notification with unlocked mutex

Use RX_HANDLER_ASYNC_UNLOCKED instead of unlock and re-lock
the mutex independently.

Signed-off-by: Chaya Rachel Ivgi <chaya.rachel.ivgi@intel.com>
Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>

1 files changed, 0 insertions, 9 deletions

diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/tt.c b/drivers/net/wireless/intel/iwlwifi/mvm/tt.c
index f1f28255a3a6..8d27137a9284 100644
--- a/drivers/net/wireless/intel/iwlwifi/mvm/tt.c
+++ b/drivers/net/wireless/intel/iwlwifi/mvm/tt.c
@@ -204,20 +204,11 @@ void iwl_mvm_temp_notif(struct iwl_mvm *mvm, struct iwl_rx_cmd_buffer *rxb)
         if (WARN_ON(ths_crossed >= IWL_MAX_DTS_TRIPS))
                 return;
 
-        /*
-         * We are now handling a temperature notification from the firmware
-         * in ASYNC and hold the mutex. thermal_notify_framework will call
-         * us back through get_temp() which ought to send a SYNC command to
-         * the firmware and hence to take the mutex.
-         * Avoid the deadlock by unlocking the mutex here.
-         */
         if (mvm->tz_device.tzone) {
                 struct iwl_mvm_thermal_device *tz_dev = &mvm->tz_device;
 
-                mutex_unlock(&mvm->mutex);
                 thermal_notify_framework(tz_dev->tzone,
                                          tz_dev->fw_trips_index[ths_crossed]);
-                mutex_lock(&mvm->mutex);
         }
 #endif /* CONFIG_THERMAL */
 }