From: Pavel Machek <pavel@ucw.cz>
To: Jamie Iles <jamie@jamieiles.com>
Cc: Daniel Walker <dwalker@fifo99.com>,
Jeff Ohlstein <johlstei@codeaurora.org>,
Bryan Huntsman <bryanh@codeaurora.org>,
David Brown <davidb@codeaurora.org>,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
Stepan Moskovchenko <stepanm@codeaurora.org>,
Gregory Bean <gbean@codeaurora.org>,
Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Subject: Re: [PATCH] msm: watchdog: support watchdog on 8x60 and 8960
Date: Thu, 28 Apr 2011 17:19:10 +0000 [thread overview]
Message-ID: <20110428171909.GC7345@localhost.ucw.cz> (raw)
In-Reply-To: <20110330161419.GB28252@pulham.picochip.com>
> > It doesn't sound too different that all the other watchdogs in
> > drivers/watchdog/ .. Your just detecting lockups right?
>
> There are some watchdogs in there such as
> drivers/watchdog/at91sam9_wdt.c that can't be stopped once enabled so
> the driver sets up a soft timer in the kernel that kicks the watchdog to
> prevent the system rebooting.
>
> With this approach you could have the watchdog always enabled and being
> kicked even if the userspace daemon wasn't running, but with the
> flexibility of kicking it from userspace if you wanted.
sounds like a way to do it.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2011-04-28 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 2:18 [PATCH] msm: watchdog: support watchdog on 8x60 and 8960 Jeff Ohlstein
2011-03-29 19:22 ` Daniel Walker
2011-03-30 4:40 ` Jeff Ohlstein
2011-03-30 16:03 ` Daniel Walker
2011-03-30 16:14 ` Jamie Iles
2011-04-28 17:19 ` Pavel Machek [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=20110428171909.GC7345@localhost.ucw.cz \
--to=pavel@ucw.cz \
--cc=adharmap@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=dwalker@fifo99.com \
--cc=gbean@codeaurora.org \
--cc=jamie@jamieiles.com \
--cc=johlstei@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=stepanm@codeaurora.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).