From: Ulf Hansson <ulf.hansson@linaro.org>
To: "Rafael J . Wysocki" <rjw@rjwysocki.net>, linux-pm@vger.kernel.org
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Saravana Kannan <saravanak@google.com>,
Alan Stern <stern@rowland.harvard.edu>,
Adrian Hunter <adrian.hunter@intel.com>,
Tony Lindgren <tony@atomide.com>,
Kevin Hilman <khilman@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 3/3] PM: runtime: Clarify documentation when callbacks are unassigned
Date: Tue, 8 Jun 2021 11:02:50 +0200 [thread overview]
Message-ID: <20210608090250.85256-4-ulf.hansson@linaro.org> (raw)
In-Reply-To: <20210608090250.85256-1-ulf.hansson@linaro.org>
Recent changes to the PM core allows ->runtime_suspend|resume callbacks to
be unassigned.
In the earlier behaviour the PM core would return -ENOSYS, when trying to
runtime resume a device, for example. Let's update the documentation to
clarify this.
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
---
Changes in v2:
- Added a new patch for the updating the docs, as pointed out by Alan.
---
Documentation/power/runtime_pm.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/power/runtime_pm.rst b/Documentation/power/runtime_pm.rst
index 18ae21bf7f92..3d09c9fd450d 100644
--- a/Documentation/power/runtime_pm.rst
+++ b/Documentation/power/runtime_pm.rst
@@ -827,6 +827,14 @@ or driver about runtime power changes. Instead, the driver for the device's
parent must take responsibility for telling the device's driver when the
parent's power state changes.
+Note that, in some cases it may not be desirable for subsystems/drivers to call
+pm_runtime_no_callbacks() for their devices. This could be because a subset of
+the runtime PM callbacks needs to be implemented, a platform dependent PM
+domain could get attached to the device or that the device is power manged
+through a supplier device link. For these reasons and to avoid boilerplate code
+in subsystems/drivers, the PM core allows runtime PM callbacks to be
+unassigned.
+
9. Autosuspend, or automatically-delayed suspends
=================================================
--
2.25.1
next prev parent reply other threads:[~2021-06-08 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 9:02 [PATCH v2 0/3] PM: runtime: Update behaviour for no callbacks Ulf Hansson
2021-06-08 9:02 ` [PATCH v2 1/3] PM: runtime: Improve path in rpm_idle() when no callback Ulf Hansson
2021-06-08 9:02 ` [PATCH v2 2/3] PM: runtime: Allow unassigned ->runtime_suspend|resume callbacks Ulf Hansson
2021-06-08 9:02 ` Ulf Hansson [this message]
2021-06-08 14:23 ` [PATCH v2 3/3] PM: runtime: Clarify documentation when callbacks are unassigned Alan Stern
2021-06-08 14:30 ` Ulf Hansson
2021-06-08 14:49 ` Alan Stern
2021-06-09 9:45 ` Ulf Hansson
2021-06-08 14:24 ` [PATCH v2 0/3] PM: runtime: Update behaviour for no callbacks Alan Stern
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=20210608090250.85256-4-ulf.hansson@linaro.org \
--to=ulf.hansson@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=geert+renesas@glider.be \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=saravanak@google.com \
--cc=stern@rowland.harvard.edu \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).