[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTimM+9__P4jpvuEL0zDFCyzPX=MrmA@mail.gmail.com>
Date: Thu, 16 Jun 2011 15:10:06 +0200
From: Andrea Galbusera <gizero@...il.com>
To: Wim Van Sebroeck <wim@...ana.be>
Cc: LKML <linux-kernel@...r.kernel.org>,
Linux Watchdog Mailing List <linux-watchdog@...r.kernel.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [RFC] [PATCH 0/10] Generic Watchdog Timer Driver
Hi Wim,
On Wed, Feb 23, 2011 at 9:41 PM, Wim Van Sebroeck <wim@...ana.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.
TIA
Kind regards,
Andrea
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists