diff options
| author | Uwe Kleine-König <u.kleine-koenig@pengutronix.de> | 2021-03-30 14:37:41 +0200 |
|---|---|---|
| committer | Thierry Reding <thierry.reding@gmail.com> | 2021-04-09 14:46:27 +0200 |
| commit | a9ea2e793e5aee690b90d115dbb9229934d30f2e (patch) | |
| tree | 7201b754d5b396b9f24bec0d6e80ffaa7ffdece5 /crypto | |
| parent | 13ef0414c891658c7d4c1d13fbd58a8d59a09dd4 (diff) | |
pwm: sti: Don't modify HW state in .remove callback
A consumer is expected to disable a PWM before calling pwm_put(). And if
they didn't there is hopefully a good reason (or the consumer needs
fixing). Also if disabling an enabled PWM was the right thing to do,
this should better be done in the framework instead of in each low level
driver.
So drop the hardware modification from the .remove() callback.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Thierry Reding <thierry.reding@gmail.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions