watchdog: max77620: Add comment to clarify set_timeout procedure
Clarify why we need to ping the watchdog before changing the timeout by quoting the MAX77714 datasheet. Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net> Reviewed-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Lee Jones <lee.jones@linaro.org>
This commit is contained in:
parent
254099d8fa
commit
3f6f1f1f9f
|
@ -123,6 +123,11 @@ static int max77620_wdt_set_timeout(struct watchdog_device *wdt_dev,
|
|||
break;
|
||||
}
|
||||
|
||||
/*
|
||||
* "If the value of TWD needs to be changed, clear the system
|
||||
* watchdog timer first [...], then change the value of TWD."
|
||||
* (MAX77714 datasheet but applies to MAX77620 too)
|
||||
*/
|
||||
ret = regmap_update_bits(wdt->rmap, wdt->drv_data->reg_cnfg_glbl3,
|
||||
wdt->drv_data->wdtc_mask, 0x1);
|
||||
if (ret < 0)
|
||||
|
|
Loading…
Reference in New Issue