On Wed, Jan 4, 2017 at 4:25 AM, Guenter Roeck <linux@xxxxxxxxxxxx> wrote: > Enabling the clock before accessing chip registers and disabling it > afterwards does not really make sense and only adds complexity to > the driver. In addition to that, a comment int the driver suggests > that it does not serve a useful purpose either. > > "The watchdog block is of course always clocked, the > clk_enable()/clk_disable() calls are mainly for performing reference > counting higher up in the clock hierarchy." > > Just keep the clock enabled instead. > > Signed-off-by: Guenter Roeck <linux@xxxxxxxxxxxx> Reviewed-by: Linus Walleij <linus.walleij@xxxxxxxxxx> Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
