All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pádraig Brady" <P@draigBrady.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-watchdog@vger.kernel.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Wim Van Sebroeck <wim@iguana.be>,
	LM Sensors <lm-sensors@lm-sensors.org>,
	Thilo Cestonaro <thilo.cestonaro@ts.fujitsu.com>
Subject: Re: Watchdog timer core enhancements
Date: Thu, 15 Mar 2012 12:39:46 +0000	[thread overview]
Message-ID: <4F61E312.90209@draigBrady.com> (raw)
In-Reply-To: <1331812757-3491-1-git-send-email-hdegoede@redhat.com>

On 03/15/2012 11:59 AM, Hans de Goede wrote:
> Hi,
> 
> Short selfintro for the watchdog people: I'm a FOSS developer / enthusiast
> for close to 15 years now. I've written Linux kernel drivers for a ton
> of webcams and various hwmon IC's.
> 
> Three of the hwmon drivers I maintain are IC's which also include a watchdog
> part in their hwmon solution.
> 
> This is a resend of a series of watchdog_dev patches which I initially send
> on Sep 12 2011:
> http://lists.lm-sensors.org/pipermail/lm-sensors/2011-September/033707.html
> And which unfortunately has seen 0 reviews / feedback since then.
> 
> This resend is re-based on top of v3.3-rc7
> 
> Currently the hwmon drivers I maintain are implementing the watchdog API
> all by themselves, I would very much like to switch them over to
> watchdog_dev to remove a lot of code duplication, but there currently
> are 2 things stopping me from moving them over:
> 
> 1) The driver core only works for 1 watchdog, but both my fschmd and my sch5636
> test systems also have an iTCO watchdog and that tends to load first. Thus when
> writing the fschmd watchdog code I made it support loading either on the
> default watchdog minor, or on one of the additional reserved watchdog minors
> (212-215). The first patch in this series adds support for this to the
> watchdog timer driver core (which was quite straightforward to add).

I noticed Alan Cox recently proposed multiple watchdog device support
https://lkml.org/lkml/2012/2/28/473

cheers,
Pádraig.
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: "Pádraig Brady" <P@draigBrady.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-watchdog@vger.kernel.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Wim Van Sebroeck <wim@iguana.be>,
	LM Sensors <lm-sensors@lm-sensors.org>,
	Thilo Cestonaro <thilo.cestonaro@ts.fujitsu.com>
Subject: Re: [lm-sensors] Watchdog timer core enhancements
Date: Thu, 15 Mar 2012 12:39:46 +0000	[thread overview]
Message-ID: <4F61E312.90209@draigBrady.com> (raw)
In-Reply-To: <1331812757-3491-1-git-send-email-hdegoede@redhat.com>

On 03/15/2012 11:59 AM, Hans de Goede wrote:
> Hi,
> 
> Short selfintro for the watchdog people: I'm a FOSS developer / enthusiast
> for close to 15 years now. I've written Linux kernel drivers for a ton
> of webcams and various hwmon IC's.
> 
> Three of the hwmon drivers I maintain are IC's which also include a watchdog
> part in their hwmon solution.
> 
> This is a resend of a series of watchdog_dev patches which I initially send
> on Sep 12 2011:
> http://lists.lm-sensors.org/pipermail/lm-sensors/2011-September/033707.html
> And which unfortunately has seen 0 reviews / feedback since then.
> 
> This resend is re-based on top of v3.3-rc7
> 
> Currently the hwmon drivers I maintain are implementing the watchdog API
> all by themselves, I would very much like to switch them over to
> watchdog_dev to remove a lot of code duplication, but there currently
> are 2 things stopping me from moving them over:
> 
> 1) The driver core only works for 1 watchdog, but both my fschmd and my sch5636
> test systems also have an iTCO watchdog and that tends to load first. Thus when
> writing the fschmd watchdog code I made it support loading either on the
> default watchdog minor, or on one of the additional reserved watchdog minors
> (212-215). The first patch in this series adds support for this to the
> watchdog timer driver core (which was quite straightforward to add).

I noticed Alan Cox recently proposed multiple watchdog device support
https://lkml.org/lkml/2012/2/28/473

cheers,
Pádraig.

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2012-03-15 12:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 11:59 Watchdog timer core enhancements Hans de Goede
2012-03-15 11:59 ` [lm-sensors] " Hans de Goede
2012-03-15 11:59 ` [PATCH 1/3] watchdog_dev: Add support for having more then 1 watchdog Hans de Goede
2012-03-15 11:59   ` [lm-sensors] " Hans de Goede
2012-03-15 13:11   ` Alan Cox
2012-03-15 13:11     ` [lm-sensors] " Alan Cox
2012-03-15 14:18     ` Hans de Goede
2012-03-15 14:18       ` [lm-sensors] " Hans de Goede
2012-03-15 15:38       ` Alan Cox
2012-03-15 15:38         ` [lm-sensors] " Alan Cox
2012-05-04 12:34         ` Wim Van Sebroeck
2012-05-04 12:34           ` [lm-sensors] " Wim Van Sebroeck
2012-05-07  6:58           ` Hans de Goede
2012-05-07  6:58             ` [lm-sensors] " Hans de Goede
2012-03-15 11:59 ` [PATCH 2/3] watchdog_dev: Add support for dynamically allocated watchdog_device structs Hans de Goede
2012-03-15 11:59   ` [lm-sensors] " Hans de Goede
2012-03-15 11:59 ` [PATCH 3/3] watchdog_dev: Let the driver update the timeout field on set_timeout success Hans de Goede
2012-03-15 11:59   ` [lm-sensors] [PATCH 3/3] watchdog_dev: Let the driver update the timeout field on set_timeout succes Hans de Goede
2012-03-15 12:39 ` Pádraig Brady [this message]
2012-03-15 12:39   ` [lm-sensors] Watchdog timer core enhancements Pádraig Brady
2012-03-15 21:13 ` Wim Van Sebroeck
2012-03-15 21:13   ` [lm-sensors] " Wim Van Sebroeck
2012-03-16  7:43   ` Hans de Goede
2012-03-16  7:43     ` [lm-sensors] " Hans de Goede
2012-03-17 12:56   ` Wolfram Sang
2012-03-17 12:56     ` [lm-sensors] " 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=4F61E312.90209@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hdegoede@redhat.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=thilo.cestonaro@ts.fujitsu.com \
    --cc=wim@iguana.be \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.