diff mbox series

[v3,3/3] PM: runtime: Clarify documentation when callbacks are unassigned

Message ID 20210609100157.97635-1-ulf.hansson@linaro.org (mailing list archive)
State New, archived
Headers show
Series None | expand

Commit Message

Ulf Hansson June 9, 2021, 10:01 a.m. UTC
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 v3:
	- Fix spelling and further clarified the behaviour, according to
	comments from Alan.

 Documentation/power/runtime_pm.rst | 8 ++++++++
 1 file changed, 8 insertions(+)
diff mbox series


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
 9. Autosuspend, or automatically-delayed suspends