shwdt: fix usage of mod_timer
Subsystems (2)
PATCH 1/1 shwdt: fix usage of mod_timer
This patch fixes the usage of mod_timer and makes the driver usable. mod_timer must be called with an absolute timeout in jiffies, the old implementation used a relative timeout thus the hardware watchdog was never triggered.
drivers/watchdog/shwdt.c +1 -1
@@ -64,7 +64,7 @@* misses its deadline, the kernel timer will allow the WDT to overflow. */ static int clock_division_ratio =WTCSR_CKS_4096 ; -#define next_ping_period (cks) msecs_to_jiffies(cks - 4) +#define next_ping_period (cks) (jiffies + msecs_to_jiffies(cks - 4))static const struct watchdog_info sh_wdt_info;static struct platform_device *sh_wdt_dev;
Paul Mundt
AppliedQuoted 7 lines · David Engraf
This patch fixes the usage of
mod_timerand makes the driver usable.mod_timermust be called with an absolute timeout in jiffies, the old implementation used a relative timeout thus the hardware watchdog was never triggered.Signed-off-by David Engraf <[email protected]>
Applied, thanks.
Hi Paul,
Quoted 9 lines · David Engraf
Quoted 7 lines
This patch fixes the usage of
mod_timerand makes the driver usable.mod_timermust be called with an absolute timeout in jiffies, the old implementation used a relative timeout thus the hardware watchdog was never triggered.Signed-off-by David Engraf <[email protected]>Applied, thanks.
So this patch will go via your tree then.
Kind regards,
Wim.