]> asedeno.scripts.mit.edu Git - linux.git/commitdiff
pwm: Update comment on struct pwm_ops::apply
authorRasmus Villemoes <linux@rasmusvillemoes.dk>
Fri, 4 Oct 2019 13:32:07 +0000 (15:32 +0200)
committerThierry Reding <thierry.reding@gmail.com>
Mon, 21 Oct 2019 14:50:03 +0000 (16:50 +0200)
Commit 71523d1812ac (pwm: Ensure pwm_apply_state() doesn't modify the
state argument) updated the kernel-doc for pwm_apply_state(), but not
for the ->apply callback in the pwm_ops struct.

Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Reviewed-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Thierry Reding <thierry.reding@gmail.com>
include/linux/pwm.h

index b2c9c460947d13ec3a724fab9fd36bf0f7a77b98..0ef808d925bb741471a34513893fb6c9e52f39d7 100644 (file)
@@ -243,10 +243,7 @@ pwm_set_relative_duty_cycle(struct pwm_state *state, unsigned int duty_cycle,
  * @request: optional hook for requesting a PWM
  * @free: optional hook for freeing a PWM
  * @capture: capture and report PWM signal
- * @apply: atomically apply a new PWM config. The state argument
- *        should be adjusted with the real hardware config (if the
- *        approximate the period or duty_cycle value, state should
- *        reflect it)
+ * @apply: atomically apply a new PWM config
  * @get_state: get the current PWM state. This function is only
  *            called once per PWM device when the PWM chip is
  *            registered.