Skip to content

Commit a96d365

Browse files
Uwe Kleine-KönigUwe Kleine-König
authored andcommitted
pwm: Remove wrong implementation details from pwm_ops's documentation
When .get_state() is called is an implementation detail that implementors and users shouldn't care about and rely on. Additionally it's wrong, because with PWM_DEBUG enabled it is called more often. Just drop the wrong statement. Signed-off-by: Uwe Kleine-König <[email protected]> Link: https://lore.kernel.org/r/611ba758d7e9fb2695e96b23cb7ceeefb6ba8513.1717756902.git.u.kleine-koenig@baylibre.com Signed-off-by: Uwe Kleine-König <[email protected]>
1 parent d6f66e2 commit a96d365

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

include/linux/pwm.h

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -252,9 +252,7 @@ struct pwm_capture {
252252
* @free: optional hook for freeing a PWM
253253
* @capture: capture and report PWM signal
254254
* @apply: atomically apply a new PWM config
255-
* @get_state: get the current PWM state. This function is only
256-
* called once per PWM device when the PWM chip is
257-
* registered.
255+
* @get_state: get the current PWM state.
258256
*/
259257
struct pwm_ops {
260258
int (*request)(struct pwm_chip *chip, struct pwm_device *pwm);

0 commit comments

Comments
 (0)