aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorYoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>2019-05-31 18:54:58 +0900
committerThierry Reding <thierry.reding@gmail.com>2019-06-26 11:39:11 +0200
commit321a7cea973b4f63bb7e3baaea8428dfb8b424a9 (patch)
tree47376820f70045bdf4cc813ee08a78abda544714
parentpwm: meson: Add documentation to the driver (diff)
downloadlinux-dev-321a7cea973b4f63bb7e3baaea8428dfb8b424a9.tar.xz
linux-dev-321a7cea973b4f63bb7e3baaea8428dfb8b424a9.zip
pwm: Add power management descriptions
This patch adds power management descriptions that consumers should implement it. Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be> Reviewed-by: Simon Horman <horms+renesas@verge.net.au> Signed-off-by: Thierry Reding <thierry.reding@gmail.com>
-rw-r--r--Documentation/pwm.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/pwm.txt b/Documentation/pwm.txt
index 8fbf0aa3ba2d..ab62f1bb0366 100644
--- a/Documentation/pwm.txt
+++ b/Documentation/pwm.txt
@@ -65,6 +65,10 @@ period). struct pwm_args contains 2 fields (period and polarity) and should
be used to set the initial PWM config (usually done in the probe function
of the PWM user). PWM arguments are retrieved with pwm_get_args().
+All consumers should really be reconfiguring the PWM upon resume as
+appropriate. This is the only way to ensure that everything is resumed in
+the proper order.
+
Using PWMs with the sysfs interface
-----------------------------------
@@ -141,6 +145,9 @@ The implementation of ->get_state() (a method used to retrieve initial PWM
state) is also encouraged for the same reason: letting the PWM user know
about the current PWM state would allow him to avoid glitches.
+Drivers should not implement any power management. In other words,
+consumers should implement it as described in the "Using PWMs" section.
+
Locking
-------