From: Manaf Meethalavalappu Pallikunhi <quic_manafm@quicinc.com>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
Thara Gopinath <thara.gopinath@linaro.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] thermal/core: Clear all mitigation when thermal zone is disabled
Date: Wed, 29 Dec 2021 12:22:54 +0530 [thread overview]
Message-ID: <cf6cfba0-816f-ca1e-3bb1-aad693e5a0b3@quicinc.com> (raw)
In-Reply-To: <YcSNIJVnCQvx6ttg@google.com>
On 12/23/2021 8:22 PM, Matthias Kaehlcke wrote:
> On Tue, Dec 21, 2021 at 04:11:58PM +0530, Manaf Meethalavalappu Pallikunhi wrote:
>> Whenever a thermal zone is in trip violated state, there is a chance
>> that the same thermal zone mode can be disabled either via thermal
>> core API or via thermal zone sysfs. Once it is disabled, the framework
>> bails out any re-evaluation of thermal zone. It leads to a case where
>> if it is already in mitigation state, it will stay the same state
>> until it is re-enabled.
>>
>> To avoid above mentioned issue, on thermal zone disable request
>> reset thermal zone and clear mitigation for each trip explicitly.
>>
>> Signed-off-by: Manaf Meethalavalappu Pallikunhi <quic_manafm@quicinc.com>
>> ---
>> drivers/thermal/thermal_core.c | 9 ++++++++-
>> 1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
>> index 51374f4..a8ae340 100644
>> --- a/drivers/thermal/thermal_core.c
>> +++ b/drivers/thermal/thermal_core.c
>> @@ -427,6 +427,7 @@ static int thermal_zone_device_set_mode(struct thermal_zone_device *tz,
>> enum thermal_device_mode mode)
>> {
>> int ret = 0;
>> + int count;
>>
>> mutex_lock(&tz->lock);
>>
>> @@ -449,8 +450,14 @@ static int thermal_zone_device_set_mode(struct thermal_zone_device *tz,
>>
>> if (mode == THERMAL_DEVICE_ENABLED)
>> thermal_notify_tz_enable(tz->id);
>> - else
>> + else {
>> + /* make sure all previous throttlings are cleared */
>> + thermal_zone_device_init(tz);
>> + for (count = 0; count < tz->trips; count++)
>> + handle_thermal_trip(tz, count);
> nit: s/count/trip/
Updated in V2
prev parent reply other threads:[~2021-12-29 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 10:41 [PATCH] thermal/core: Clear all mitigation when thermal zone is disabled Manaf Meethalavalappu Pallikunhi
2021-12-23 14:52 ` Matthias Kaehlcke
2021-12-29 6:52 ` Manaf Meethalavalappu Pallikunhi [this message]
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=cf6cfba0-816f-ca1e-3bb1-aad693e5a0b3@quicinc.com \
--to=quic_manafm@quicinc.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=thara.gopinath@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).