Embedded Linux development
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: celinux-dev@tree.celinuxforum.org, linux-embedded@vger.kernel.org
Subject: CELF Project Proposal: Create a watchdog framework for the Linux kernel
Date: Fri, 18 Dec 2009 00:02:15 +0100	[thread overview]
Message-ID: <20091217230215.GC23944@pengutronix.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]

Proposer: Wolfram Sang

Summary: Create a watchdog framework for the Linux kernel

Description: The watchdog API of the Linux kernel is documented and used for
years. Yet, there is no abstraction for its common functionality (open, write,
ioctl, close), so every watchdog driver has to implement those methods on its
own. In addition to the vast amount of code duplication in the kernel source,
this is also error-prone as there are subtle corner-cases in handling the
watchdog and the userspace-input correctly. Although there is code review for
new drivers, it seems very desirable to improve the situation as a whole.

There have been two approaches for a generic watchdog framework, one from Alan
Cox and one from Wim van Sebroeck, the current watchdog maintainer. Sadly,
nothing from those have made it to mainline so far. This is a bit surprising;
although watchdogs are usually rather simple devices, they are crucial for the
stability concept of an enormous number of devices. The benefit of this
proposal is to have a rock-solid, well maintainable and trustworthy watchdog
framework, which makes writing new drivers faster and less error-prone.

Related work:

 * Proposal by Alan Cox:
        http://git.kernel.org/?p=linux/kernel/git/wim/linux-2.6-watchdog-next.git;a=shortlog;h=refs/heads/alan-generic-watchdog

 * Proposal by Wim van Sebroeck:
        http://git.kernel.org/?p=linux/kernel/git/wim/linux-2.6-watchdog-next.git;a=shortlog;h=refs/heads/wim-generic-watchdog

Scope:
        My estimation would be 4 weeks of development and testing

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-12-17 23:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 23:02 Wolfram Sang [this message]
2009-12-17 23:10 ` CELF Project Proposal: Create a watchdog framework for the Linux kernel Tim Bird

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=20091217230215.GC23944@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=celinux-dev@tree.celinuxforum.org \
    --cc=linux-embedded@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