All of
 help / color / mirror / Atom feed
From: Doug Anderson <>
To: Wim Van Sebroeck <>, Guenter Roeck <>
Cc: Heiko Stuebner <>,
	Lunxue Dai <>,
	Jisheng Zhang <>,
	Dinh Nguyen <>,
	Doug Anderson <>,,
Subject: [PATCH v2 1/2] watchdog: dw_wdt: pat the watchdog before enabling it
Date: Mon, 26 Jan 2015 15:27:15 -0800	[thread overview]
Message-ID: <> (raw)

On some dw_wdt implementations the "top" register may be initted to 0
at bootup.  In such a case, each "pat" of the watchdog will reset the
timer to 0xffff.  That's pretty short.

The input clock of the wdt can be any of a wide range of values.  On
an rk3288 system, I've seen the wdt clock be 24.75 MHz.  That means
each tick is ~40ns and we'll count to 0xffff in ~2.6ms.

Because of the above two facts, it's a really good idea to pat the
watchdog after initting the "top" register properly and before
enabling the watchdog.  If you don't then there's no way we'll get the
next heartbeat in time.

Jisheng Zhang fixed this problem on some dw_mmc versions by using the
TOP_INIT feature.  However, the dw_wdt on rk3288 doesn't have TOP_INIT
so it's a good idea to also pat the watchdog manually.

Signed-off-by: Doug Anderson <>
Changes in v2:
- Add comment about why TOP_INIT doesn't work on rk3288; move pat
  to right next to the attempt to use TOP_INIT.

 drivers/watchdog/dw_wdt.c | 19 +++++++++++++------
 1 file changed, 13 insertions(+), 6 deletions(-)

diff --git a/drivers/watchdog/dw_wdt.c b/drivers/watchdog/dw_wdt.c
index b34a2e4..2c24882 100644
--- a/drivers/watchdog/dw_wdt.c
+++ b/drivers/watchdog/dw_wdt.c
@@ -96,6 +96,12 @@ static inline void dw_wdt_set_next_heartbeat(void)
 	dw_wdt.next_heartbeat = jiffies + dw_wdt_get_top() * HZ;
+static void dw_wdt_keepalive(void)
+	writel(WDOG_COUNTER_RESTART_KICK_VALUE, dw_wdt.regs +
 static int dw_wdt_set_top(unsigned top_s)
 	int i, top_val = DW_WDT_MAX_TOP;
@@ -114,17 +120,18 @@ static int dw_wdt_set_top(unsigned top_s)
 	writel(top_val | top_val << WDOG_TIMEOUT_RANGE_TOPINIT_SHIFT,
+	/*
+	 * On some versions of dw_wdt writing to TOPINIT counts as a pat
+	 * (kick) of the watchdog; for other version of dw_wdt bits 4-7
+	 * are reserved and we need to pat the watchdog dog manually.
+	 */
+	dw_wdt_keepalive();
 	return dw_wdt_top_in_seconds(top_val);
-static void dw_wdt_keepalive(void)
-	writel(WDOG_COUNTER_RESTART_KICK_VALUE, dw_wdt.regs +
 static int dw_wdt_restart_handle(struct notifier_block *this,
 				unsigned long mode, void *cmd)

             reply	other threads:[~2015-01-26 23:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 23:27 Doug Anderson [this message]
2015-01-26 23:27 ` [PATCH v2 2/2] watchdog: dw_wdt: Try to get a 30 second watchdog by default Doug Anderson
2015-01-27  2:12 ` [PATCH v2 1/2] watchdog: dw_wdt: pat the watchdog before enabling it Guenter Roeck
2015-01-27  3:49 ` Jisheng Zhang
2015-01-27  4:08   ` Guenter Roeck
2015-01-27  4:52     ` Jisheng Zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.