From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Antoine Tenart <atenart@kernel.org>,
rui.zhang@intel.com, daniel.lezcano@linaro.org, amitk@kernel.org
Cc: linux-pm@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] thermal: int340x: do not set a wrong tcc offset on resume
Date: Fri, 24 Sep 2021 09:27:47 -0700 [thread overview]
Message-ID: <46d6d30201e11422f57bd79691133dc0491bd4c5.camel@linux.intel.com> (raw)
In-Reply-To: <20210909085613.5577-2-atenart@kernel.org>
Hi Daniel,
This patch is important. Can we send for 5.15 rc release?
I see the previous version of this patch is applied to linux-next.
But this series is better as it splits into two patches. The first one
can be easily backported and will fix the problem. The second one is an
improvement.
Thanks,
Srinivas
On Thu, 2021-09-09 at 10:56 +0200, Antoine Tenart wrote:
> After upgrading to Linux 5.13.3 I noticed my laptop would shutdown
> due
> to overheat (when it should not). It turned out this was due to
> commit
> fe6a6de6692e ("thermal/drivers/int340x/processor_thermal: Fix tcc
> setting").
>
> What happens is this drivers uses a global variable to keep track of
> the
> tcc offset (tcc_offset_save) and uses it on resume. The issue is this
> variable is initialized to 0, but is only set in
> tcc_offset_degree_celsius_store, i.e. when the tcc offset is
> explicitly
> set by userspace. If that does not happen, the resume path will set
> the
> offset to 0 (in my case the h/w default being 3, the offset would
> become
> too low after a suspend/resume cycle).
>
> The issue did not arise before commit fe6a6de6692e, as the function
> setting the offset would return if the offset was 0. This is no
> longer
> the case (rightfully).
>
> Fix this by not applying the offset if it wasn't saved before,
> reverting
> back to the old logic. A better approach will come later, but this
> will
> be easier to apply to stable kernels.
>
> The logic to restore the offset after a resume was there long before
> commit fe6a6de6692e, but as a value of 0 was considered invalid I'm
> referencing the commit that made the issue possible in the Fixes tag
> instead.
>
> Fixes: fe6a6de6692e ("thermal/drivers/int340x/processor_thermal: Fix
> tcc setting")
> Cc: stable@vger.kernel.org
> Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> Signed-off-by: Antoine Tenart <atenart@kernel.org>
> ---
> .../thermal/intel/int340x_thermal/processor_thermal_device.c | 5
> +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git
> a/drivers/thermal/intel/int340x_thermal/processor_thermal_device.c
> b/drivers/thermal/intel/int340x_thermal/processor_thermal_device.c
> index 0f0038af2ad4..fb64acfd5e07 100644
> ---
> a/drivers/thermal/intel/int340x_thermal/processor_thermal_device.c
> +++
> b/drivers/thermal/intel/int340x_thermal/processor_thermal_device.c
> @@ -107,7 +107,7 @@ static int tcc_offset_update(unsigned int tcc)
> return 0;
> }
>
> -static unsigned int tcc_offset_save;
> +static int tcc_offset_save = -1;
>
> static ssize_t tcc_offset_degree_celsius_store(struct device *dev,
> struct device_attribute *attr, const
> char *buf,
> @@ -352,7 +352,8 @@ int proc_thermal_resume(struct device *dev)
> proc_dev = dev_get_drvdata(dev);
> proc_thermal_read_ppcc(proc_dev);
>
> - tcc_offset_update(tcc_offset_save);
> + if (tcc_offset_save >= 0)
> + tcc_offset_update(tcc_offset_save);
>
> return 0;
> }
next prev parent reply other threads:[~2021-09-24 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 8:56 [PATCH v2 0/2] thermal: int340x: fix tcc offset on resume Antoine Tenart
2021-09-09 8:56 ` [PATCH v2 1/2] thermal: int340x: do not set a wrong " Antoine Tenart
2021-09-24 16:27 ` Srinivas Pandruvada [this message]
2021-09-24 17:40 ` Daniel Lezcano
2021-09-24 17:51 ` Srinivas Pandruvada
2021-10-20 13:38 ` Antoine Tenart
2021-10-21 9:47 ` Daniel Lezcano
2021-10-21 10:02 ` Antoine Tenart
2021-09-09 8:56 ` [PATCH v2 2/2] thermal: int340x: improve the tcc offset saving for suspend/resume Antoine Tenart
2021-09-09 9:35 ` [PATCH v2 0/2] thermal: int340x: fix tcc offset on resume Srinivas Pandruvada
2021-09-17 7:56 ` Daniel Lezcano
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=46d6d30201e11422f57bd79691133dc0491bd4c5.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=amitk@kernel.org \
--cc=atenart@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=stable@vger.kernel.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).