From: Jean Delvare <khali@linux-fr.org>
To: guenter.roeck@ericsson.com
Cc: Hans de Goede <hdegoede@redhat.com>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
Wim Van Sebroeck <wim@iguana.be>,
Thilo Cestonaro <thilo.cestonaro@ts.fujitsu.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
LM Sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [PATCH 5/5] hwmon/sch5636: Add support for the integrated watchdog
Date: Mon, 12 Sep 2011 20:03:02 +0200 [thread overview]
Message-ID: <20110912200302.28dbfdfd@endymion.delvare> (raw)
In-Reply-To: <1315848826.2455.193.camel@groeck-laptop>
On Mon, 12 Sep 2011 10:33:46 -0700, Guenter Roeck wrote:
> On Mon, 2011-09-12 at 05:57 -0400, Hans de Goede wrote:
> > Add support for the watchdog integrated into the (Fujitsu Theseus version of)
> > the sch5636 superio hwmon part. Using the new watchdog timer core.
> >
> > Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> > ---
> > drivers/hwmon/sch5636.c | 233 ++++++++++++++++++++++++++++++++++++++++++++++-
> > 1 files changed, 231 insertions(+), 2 deletions(-)
> >
> [ resent to proper thread ]
>
> Given that this is no longer a pure hwmon driver, it may make sense to
> split it into separate mfd/hwmon/watchdog drivers. But on the other side
> I notice that other drivers in the hwmon directory implement watchdog
> functionality as well. Bad precedent :(.
IIRC the first driver doing this was one of the FSC drivers and this was
before the MFD framework was created. It was simply never migrated, and
other drivers followed the trend.
> Wonder what happens with those watchdogs if HWMON is disabled.
Then the watchdog feature isn't available. The idea as I understand it
is that hardware monitoring is the main feature of these chips and
watchdog is only an add-on, so we don't expect the user to want the
watchdog feature without the hardware monitoring feature.
> Not really sure if we should let this happen, or start being more
> restrictive and enforce cleaner code. Jean, any thoughts/comments ?
I have no objection to merging the code as is, as you found out it's not
doing anything other drivers haven't already.
If anybody cares, that person can clean up one or more drivers, later.
That being said, at least for I2C devices, I don't mind leaving things
as they are, as doing things "better" means more complex code for very
little benefit. For Super-I/O chips which are multifunction by nature,
the MFD framework is certainly the right way to go.
--
Jean Delvare
WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: guenter.roeck@ericsson.com
Cc: Hans de Goede <hdegoede@redhat.com>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
Wim Van Sebroeck <wim@iguana.be>,
Thilo Cestonaro <thilo.cestonaro@ts.fujitsu.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
LM Sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [PATCH 5/5] hwmon/sch5636: Add support for the
Date: Mon, 12 Sep 2011 18:03:02 +0000 [thread overview]
Message-ID: <20110912200302.28dbfdfd@endymion.delvare> (raw)
In-Reply-To: <1315848826.2455.193.camel@groeck-laptop>
On Mon, 12 Sep 2011 10:33:46 -0700, Guenter Roeck wrote:
> On Mon, 2011-09-12 at 05:57 -0400, Hans de Goede wrote:
> > Add support for the watchdog integrated into the (Fujitsu Theseus version of)
> > the sch5636 superio hwmon part. Using the new watchdog timer core.
> >
> > Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> > ---
> > drivers/hwmon/sch5636.c | 233 ++++++++++++++++++++++++++++++++++++++++++++++-
> > 1 files changed, 231 insertions(+), 2 deletions(-)
> >
> [ resent to proper thread ]
>
> Given that this is no longer a pure hwmon driver, it may make sense to
> split it into separate mfd/hwmon/watchdog drivers. But on the other side
> I notice that other drivers in the hwmon directory implement watchdog
> functionality as well. Bad precedent :(.
IIRC the first driver doing this was one of the FSC drivers and this was
before the MFD framework was created. It was simply never migrated, and
other drivers followed the trend.
> Wonder what happens with those watchdogs if HWMON is disabled.
Then the watchdog feature isn't available. The idea as I understand it
is that hardware monitoring is the main feature of these chips and
watchdog is only an add-on, so we don't expect the user to want the
watchdog feature without the hardware monitoring feature.
> Not really sure if we should let this happen, or start being more
> restrictive and enforce cleaner code. Jean, any thoughts/comments ?
I have no objection to merging the code as is, as you found out it's not
doing anything other drivers haven't already.
If anybody cares, that person can clean up one or more drivers, later.
That being said, at least for I2C devices, I don't mind leaving things
as they are, as doing things "better" means more complex code for very
little benefit. For Super-I/O chips which are multifunction by nature,
the MFD framework is certainly the right way to go.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2011-09-12 18:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 9:56 Watchdog timer core enhancements + sch5636 watchdog driver Hans de Goede
2011-09-12 9:56 ` [lm-sensors] Watchdog timer core enhancements + sch5636 watchdog Hans de Goede
2011-09-12 9:56 ` [PATCH 1/5] watchdog_dev: Use wddev function parameter instead of wdd global Hans de Goede
2011-09-12 9:56 ` [lm-sensors] [PATCH 1/5] watchdog_dev: Use wddev function parameter Hans de Goede
2011-09-12 9:56 ` [PATCH 2/5] watchdog_dev: Add support for having more then 1 watchdog Hans de Goede
2011-09-12 9:56 ` [lm-sensors] [PATCH 2/5] watchdog_dev: Add support for having more Hans de Goede
2011-09-12 9:56 ` [PATCH 3/5] watchdog_dev: Add support for dynamically allocated watchdog_device structs Hans de Goede
2011-09-12 9:56 ` [lm-sensors] [PATCH 3/5] watchdog_dev: Add support for dynamically Hans de Goede
2011-09-12 9:56 ` [PATCH 4/5] watchdog_dev: Let the driver update the timeout field on set_timeout success Hans de Goede
2011-09-12 9:56 ` [lm-sensors] [PATCH 4/5] watchdog_dev: Let the driver update the Hans de Goede
2011-09-12 9:57 ` [PATCH 5/5] hwmon/sch5636: Add support for the integrated watchdog Hans de Goede
2011-09-12 9:57 ` [lm-sensors] [PATCH 5/5] hwmon/sch5636: Add support for the Hans de Goede
2011-09-12 17:33 ` [lm-sensors] [PATCH 5/5] hwmon/sch5636: Add support for the integrated watchdog Guenter Roeck
2011-09-12 17:33 ` [lm-sensors] [PATCH 5/5] hwmon/sch5636: Add support for the Guenter Roeck
2011-09-12 17:53 ` [lm-sensors] [PATCH 5/5] hwmon/sch5636: Add support for the integrated watchdog Hans de Goede
2011-09-12 17:53 ` [lm-sensors] [PATCH 5/5] hwmon/sch5636: Add support for the Hans de Goede
2011-09-12 18:03 ` Jean Delvare [this message]
2011-09-12 18:03 ` Jean Delvare
2011-09-12 18:48 ` [lm-sensors] [PATCH 5/5] hwmon/sch5636: Add support for the integrated watchdog Guenter Roeck
2011-09-12 18:48 ` [lm-sensors] [PATCH 5/5] hwmon/sch5636: Add support for the Guenter Roeck
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=20110912200302.28dbfdfd@endymion.delvare \
--to=khali@linux-fr.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=guenter.roeck@ericsson.com \
--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.