diff options
| author | Uwe Kleine-König <[email protected]> | 2021-07-07 18:27:53 +0200 |
|---|---|---|
| committer | Thierry Reding <[email protected]> | 2021-09-02 21:38:37 +0200 |
| commit | d44084c93427bb0a9261432db1a8ca76a42d805e (patch) | |
| tree | 7738cad80999895efbe86fb1846ca98012e3b55a | |
| parent | 9d768cd7fd42bb0be16f36aec48548fca5260759 (diff) | |
pwm: stm32-lp: 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.
Signed-off-by: Uwe Kleine-König <[email protected]>
Signed-off-by: Thierry Reding <[email protected]>
| -rw-r--r-- | drivers/pwm/pwm-stm32-lp.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/pwm/pwm-stm32-lp.c b/drivers/pwm/pwm-stm32-lp.c index 93dd03618465..e4a10aac354d 100644 --- a/drivers/pwm/pwm-stm32-lp.c +++ b/drivers/pwm/pwm-stm32-lp.c @@ -222,8 +222,6 @@ static int stm32_pwm_lp_remove(struct platform_device *pdev) { struct stm32_pwm_lp *priv = platform_get_drvdata(pdev); - pwm_disable(&priv->chip.pwms[0]); - return pwmchip_remove(&priv->chip); } |