From: Daniel Walker <dwalker@fifo99.com>
To: Jeff Ohlstein <johlstei@codeaurora.org>
Cc: 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: Wed, 30 Mar 2011 09:03:26 -0700 [thread overview]
Message-ID: <1301501006.5346.2.camel@m0nster> (raw)
In-Reply-To: <4D92B43B.5050101@codeaurora.org>
On Tue, 2011-03-29 at 21:40 -0700, Jeff Ohlstein wrote:
> Daniel Walker wrote:
> > Are you saying this is mostly a debugging facility ? The interrupts off
> > thing I can see as just debugging, but I don't understand the bus
> > lockups part.
> >
>
> It isn't just a debugging facility. It is still beneficial to the end user
> in that it restarts the system if there is a bus lockup or a faulty
> interrupt
> handler in a rarely used codepath. This is better than the alternative
> of draining
> the battery and turning off. We want this to be turned on independent of
> what userspace
> one is using, unless they explicitly turn it off themselves.
It doesn't sound too different that all the other watchdogs in
drivers/watchdog/ .. Your just detecting lockups right?
Daniel
next prev parent reply other threads:[~2011-03-30 16:03 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 [this message]
2011-03-30 16:14 ` Jamie Iles
2011-04-28 17:19 ` Pavel Machek
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=1301501006.5346.2.camel@m0nster \
--to=dwalker@fifo99.com \
--cc=adharmap@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=gbean@codeaurora.org \
--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).