From: "Zhang, Rui" <rui.zhang@intel.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"hpausten@protonmail.com" <hpausten@protonmail.com>
Cc: "kvalo@kernel.org" <kvalo@kernel.org>,
"Greenman, Gregory" <gregory.greenman@intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>,
"Stern, Avraham" <avraham.stern@intel.com>
Subject: Re: [PATCH] wifi: iwlwifi: mvm: enable thermal zone only when firmware is loaded
Date: Sun, 16 Jul 2023 13:45:05 +0000 [thread overview]
Message-ID: <7a45b2ed16645523a13d69290b27031f607b214a.camel@intel.com> (raw)
In-Reply-To: <e8777141-882c-d5a0-b93b-2dbeb6ea93f7@linaro.org>
On Thu, 2023-07-13 at 11:41 +0200, Daniel Lezcano wrote:
> On 10/07/2023 12:47, Harry Austen wrote:
> > In iwl_mvm_thermal_zone_register(), when registering a thermal
> > zone, the
> > thermal subsystem will evaluate its temperature.
> > But iwl_mvm_tzone_get_temp() fails at this time because
> > iwl_mvm_firmware_running() returns false.
> > And that's why many users report that they see
> > "thermal thermal_zoneX: failed to read out thermal zone (-61)"
> > message during wifi driver probing.
> >
> > This patch attempts to fix this by delaying enabling of the thermal
> > zone
> > until after the firmware has been loaded/initialized. It also gets
> > disabled when going into suspend.
>
> Thanks for taking care of this bug.
>
> The thermal zone will be accessible from userspace
Currently, I see that the mode is checked only in
__thermal_zone_device_update().
should we limit the userspace access for disabled thermal zone? For
example, return failure when reading 'temp' sysfs attribute.
> and can be enabled
> manually.
maybe we should have a .change_mode() callback and return failure when
enabling the thermal zone with wifi firmware unloaded.
> The resulting temperature read error will be the same in this
> case.
>
> IMO, it is cleaner to actually [un]register the thermal zone when the
> firmware is [un]loaded
Austen,
may I know how often is this wifi firmware loaded/unloaded?
thanks,
rui
>
> > Signed-off-by: Harry Austen <hpausten@protonmail.com>
> > ---
> > .../net/wireless/intel/iwlwifi/mvm/mac80211.c | 18
> > ++++++++++++++++++
> > drivers/net/wireless/intel/iwlwifi/mvm/tt.c | 9 +--------
> > 2 files changed, 19 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c
> > b/drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c
> > index ce7905faa08f..a47d29a64dd4 100644
> > --- a/drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c
> > +++ b/drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c
> > @@ -1187,6 +1187,17 @@ int iwl_mvm_mac_start(struct ieee80211_hw
> > *hw)
> >
> > mutex_unlock(&mvm->mutex);
> >
> > +#ifdef CONFIG_THERMAL
> > + /* Needs to be done outside of mutex guarded section to
> > prevent deadlock, since enabling
> > + * the thermal zone calls the .get_temp() callback, which
> > attempts to acquire the mutex.
> > + */
> > + if (!ret) {
> > + ret = thermal_zone_device_enable(mvm-
> > >tz_device.tzone);
> > + if (ret)
> > + IWL_DEBUG_TEMP(mvm, "Failed to enable
> > thermal zone (err = %d)\n", ret);
> > + }
> > +#endif
> > +
> > iwl_mvm_mei_set_sw_rfkill_state(mvm);
> >
> > return ret;
> > @@ -1282,6 +1293,7 @@ void __iwl_mvm_mac_stop(struct iwl_mvm *mvm)
> > void iwl_mvm_mac_stop(struct ieee80211_hw *hw)
> > {
> > struct iwl_mvm *mvm = IWL_MAC80211_GET_MVM(hw);
> > + int ret;
> >
> > flush_work(&mvm->async_handlers_wk);
> > flush_work(&mvm->add_stream_wk);
> > @@ -1307,6 +1319,12 @@ void iwl_mvm_mac_stop(struct ieee80211_hw
> > *hw)
> >
> > iwl_mvm_mei_set_sw_rfkill_state(mvm);
> >
> > +#ifdef CONFIG_THERMAL
> > + ret = thermal_zone_device_disable(mvm->tz_device.tzone);
> > + if (ret)
> > + IWL_DEBUG_TEMP(mvm, "Failed to disable thermal zone
> > (err = %d)\n", ret);
> > +#endif
> > +
> > mutex_lock(&mvm->mutex);
> > __iwl_mvm_mac_stop(mvm);
> > mutex_unlock(&mvm->mutex);
> > diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/tt.c
> > b/drivers/net/wireless/intel/iwlwifi/mvm/tt.c
> > index 157e96fa23c1..964d2d011c6b 100644
> > --- a/drivers/net/wireless/intel/iwlwifi/mvm/tt.c
> > +++ b/drivers/net/wireless/intel/iwlwifi/mvm/tt.c
> > @@ -680,7 +680,7 @@ static struct thermal_zone_device_ops
> > tzone_ops = {
> >
> > static void iwl_mvm_thermal_zone_register(struct iwl_mvm *mvm)
> > {
> > - int i, ret;
> > + int i;
> > char name[16];
> > static atomic_t counter = ATOMIC_INIT(0);
> >
> > @@ -707,13 +707,6 @@ static void
> > iwl_mvm_thermal_zone_register(struct iwl_mvm *mvm)
> > return;
> > }
> >
> > - ret = thermal_zone_device_enable(mvm->tz_device.tzone);
> > - if (ret) {
> > - IWL_DEBUG_TEMP(mvm, "Failed to enable thermal
> > zone\n");
> > - thermal_zone_device_unregister(mvm-
> > >tz_device.tzone);
> > - return;
> > - }
> > -
> > /* 0 is a valid temperature,
> > * so initialize the array with S16_MIN which invalid
> > temperature
> > */
> > --
> > 2.41.0
> >
> >
>
next prev parent reply other threads:[~2023-07-16 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 10:47 [PATCH] wifi: iwlwifi: mvm: enable thermal zone only when firmware is loaded Harry Austen
2023-07-13 9:41 ` Daniel Lezcano
2023-07-16 13:45 ` Zhang, Rui [this message]
2023-07-23 21:10 ` Harry Austen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7a45b2ed16645523a13d69290b27031f607b214a.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=avraham.stern@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=gregory.greenman@intel.com \
--cc=hpausten@protonmail.com \
--cc=johannes.berg@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox