The TOP_INIT may be zero, so the timeout period may be very short after initialization is done, thus the system may be reset soon after enabling. We fix this problem by restarting the counter immediately after enabling WDT. Signed-off-by: Jisheng Zhang <jszhang@xxxxxxxxxxx> --- drivers/watchdog/dw_wdt.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/watchdog/dw_wdt.c b/drivers/watchdog/dw_wdt.c index 9f21029..ad0619d 100644 --- a/drivers/watchdog/dw_wdt.c +++ b/drivers/watchdog/dw_wdt.c @@ -146,6 +146,7 @@ static int dw_wdt_open(struct inode *inode, struct file *filp) dw_wdt_set_top(DW_WDT_MAX_TOP); writel(WDOG_CONTROL_REG_WDT_EN_MASK, dw_wdt.regs + WDOG_CONTROL_REG_OFFSET); + dw_wdt_keepalive(); } dw_wdt_set_next_heartbeat(); -- 2.1.0 -- 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
