From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: Brian Norris <briannorris@chromium.org>,
Alan Stern <stern@rowland.harvard.edu>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Ulf Hansson <ulf.hansson@oss.qualcomm.com>,
Linux Driver Core Development <driver-core@lists.linux.dev>
Subject: [PATCH v1 0/4] PM: runtime: Close some gaps related to autosuspend
Date: Thu, 19 Nov 2026 21:13:03 +0100 [thread overview]
Message-ID: <1978814.tdWV9SEqCh@rafael.j.wysocki> (raw)
Hi All,
This is a follow-up series for
https://web.git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=26236a3e8803f7e1ace104020d7f006edb220116
which is in linux-next.
First of all, I was mistaken when I wrote this in the changelog of the above:
Updating the last_busy timestamp when rpm_idle() returns an error
without calling rpm_suspend() is not useful because the device is then
going to remain active for an unknown amount of time and its autosuspend
delay needs to take effect later.
There actually is a reason for doing this which is that an autosuspend timer
(left behind by an intermediate runtime resume) may be running when rpm_idle()
runs and that autosuspend timer needs to be prevented from using a soon-to-be-stale
last_busy timestamp value. There is one more issue related to that in
__pm_runtime_idle() and both are addressed by patch [1/4].
Patch [2/4] simply removes spaces preceding labels as a matter of cleanup.
Patch [3/4] removes one more difference in the handling of devices that are
resumed by rpm_resume() and those that are already active when they are passed
to that function.
Patch [4/4] drops the direct pm_runtime_mark_last_busy() calls from rpm_resume()
that are not needed any more after the previous changes.
For details, please see the patch changelogs.
Thanks!
next reply other threads:[~2026-11-19 20:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 20:13 Rafael J. Wysocki [this message]
2026-11-19 20:16 ` [PATCH v1 1/4] PM: runtime: Update last_busy in all rpm_idle() paths Rafael J. Wysocki
2026-11-20 20:59 ` Brian Norris
2026-11-20 21:29 ` Rafael J. Wysocki (Intel)
2026-11-19 20:17 ` [PATCH v1 2/4] PM: runtime: Drop space characters preceding labels Rafael J. Wysocki
2026-11-20 2:47 ` Alan Stern
2026-11-20 12:11 ` Rafael J. Wysocki (Intel)
2026-11-20 12:30 ` Rafael J. Wysocki (Intel)
2026-11-20 16:11 ` Alan Stern
2026-11-19 20:17 ` [PATCH v1 3/4] PM: runtime: Let devices suspend after an attempted resume Rafael J. Wysocki
2026-11-20 21:04 ` Brian Norris
2026-11-19 20:18 ` [PATCH v1 4/4] PM: runtime: Drop direct last_busy updates from rpm_resume() 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=1978814.tdWV9SEqCh@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=briannorris@chromium.org \
--cc=driver-core@lists.linux.dev \
--cc=linux-pm@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stern@rowland.harvard.edu \
--cc=ulf.hansson@oss.qualcomm.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