From: sylvain.rochet@finsecur•com (Sylvain Rochet)
To: linux-arm-kernel@lists•infradead.org
Subject: at91sam9: watchdog: period
Date: Wed, 7 Oct 2015 11:22:58 +0200 [thread overview]
Message-ID: <20151007092258.GA15119@gradator.net> (raw)
In-Reply-To: <20151006180342.GA13434@gradator.net>
Hi,
On Tue, Oct 06, 2015 at 08:03:43PM +0200, Sylvain Rochet wrote:
>
> I wonder if we should substract from the watchdog_ops->set_timeout()
> new_timeout argument value the previously set hardware timeout period,
> this way we would have a "60 - 16 + 12~16" instead of a "60 + 12~16"
> watchdog timeout. If someone agree I will propose a patch to do that.
A night of thinking later, it may sounds appealing but this is a stupid
idea. We have an overlap hard to deal with if user chooses a ping time
close to the timeout (e.g.: 60s timeout, 55s ping time), it sounds
stupid to do so but we can't prevent nor check that. So let's keep it
simple.
Sylvain
prev parent reply other threads:[~2015-10-07 9:22 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
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 [this message]
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=20151007092258.GA15119@gradator.net \
--to=sylvain.rochet@finsecur$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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