From: Guenter Roeck <guenter.roeck@ericsson.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] lm-sensors: Add support for new hwmon
Date: Wed, 30 Jun 2010 15:30:55 +0000 [thread overview]
Message-ID: <20100630153055.GB4974@ericsson.com> (raw)
In-Reply-To: <1277877978-27726-1-git-send-email-guenter.roeck@ericsson.com>
On Wed, Jun 30, 2010 at 11:22:48AM -0400, Jean Delvare wrote:
> Hi Guenter,
>
> On Wed, 30 Jun 2010 07:20:21 -0700, Guenter Roeck wrote:
> > On Wed, Jun 30, 2010 at 09:50:51AM -0400, Jean Delvare wrote:
> > > Hi Guenter,
> > >
> > > On Tue, 29 Jun 2010 23:06:18 -0700, Guenter Roeck wrote:
> > > > This patch adds support for the following new attributes to libsensors and
> > > > to the sensors command.
> > > >
> > > > inX_lcrit
> > > > inX_crit
> > > > inX_fault
> > > > temp_lcrit
> > > > powerX_cap
> > > > powerX_max
> > > > powerX_crit
> > > > powerX_alarm
> > > > powerX_fault
> > > > currX_lcrit
> > > > currX_crit
> > > > currX_fault
> > >
> > > Fair enough, assuming these matches the additions to
> > > Documentation/hwmon/sysfs-interface. I'm a little curious about
> > > inX_fault, powerX_fault and currX_fault though. _fault files are for
> > > hardware failures. While I can imagine a thermal diode failing, how
> > > could a voltage or current sensor be broken?
> >
> > I thought about that myself, ie if it would be better to introduce
> > _lcrit_alarm and _crit_alarm instead. My ultimate conclusion was that the chips
> > I am working with right now are voltage controllers, and thus exceeding the limits
> > points to a fault rather than a critical limit alarm. Action taken by the chip
> > is typically also drastic; raising a fault alarm is only the least drastic action
> > possible. More likely the chip will be configured to reset the board or shut down
> > power completely.
> >
> > This applies to chips which have both "alarm" and "critical" limits.
> >
> > So even if the event does not exactly match the "fault" description in the API,
> > I concluded that "fault" is a better match to what happens than "crit_alarm" or
> > "lcrit_alarm". I don't feel too strongly about that, though, so if you disagree
> > I'll be happy to change the code and API to "lcrit_alarm" and "crit_alarm"
> > for those sensors.
>
> Yes, I disagree, and yes, please change. "alarms" in the hwmon
> framework are flags raised because of out-of-limits measurements, and
> we should stick to this to avoid any confusion. And "faults" are
> something else. Let's stick to this.
>
Ok, I'll do that. I'll also re-submit the driver for SMM665 to reflect the changes.
> in[0-*]_fault should probably be removed from
> Documentation/hwmon/sysfs-interface altogether, to clear the confusion.
Guess so.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2010-06-30 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 6:06 [lm-sensors] [PATCH] lm-sensors: Add support for new hwmon Guenter Roeck
2010-06-30 13:50 ` Jean Delvare
2010-06-30 14:20 ` Guenter Roeck
2010-06-30 15:22 ` Jean Delvare
2010-06-30 15:30 ` Guenter Roeck [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=20100630153055.GB4974@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=lm-sensors@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 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.