From: thierry.reding@avionic-design.de (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] watchdog: Add support for the Avionic Design Xanthos watchdog timer.
Date: Fri, 28 Aug 2009 08:11:08 +0200 [thread overview]
Message-ID: <20090828061108.GA1649@avionic-design.de> (raw)
In-Reply-To: <20090827204448.GL29382@infomag.iguana.be>
* Wim Van Sebroeck wrote:
> Hi Bill,
>
> >> This is the only thing I'm still struggling with: the goal of a watchdog device driver is to make sure that the system reboots when the system isn't stable anymore. So why should you then trigger the interrupt?
> >>
> >
> > ... because a hard reboot might not be the way he wants to resolve the
> > situation.
>
> If your system is unstable then sending a keepalive to the watchdog during
> this interrupt is not going to change anything neither... Or am I missing
> something?
In this case, writing the timeout value to the watchdog is not actually a
keepalive. This is in fact the mechanism used to reset/acknowledge the
watchdog's interrupt.
Thierry
next prev parent reply other threads:[~2009-08-28 6:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090821073105.GC29382@infomag.iguana.be>
2009-08-21 13:10 ` [PATCH] watchdog: Add support for the Avionic Design Xanthos watchdog timer Thierry Reding
2009-08-21 22:34 ` Andrew Morton
2009-08-22 8:18 ` Wim Van Sebroeck
2009-08-24 9:04 ` Thierry Reding
2009-08-24 9:28 ` Thierry Reding
2009-08-27 20:23 ` Wim Van Sebroeck
2009-08-27 20:31 ` Bill Gatliff
2009-08-27 20:44 ` Wim Van Sebroeck
2009-08-28 1:32 ` Bill Gatliff
2009-08-31 12:35 ` Wim Van Sebroeck
2009-08-31 20:06 ` Mark Brown
2009-08-28 6:11 ` Thierry Reding [this message]
2009-08-31 11:58 ` Wim Van Sebroeck
2009-09-21 14:58 ` Thierry Reding
2009-09-23 7:26 ` Wim Van Sebroeck
2009-09-23 11:49 ` Thierry Reding
2009-09-24 11:05 ` Wim Van Sebroeck
2009-09-24 11:09 ` Thierry Reding
2009-08-24 9:11 ` Thierry Reding
2009-08-24 9:13 ` 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=20090828061108.GA1649@avionic-design.de \
--to=thierry.reding@avionic-design.de \
--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 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.