From: Wolfram Sang <w.sang@pengutronix.de>
To: Wolfgang Denk <wd@denx.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: Tue, 6 Dec 2011 22:59:36 +0100 [thread overview]
Message-ID: <20111206215936.GE14154@pengutronix.de> (raw)
In-Reply-To: <20111204170810.8370625EA22@gemini.denx.de>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
Hi Wolfgang,
> > 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
...
> 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.
I never said the features are useless. I also didn't say you should do
everything in userspace. I asked because I wanted to know what exactly are the
things you are missing from what is possible today. So, this could maybe be
added to the current watchdog frameworks. Adding a new framework (with lots of
issues) and requiring a new set of drivers won't cut it.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-12-06 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 9:53 Heiko Schocher
2011-12-04 12:59 ` Wolfram Sang
2011-12-04 17:08 ` Wolfgang Denk
2011-12-05 12:26 ` Alan Cox
2011-12-07 6:37 ` Heiko Schocher
2011-12-07 17:23 ` Alan Cox
2011-12-06 21:59 ` Wolfram Sang [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=20111206215936.GE14154@pengutronix.de \
--to=w.sang@pengutronix.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=wd@denx.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
Powered by JetHome