X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=Documentation%2Fpower%2Fruntime_pm.txt;h=1fd1fbe9ce95adf9b37109cfea9833d586fcfffe;hb=55f058e7574c3615dea4615573a19bdb258696c6;hp=7328cf85236c2b2bc5a4c078dc9f81f2e3febd11;hpb=51b3eae8dbe5e6fa9657b21388ad6642d6934952;p=mirror_ubuntu-zesty-kernel.git

diff --git a/Documentation/power/runtime_pm.txt b/Documentation/power/runtime_pm.txt
index 7328cf85236c..1fd1fbe9ce95 100644
--- a/Documentation/power/runtime_pm.txt
+++ b/Documentation/power/runtime_pm.txt
@@ -586,6 +586,10 @@ drivers to make their ->remove() callbacks avoid races with runtime PM directly,
 but also it allows of more flexibility in the handling of devices during the
 removal of their drivers.
 
+Drivers in ->remove() callback should undo the runtime PM changes done
+in ->probe(). Usually this means calling pm_runtime_disable(),
+pm_runtime_dont_use_autosuspend() etc.
+
 The user space can effectively disallow the driver of the device to power manage
 it at run time by changing the value of its /sys/devices/.../power/control
 attribute to "on", which causes pm_runtime_forbid() to be called.  In principle,