mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wim Van Sebroeck <wim@iguana.be>
To: Andrea Galbusera <gizero@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [RFC] [PATCH 0/10] Generic Watchdog Timer Driver
Date: Fri, 17 Jun 2011 09:11:18 +0200	[thread overview]
Message-ID: <20110617071118.GJ23305@infomag.iguana.be> (raw)
In-Reply-To: <BANLkTimM+9__P4jpvuEL0zDFCyzPX=MrmA@mail.gmail.com>

Hi Andrea,

> On Wed, Feb 23, 2011 at 9:41 PM, Wim Van Sebroeck <wim@iguana.be> wrote:
> > To reduce copying the same code over and over in each watchdog device driver, Alan Cox and myself constructed a new framework/API that consolidates the common watchdog timer driver functions.
> >
> > This framework/API consists of the following patches:
> > part  1: Introduction of the WatchDog Timer Driver Core
> > part  2: Add the basic ioctl functionality
> > part  3: Add the WDIOC_KEEPALIVE ioctl
> > part  4: Add the WDIOC_SETOPTIONS ioctl
> > part  5: Add the WDIOC_SETTIMEOUT and WDIOC_GETTIMEOUT ioctl
> > part  6: Add orphan control
> > part  7: Add the Magic Close feature
> > part  8: Add the nowayout feature
> > part  9: Add support for a miscdev parent device
> > part 10: Add support for extra ioctl calls
> 
> While looking for efforts to provide a generic driver for gpio driven
> watchdog devices, like some simple hardware supervisors, I came into
> this patchset RFC, which turned out to be very interesting to me.
> Maybe I'm looking into the wrong places, but I could not find any
> upstream commit after this RFC.
> Since I don't see any real critic from commenters to the approach you
> are suggesting, I'd like to know if there still is some
> work-in-progress on this.

I was working on it yesterday and will finish testing today.
So expect a new post this afternoon.

I incorporated the comments I received. Orphan control will not be in (as
long as the watchdog device is registered you can reopen it). And we will
add the minimum and maximum timeout in an extra part.

Kind regards,
Wim.


      reply	other threads:[~2011-06-17  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 20:41 Wim Van Sebroeck
2011-02-23 22:19 ` Mike Waychison
2011-06-16 13:10 ` Andrea Galbusera
2011-06-17  7:11   ` Wim Van Sebroeck [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=20110617071118.GJ23305@infomag.iguana.be \
    --to=wim@iguana.be \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gizero@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@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®