diff options
| author | Uwe Kleine-König <u.kleine-koenig@pengutronix.de> | 2021-04-23 19:32:26 +0300 |
|---|---|---|
| committer | Thierry Reding <thierry.reding@gmail.com> | 2021-04-26 09:49:48 +0300 |
| commit | a6efb35019d00f483a0e5f188747723371d659fe (patch) | |
| tree | 5fa637b022fb3adc2eb716caf22747553ccee5fb /drivers | |
| parent | 8035e6c66a5e98f098edf7441667de74affb4e78 (diff) | |
| download | linux-a6efb35019d00f483a0e5f188747723371d659fe.tar.xz | |
pwm: Reword docs about pwm_apply_state()
The main issue is that the current documentation talks about the
non-existent function pwm_get_last_applied_state. (This was right in the
context of
https://lore.kernel.org/linux-pwm/20210406073036.26857-1-u.kleine-koenig@pengutronix.de/
but was then missed to adapt when this patch was reduced to a
documentation update.)
While at is also clarify "last applied PWM state" to "PWM state that was
passed to the last invocation of pwm_apply_state()" to better
distinguish to the last actually implemented state and reword to drop a
word repetition.
Fixes: 1a7a6e8072ea ("pwm: Clarify which state pwm_get_state() returns")
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Thierry Reding <thierry.reding@gmail.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions