From: Wolfram Sang <w.sang@pengutronix.de>
To: Heiko Schocher <hs@denx.de>
Cc: linux-watchdog@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Wolfgang Denk <wd@denx.de>,
Stefan Roese <sr@denx.de>
Subject: Re: [PATCH] RFC, watchdog: add generic wdt driver API
Date: Sun, 4 Dec 2011 13:59:28 +0100 [thread overview]
Message-ID: <20111204125928.GB5788@pengutronix.de> (raw)
In-Reply-To: <1322992423-21683-1-git-send-email-hs@denx.de>
[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]
On Sun, Dec 04, 2011 at 10:53:43AM +0100, Heiko Schocher wrote:
> This driver implements a character device with major number 10 and minor
> number 130. It is a software abstraction of the hardware watchdog
> with two different APIs. While the driver periodically triggers the
> hardware watchdog, the software can setup independent timeout periods.
>
> "REGULAR API"
> provides a facility to setup a watchdog behaviour shared by all
> processes using the driver. This interface uses read, write and
> ioctl calls.
>
> "CHAIN API"
> can be used to register configurable "watchdog chains" from
> kernel and/or user space. This interface uses ioctl calls only.
>
> more info about this two APIs are found in
> Documentation/watchdog/wd-api.txt
>
> Different hardware layers can attached to this driver. As this
> is an RFC add in this patch also, as an example for an hardware
> layer, support for the arm davinci internal WDT.
>
> Signed-off-by: Heiko Schocher <hs@denx.de>
> Cc: linux-watchdog@vger.kernel.org
> Cc: devicetree-discuss@lists.ozlabs.org
> Cc: linux-kernel@vger.kernel.org
> Cc: Wolfgang Denk <wd@denx.de>
> Cc: Stefan Roese <sr@denx.de>
>
> ---
> 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
covering your use case but showing a potential way maybe) Didn't look much at
the code, but glimpsing says it needs some cleanups regarding comments and
excessive debug output.
Regards,
Wolfram
[1] http://lists.freedesktop.org/archives/systemd-devel/2011-November/003802.html
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-12-04 12: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 [this message]
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
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=20111204125928.GB5788@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
all inboxes | Powered by JetHome®