Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1370087
| From | Krzysztof Kozlowski <krzk@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [PATCH v2] PM / runtime: Document steps for device removal |
| Date | 2016-04-03 05:30 +0200 |
| Message-ID | <rjGTD-5yO-1@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Put a reminder that during device removal drivers should revert all PM runtime changes from the probe. Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org> --- Changes since v1: 1. Address Alan's comments. --- Documentation/power/runtime_pm.txt | 4 ++++ 1 file changed, 4 insertions(+) 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, -- 2.1.4
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
[PATCH v2] PM / runtime: Document steps for device removal Krzysztof Kozlowski <krzk@kernel.org> - 2016-04-03 05:30 +0200
Re: [PATCH v2] PM / runtime: Document steps for device removal Alan Stern <stern@rowland.harvard.edu> - 2016-04-03 20:30 +0200
Re: [PATCH v2] PM / runtime: Document steps for device removal "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2016-04-07 01:40 +0200
csiph-web