From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: at91sam9: watchdog: period
Date: Tue, 19 May 2015 12:04:33 +0200 [thread overview]
Message-ID: <20150519120433.763a416e@bbrezillon> (raw)
In-Reply-To: <555B07D0.4030000@aksignal.cz>
On Tue, 19 May 2015 11:52:16 +0200
Ji?? Prchal <jiri.prchal@aksignal.cz> wrote:
>
>
> On 19.5.2015 11:14, Boris Brezillon wrote:
> >
> > There's a difference between your heartbeat (the frequency you
> > refresh/reset your watchdog) and the watchdog expiration time (here set
> > to 16 secs).
> > We usually set the heartbeat to 1/2 or 1/4 the expiration time, so that
> > we're (almost) sure we can reset the watchdog before its expiration.
> >
> >
> I'm confused. Why need kernel to know the time in witch userspace process will reset watchdog?
This time is not exposed to userspace, it's the internal heartbeat used
by the driver to refresh the watchdog.
> And how to change watchdog expiration time?
With the atmel,max-heartbeat-sec property.
Anyway, that does not explain why your system takes 61 secs to trigger
a reset (instead of 16 secs).
Can you try to revert this commit [1] ?
[1]https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/watchdog/at91sam9_wdt.c?id=d677772e1358924bf487cd833bdc4d50f3f6f64d
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-19 10:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 7:16 at91sam9: watchdog: period Jiří Prchal
2015-05-15 13:59 ` Bryan Evenson
2015-05-15 14:19 ` Nicolas Ferre
2015-05-18 6:25 ` Jiří Prchal
2015-05-15 15:25 ` Boris Brezillon
2015-05-18 6:27 ` Jiří Prchal
2015-05-18 7:27 ` Boris Brezillon
2015-05-18 8:17 ` Jiří Prchal
2015-05-19 3:07 ` Yang, Wenyou
2015-05-19 7:14 ` Boris Brezillon
2015-05-19 9:01 ` Jiří Prchal
2015-05-19 9:14 ` Boris Brezillon
2015-05-19 9:52 ` Jiří Prchal
2015-05-19 10:04 ` Boris Brezillon [this message]
2015-05-20 12:39 ` Jiří Prchal
2015-05-21 12:41 ` Jiří Prchal
2015-05-27 7:11 ` Jiří Prchal
2015-05-19 7:12 ` Boris Brezillon
2015-05-19 9:00 ` Jiří Prchal
2015-10-06 13:07 ` Jiří Prchal
2015-10-06 18:03 ` Sylvain Rochet
2015-10-07 7:16 ` Jiří Prchal
2015-10-07 9:22 ` Sylvain Rochet
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=20150519120433.763a416e@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).