From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Daniel Newby" <daniel.a.newby@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: how to allow board writers to customize driver behavior (watchdog here)
Date: Thu, 24 May 2007 11:08:25 -0400 [thread overview]
Message-ID: <8bd0f97a0705240808v7073f0f7g182fabddc3b3ed97@mail.gmail.com> (raw)
In-Reply-To: <ba1ee50c0705240147t3d2ebf43w8cb0335bc7c239e4@mail.gmail.com>
On 5/24/07, Daniel Newby <daniel.a.newby@gmail.com> wrote:
> On 5/24/07, Paul Mundt <lethal@linux-sh.org> wrote:
> > It sounds like your constraining your driver based on terminology.
> > Watchdogs on most embedded platforms support either a 'reset' mode or
> > otherwise act as periodic timers, trying to push both of these
> > functionalities in to a watchdog driver is rather pointless.
> > CONFIG_WATCHDOG implies 'reset' mode by definition.
>
> I agree for a product in the hands of a customer: let the watchdog
> pull your bacon out of the fire.
>
> But what about debugging? Suppose your embedded computer with custom
> drivers locks up solid every few hundred hours. It would be nice if
> the watchdog gave a stack dump instead erasing the evidence. How about
> having "action=reset" and "action=debug"?
"action" corresponds one to one with the functionality of the hardware
device ... what the board guy wishes to do when the interrupt expires
is up to the board guy and that may include doing a debug dump
somewhere ... that is most definitely not a realm i want to tread into
it ;)
-mike
next prev parent reply other threads:[~2007-05-24 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 4:21 Mike Frysinger
2007-05-24 5:23 ` Paul Mundt
2007-05-24 8:47 ` Daniel Newby
2007-05-24 9:32 ` Paul Mundt
2007-05-24 15:08 ` Mike Frysinger [this message]
2007-05-24 13:29 ` Robin Getz
2007-05-24 15:23 ` Paul Mundt
2007-05-24 17:32 ` Robin Getz
2007-05-25 4:04 ` Paul Mundt
2007-05-25 10:09 ` Daniel Newby
2007-05-25 17:55 ` Mike Frysinger
2007-05-24 15:12 ` Mike Frysinger
2007-05-24 10:01 ` Alan Cox
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=8bd0f97a0705240808v7073f0f7g182fabddc3b3ed97@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=daniel.a.newby@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®