From: Guenter Roeck <linux@roeck-us.net>
To: Stefan Christ <s.christ@phytec.de>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2] watchdog: da9063_wdt: don't trigger watchdog too fast
Date: Wed, 6 Jul 2016 11:19:58 -0700 [thread overview]
Message-ID: <20160706181958.GA24332@roeck-us.net> (raw)
In-Reply-To: <1467794411-11155-1-git-send-email-s.christ@phytec.de>
On Wed, Jul 06, 2016 at 10:40:11AM +0200, Stefan Christ wrote:
> Triggering the watchdog faster than T_WDMIN=256ms leads to resets of the
> DA9063 chip. The datasheet says that the watchdog must only be triggered
> in the timeframe T_WDMIN to T_WDMAX. The T_WDMAX is configured in the
> driver.
>
> Signed-off-by: Stefan Christ <s.christ@phytec.de>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> v2: use internal kernel API 'min_hw_heartbeat_ms' instead of driver specific
> implementation.
>
> Hi,
>
> this is a follow up patch to the patch
>
> [RFC 1/6] watchdog: da9063_wdt: don't trigger watchdog too fast
>
> in my RFC patch series. Using the internal kernel watchdog API also makes my
> second patch
>
> [RFC 2/6] watchdog: da9063_wdt: use delayed work to trigger
>
> obsolete, because the kernel API uses a delayed worker already.
>
> Kind regards,
> Stefan Christ
> ---
> drivers/watchdog/da9063_wdt.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/watchdog/da9063_wdt.c b/drivers/watchdog/da9063_wdt.c
> index a100f64..5d6b4e5 100644
> --- a/drivers/watchdog/da9063_wdt.c
> +++ b/drivers/watchdog/da9063_wdt.c
> @@ -34,6 +34,7 @@ static const unsigned int wdt_timeout[] = { 0, 2, 4, 8, 16, 32, 65, 131 };
> #define DA9063_WDT_MIN_TIMEOUT wdt_timeout[DA9063_TWDSCALE_MIN]
> #define DA9063_WDT_MAX_TIMEOUT wdt_timeout[DA9063_TWDSCALE_MAX]
> #define DA9063_WDG_TIMEOUT wdt_timeout[3]
> +#define DA9063_RESET_PROTECTION_MS 256
>
> struct da9063_watchdog {
> struct da9063 *da9063;
> @@ -171,6 +172,7 @@ static int da9063_wdt_probe(struct platform_device *pdev)
> wdt->wdtdev.ops = &da9063_watchdog_ops;
> wdt->wdtdev.min_timeout = DA9063_WDT_MIN_TIMEOUT;
> wdt->wdtdev.max_timeout = DA9063_WDT_MAX_TIMEOUT;
> + wdt->wdtdev.min_hw_heartbeat_ms = DA9063_RESET_PROTECTION_MS;
> wdt->wdtdev.timeout = DA9063_WDG_TIMEOUT;
> wdt->wdtdev.parent = &pdev->dev;
>
> --
> 1.9.1
>
next prev parent reply other threads:[~2016-07-06 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 8:40 [PATCH v2] watchdog: da9063_wdt: don't trigger watchdog too fast Stefan Christ
2016-07-06 18:19 ` Guenter Roeck [this message]
2016-07-17 20:18 ` Wim Van Sebroeck
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=20160706181958.GA24332@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-watchdog@vger.kernel.org \
--cc=s.christ@phytec.de \
/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;
as well as URLs for NNTP newsgroup(s).