From: David Engraf Date: Wed, 20 Jul 2011 13:03:39 +0000 (+0200) Subject: watchdog: shwdt: fix usage of mod_timer X-Git-Tag: v3.0.1~6 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f9e4715d434299f8897e3edfed9b6dc90629ffda;p=profile%2Fivi%2Fkernel-adaptation-intel-automotive.git watchdog: shwdt: fix usage of mod_timer commit bea1906620ce72b63f83735c4cc2642b25ec54ae upstream. Fix the usage of mod_timer() and make 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. Signed-off-by: David Engraf Signed-off-by: Paul Mundt Signed-off-by: Wim Van sebroeck Signed-off-by: Andrew Morton Signed-off-by: Greg Kroah-Hartman --- diff --git a/drivers/watchdog/shwdt.c b/drivers/watchdog/shwdt.c index db84f23..a267dc0 100644 --- a/drivers/watchdog/shwdt.c +++ b/drivers/watchdog/shwdt.c @@ -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;