From: Wolfgang Denk <wd@denx.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Heiko Schocher <hs@denx.de>,
linux-watchdog@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Stefan Roese <sr@denx.de>
Subject: Re: [PATCH] RFC, watchdog: add generic wdt driver API
Date: Sun, 04 Dec 2011 18:08:10 +0100 [thread overview]
Message-ID: <20111204170810.8370625EA22@gemini.denx.de> (raw)
In-Reply-To: <20111204125928.GB5788@pengutronix.de>
Dear Wolfram,
In message <20111204125928.GB5788@pengutronix.de> you wrote:
>
> > This patch is a port from Linux 2.4 and thought as an RFC, so comments
> > are greately appreciated. First question is, has this watchdog driver
> > API a chance to go in mainline? If so, what is the direction to
> > go to push it ...
>
> I don't see this flying. We finally have a watchdog framework in the kernel
> which covers the long existing API used by existing drivers. If I understood it
> right, this additional API needs new drivers for all the watchdogs? Also, I
> didn't fully get what you are missing from the combination of the current API
> and additional userspace-handling? (check [1] for one example, not really
Watchdog support is somethign that usually comes into play for
security-critical devices. Doing this stuff in user space may or may
not be sufficient; for example, we've seen requirements where all
related code must be running from ROM (including all other kernel
code).
Also, the implementation submitted by Heiko allows for easy watchdog
control for kernel tasks. I don;t see a good way to do this through
user space.
But as Heikow wrote; this is a RFC patch, and the main purpose is to
try to find out if it has a chance to go into mainline - several
earlier attempts (which go back as far as 2002 - see for example [1],
[2]) all failed with similar arguments like yours: "It's too complex,
we already have watchdog support, nobody needs this". Funny enough
that we have a number of customers who consider the existing wdt
support unsufficient for their use cases. We've been using it on all
kinds on PPC systems, and now on ARM as well.
We will not fight for inclusion of this driver, we just wat to know if
it's worth investing efforts to get it accepted or if this is a lost
case.
[1] http://osdir.com/ml/linux.ports.ppc.embedded/2003-12/msg00188.html
[2] http://thread.gmane.org/gmane.linux.kernel/884598
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Gewöhnlich glaubt der Mensch, wenn er nur Worte hört, es müsse sich
dabei doch auch was denken lassen. -- Goethe, Faust I
next prev parent reply other threads:[~2011-12-04 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 9:53 [PATCH] RFC, watchdog: add generic wdt driver API Heiko Schocher
2011-12-04 12:59 ` Wolfram Sang
2011-12-04 17:08 ` Wolfgang Denk [this message]
[not found] ` <20111204170810.8370625EA22-C2Gvrrd9BC/j/ljBK/0BTg@public.gmane.org>
2011-12-05 12:26 ` Alan Cox
[not found] ` <20111205122649.6fc6aed2-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
2011-12-07 6:37 ` Heiko Schocher
[not found] ` <4EDF099E.80207-ynQEQJNshbs@public.gmane.org>
2011-12-07 17:23 ` Alan Cox
2011-12-06 21:59 ` Wolfram Sang
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=20111204170810.8370625EA22@gemini.denx.de \
--to=wd@denx.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hs@denx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=sr@denx.de \
--cc=w.sang@pengutronix.de \
/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).