mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: barebox@lists.infradead.org, a.fatoum@pengutronix.de
Subject: [PATCH v2 2/2] mfd: da9063: fix watchdog ping execution
Date: Mon,  4 Nov 2019 11:28:06 +0100	[thread overview]
Message-ID: <20191104102806.8044-2-m.felsch@pengutronix.de> (raw)
In-Reply-To: <20191104102806.8044-1-m.felsch@pengutronix.de>

The watchdog resets the system if the watchdog gets pinged to fast.
Between each watchdog ping must be a pause of at least 200ms. This
commit fixes that by rejecting two fast requests.

Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
---
Hi,

after the a discussion we decided to change the busy wait behaviour. Now
the driver won't wait and reject the ping-request immediately to ensure
the cool down phase.

Regards,
  Marco

 drivers/mfd/da9063.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/drivers/mfd/da9063.c b/drivers/mfd/da9063.c
index 4d459c7f18..b1e4116906 100644
--- a/drivers/mfd/da9063.c
+++ b/drivers/mfd/da9063.c
@@ -14,6 +14,7 @@
  */
 
 #include <common.h>
+#include <clock.h>
 #include <driver.h>
 #include <gpio.h>
 #include <restart.h>
@@ -33,6 +34,7 @@ struct da9063 {
 	struct i2c_client	*client1;
 	struct device_d		*dev;
 	unsigned int		timeout;
+	uint64_t		last_ping;
 };
 
 /* forbidden/impossible value; timeout will be set to this value initially to
@@ -237,6 +239,14 @@ static int da9063_watchdog_ping(struct da9063 *priv)
 	int ret;
 	u8 val;
 
+	/*
+	 * The watchdog has a cool down phase of 200ms and if we ping to fast
+	 * the da9062/3 resets the system. Reject those requests has a maximum
+	 * failure of 10% if the watchdog timeout is set to 2.048s.
+	 */
+	if ((int64_t)(priv->last_ping + 200 * MSECOND - get_time_ns()) > 0)
+		return 0;
+
 	dev_dbg(priv->dev, "ping\n");
 
 	/* reset watchdog timer; register is self clearing */
@@ -245,6 +255,8 @@ static int da9063_watchdog_ping(struct da9063 *priv)
 	if (ret < 0)
 		return ret;
 
+	priv->last_ping = get_time_ns();
+
 	return 0;
 }
 
-- 
2.20.1


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2019-11-04 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 10:28 [PATCH v2 1/2] mfd: da9063: fix TWDSCALE debug message Marco Felsch
2019-11-04 10:28 ` Marco Felsch [this message]
2019-11-05 10:10   ` [PATCH v2 2/2] mfd: da9063: fix watchdog ping execution Sascha Hauer

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20191104102806.8044-2-m.felsch@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox