summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorUwe Kleine-König <u.kleine-koenig@pengutronix.de>2021-06-17 11:51:41 +0200
committerThierry Reding <thierry.reding@gmail.com>2021-06-30 19:12:20 +0200
commit86f7fa71cd830d18d7ebcaf719dffd5ddfe1acdd (patch)
treee6f1ae64129adf06177493268f9b4f20d99e4f8e
parentc1b8ac969febc8f413c4d71f0eefe2e107610449 (diff)
downloadlinux-stable-86f7fa71cd830d18d7ebcaf719dffd5ddfe1acdd.tar.gz
linux-stable-86f7fa71cd830d18d7ebcaf719dffd5ddfe1acdd.tar.bz2
linux-stable-86f7fa71cd830d18d7ebcaf719dffd5ddfe1acdd.zip
pwm: tegra: 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>
-rw-r--r--drivers/pwm/pwm-tegra.c13
1 files changed, 0 insertions, 13 deletions
diff --git a/drivers/pwm/pwm-tegra.c b/drivers/pwm/pwm-tegra.c
index fa025795198b..a051cf43e7d7 100644
--- a/drivers/pwm/pwm-tegra.c
+++ b/drivers/pwm/pwm-tegra.c
@@ -300,25 +300,12 @@ static int tegra_pwm_probe(struct platform_device *pdev)
static int tegra_pwm_remove(struct platform_device *pdev)
{
struct tegra_pwm_chip *pc = platform_get_drvdata(pdev);
- unsigned int i;
int err;
err = clk_prepare_enable(pc->clk);
if (err < 0)
return err;
- for (i = 0; i < pc->chip.npwm; i++) {
- struct pwm_device *pwm = &pc->chip.pwms[i];
-
- if (!pwm_is_enabled(pwm))
- if (clk_prepare_enable(pc->clk) < 0)
- continue;
-
- pwm_writel(pc, i, 0);
-
- clk_disable_unprepare(pc->clk);
- }
-
reset_control_assert(pc->rst);
clk_disable_unprepare(pc->clk);