diff options
author | Rafael J. Wysocki <rjw@rjwysocki.net> | 2025-04-18 20:55:48 +0200 |
---|---|---|
committer | Rafael J. Wysocki <rjw@rjwysocki.net> | 2025-04-18 20:55:48 +0200 |
commit | f3b25a1b48191048e2f190d878fc3175fc08ffaa (patch) | |
tree | 2d4f10106729021a083cce19da15c45ebede99f4 | |
parent | dead17b1a26fd8b6202911211ec83ac1f6587658 (diff) | |
parent | 19e8019e06b478ab04683418c73ca297d114c425 (diff) |
Merge branch 'pm-docs'
Merge a runtime PM documentation correction for 6.15-rc3.
* pm-docs:
Documentation: PM: runtime: Fix a reference to pm_runtime_autosuspend()
-rw-r--r-- | Documentation/power/runtime_pm.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/power/runtime_pm.rst b/Documentation/power/runtime_pm.rst index 12f429359a82..63344bea8393 100644 --- a/Documentation/power/runtime_pm.rst +++ b/Documentation/power/runtime_pm.rst @@ -154,7 +154,7 @@ suspending the device are satisfied) and to queue up a suspend request for the device in that case. If there is no idle callback, or if the callback returns 0, then the PM core will attempt to carry out a runtime suspend of the device, also respecting devices configured for autosuspend. In essence this means a -call to __pm_runtime_autosuspend() (do note that drivers needs to update the +call to pm_runtime_autosuspend() (do note that drivers needs to update the device last busy mark, pm_runtime_mark_last_busy(), to control the delay under this circumstance). To prevent this (for example, if the callback routine has started a delayed suspend), the routine must return a non-zero value. Negative |