public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Guenter Roeck <guenter.roeck@ericsson.com>,
	lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: [lm-sensors] Adding critical/fault limits to hwmon sysfs API
Date: Thu, 24 Jun 2010 08:34:31 +0200	[thread overview]
Message-ID: <20100624083431.6487e7fe@hyperion.delvare> (raw)
In-Reply-To: <20100624000916.GA8809@sirena.org.uk>

On Thu, 24 Jun 2010 01:09:17 +0100, Mark Brown wrote:
> On Wed, Jun 23, 2010 at 02:43:46PM +0200, Jean Delvare wrote:
> 
> > For temperatures, we have temp[1-*]_crit, for the critical limit on the
> > high end. We don't have a name for the critical limit on the low end,
> > because no chip ever implemented that. The name we chose doesn't offer
> 
> FWIW battery monitoring chips are likely to implement under temperature
> warnings - the Wolfson chargers do, for example.  Low temperature can be
> as problematic as high temperature for the chemistry.

We already have temp[1-*]_min. We would have to add temp[1-*]_lcrit
only if a chip has 2 lower limits, one which is only a warning and one
which is critical.

-- 
Jean Delvare

      reply	other threads:[~2010-06-24  6:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-20 16:37 Adding critical/fault limits to hwmon sysfs API Guenter Roeck
2010-06-23 12:43 ` [lm-sensors] " Jean Delvare
2010-06-23 13:31   ` Guenter Roeck
2010-06-23 14:29     ` Jean Delvare
2010-06-23 15:03       ` Guenter Roeck
2010-06-23 16:34         ` Jean Delvare
2010-06-23 17:21           ` Guenter Roeck
2010-06-24  0:09   ` Mark Brown
2010-06-24  6:34     ` Jean Delvare [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=20100624083431.6487e7fe@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=guenter.roeck@ericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.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