From: Jean Delvare <khali@linux-fr.org>
To: "R, Durgadoss" <durgadoss.r@intel.com>
Cc: Guenter Roeck <guenter.roeck@ericsson.com>,
platform-driver-x86@vger.kernel.org,
Alan Cox <alan@linux.intel.com>,
lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] A new Subsystem for Current Management
Date: Sun, 6 Nov 2011 14:53:31 +0100 [thread overview]
Message-ID: <20111106145331.2979656f@endymion.delvare> (raw)
In-Reply-To: <D6D887BA8C9DFF48B5233887EF04654109F102E43A@bgsmsx502.gar.corp.intel.com>
On Sat, 5 Nov 2011 22:20:45 +0530, R, Durgadoss wrote:
> > We also have
> >
> > curr[1-*]_crit
>
> In the systems that I used, this 'curr' stuff is more extensive.
> There are at least 3 current limits. The third one is the 'crit'
> Stuff; the HW shuts down the platform when the platform hits crit.
> The other two are kind of 'warnings' that the system can use to
> reduce the consumption so that it never reaches 'crit'.
>
> So, if we are using hwmon for this, we may to extend the ABI
> in terms of these.
Note that in the hwmon sysfs interface, every input traditionally has
up to 3 upper limits: _max, _crit and _emergency in this order. While
the sysfs-interface document doesn't list all of them for each input
type, all this means is that so far no driver needed them and
libsensors doesn't know about them. But they can be added at any time
if the need exists.
> (...)
> May be an initial patch will make things more visible and give more idea
> I guess. Then we can add/modify things from there.
Certainly. It will be easier to evaluate the different options after
seeing actual code.
--
Jean Delvare
next prev parent reply other threads:[~2011-11-06 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-05 7:13 A new Subsystem for Current Management R, Durgadoss
2011-11-05 13:42 ` Bill Gatliff
2011-11-05 16:36 ` [lm-sensors] " R, Durgadoss
2011-11-06 13:13 ` Jean Delvare
2011-11-08 16:54 ` Mark Brown
2011-11-08 16:57 ` Jean Delvare
2011-11-09 12:09 ` Mark Brown
2011-11-05 15:50 ` Guenter Roeck
2011-11-05 16:50 ` R, Durgadoss
2011-11-06 13:53 ` Jean Delvare [this message]
2011-11-06 13:05 ` [lm-sensors] " Jean Delvare
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=20111106145331.2979656f@endymion.delvare \
--to=khali@linux-fr.org \
--cc=alan@linux.intel.com \
--cc=durgadoss.r@intel.com \
--cc=guenter.roeck@ericsson.com \
--cc=lm-sensors@lm-sensors.org \
--cc=platform-driver-x86@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.