aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/power
diff options
context:
space:
mode:
authorKevin Hilman <khilman@ti.com>2011-06-30 18:07:31 -0400
committerRafael J. Wysocki <rjw@sisk.pl>2011-07-02 08:27:03 -0400
commit5efb54cc3fc104585cda81c44676f05115bd9ddd (patch)
tree23972de36f87064a992687a9280637d251e8e1ff /Documentation/power
parentc66a86d0cdce3bad2da794f114cc37377d242c3d (diff)
PM: Documentation: fix typo: pm_runtime_idle_sync() doesn't exist.
Replace reference to pm_runtime_idle_sync() in the driver core with pm_runtime_put_sync() which is used in the code. Signed-off-by: Kevin Hilman <khilman@ti.com> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'Documentation/power')
-rw-r--r--Documentation/power/runtime_pm.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/power/runtime_pm.txt b/Documentation/power/runtime_pm.txt
index 22accb3eb40e..518d9be4c731 100644
--- a/Documentation/power/runtime_pm.txt
+++ b/Documentation/power/runtime_pm.txt
@@ -506,7 +506,7 @@ pm_runtime_suspend() or pm_runtime_idle() or their asynchronous counterparts,
506they will fail returning -EAGAIN, because the device's usage counter is 506they will fail returning -EAGAIN, because the device's usage counter is
507incremented by the core before executing ->probe() and ->remove(). Still, it 507incremented by the core before executing ->probe() and ->remove(). Still, it
508may be desirable to suspend the device as soon as ->probe() or ->remove() has 508may be desirable to suspend the device as soon as ->probe() or ->remove() has
509finished, so the PM core uses pm_runtime_idle_sync() to invoke the 509finished, so the PM core uses pm_runtime_put_sync() to invoke the
510subsystem-level idle callback for the device at that time. 510subsystem-level idle callback for the device at that time.
511 511
512The user space can effectively disallow the driver of the device to power manage 512The user space can effectively disallow the driver of the device to power manage