pwm: tegra: Don't needlessly enable and disable the clock in .remove()

There is no reason to enable the PWM clock just to assert the reset
control. (If the reset control depends on the clock this is a bug and
probably it doesn't because in .probe() the reset is deasserted without
the clock being enabled.)

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Thierry Reding <thierry.reding@gmail.com>

diff --git a/drivers/pwm/pwm-tegra.c b/drivers/pwm/pwm-tegra.c
index a051cf43e7d7153bc43af75af0857fd020808d96..e865743e59890e28fbaf476c7ff61f60cb143a1b 100644 (file)
--- a/drivers/pwm/pwm-tegra.c
+++ b/drivers/pwm/pwm-tegra.c
@@ -300,14 +300,8 @@ 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);
-       int err;
-
-       err = clk_prepare_enable(pc->clk);
-       if (err < 0)
-               return err;
 
        reset_control_assert(pc->rst);
-       clk_disable_unprepare(pc->clk);
 
        return pwmchip_remove(&pc->chip);
 }