public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Lukasz Luba <lukasz.luba@arm.com>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Zhang Rui <rui.zhang@intel.com>
Subject: [PATCH v1 0/2] thermal: core: Fix two issues related to thermal zone resume
Date: Fri, 14 Jun 2024 17:17:35 +0200	[thread overview]
Message-ID: <6070114.lOV4Wx5bFT@kreacher> (raw)

Hi Everyone,

There are two issues resulting from asynchronous suspend of thermal zones.

One of them is platform-specific and related to some firmware issue (I think)
causing battery readings to become invalid after a system resume due to
interference between ACPI battery resume and a thermal zone update.  This
can be addressed by running the thermal PM notifier after all of the other
PM notifiers (including the ACPI battery one) which is done by patch [2/2].

The other one is mostly theoretical, but I couldn't convince myself that it
cannot happen.  Namely, a leftover thermal zone resume running during the
next system suspend (if it is carried out back-to-back with the previous
suspend-resume cycle) can accidentally reset tz->suspended set for a thermal
zone by the thermal pre-suspend PM notifier.  This is addressed by patch
[1/2] (which goes before the second one because the latter increases the
likelihood of the issue slightly).

Thanks!




             reply	other threads:[~2024-06-14 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 15:17 Rafael J. Wysocki [this message]
2024-06-14 15:22 ` [PATCH v1 1/2] thermal: core: Synchronize suspend-prepare and post-suspend actions Rafael J. Wysocki
2024-06-14 15:26 ` [PATCH v1 2/2] thermal: core: Change PM notifier priority to the minimum Rafael J. Wysocki

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=6070114.lOV4Wx5bFT@kreacher \
    --to=rjw@rjwysocki.net \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rui.zhang@intel.com \
    --cc=srinivas.pandruvada@linux.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