From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Jean Delvare <khali@linux-fr.org>,
"linux-acpi@vger" <linux-acpi@vger.kernel.org>,
lm-sensors@lm-sensors.org, lenb@kernel.org, trenn@suse.de
Subject: Re: Conversion of ACPI fan+thermal to hwmon sysfs
Date: Thu, 8 Mar 2007 10:13:23 -0300 [thread overview]
Message-ID: <20070308131323.GA417@khazad-dum.debian.net> (raw)
In-Reply-To: <1173346084.10227.136.camel@localhost.localdomain>
On Thu, 08 Mar 2007, Zhang Rui wrote:
> First, ACPI thermal zone can be used to set different cooling policies,
> i.e. passive cooling mode and active cooling mode.
> In passive mode, just as Matthew Garrett described, ACPI thermal may
> throttle the CPU if the passive trip point is triggered, i.e. cool a
> thermal zone by decreasing the performance of the devices(always CPU
> now) in the zone.
> The active cooling mode will use one or more active devices(usually fan)
> to decrease the temperature, which consume extra power. And this is
> really like the way that the hwmon is doing.
> So we can only map the active cooling policy to hwmon, right?
Right, which is not to say we can't extend hwmon to also cover passive.
> Second, one ACPI thermal zone may have more than one fan devices, even
> one active trip point may associate with several fan devices. And this
> seems to be different from the sensors, doesn't it?
No, a LM85 does that too. I don't recall if the current interface allows
for that mapping easily, but if it doesn't, it needs to be modified.
> Third, ACPI can not get/set the fan speed. It can only deal with the fan
> D-state. Fan is on in D0 state and off in D3 state.
That is easy to map to hwmon, you just don't implement some of the pwm
stuff.
> IMO, the hwmon sysfs interface make it very convenient for users to
> define the desired fan speed depending on a temperature measurement.
> And it seems that we can't take use of this if we map ACPI thermal and
> fan to hwmon-like sysfs interface, right?
Well, it is certainly not easy. I am not really sure the answer is "we
cannot", though, but I don't really have the inclination to break out the
paper and pencil and start thinking *hard* on it right now, sorry :(
> Oh, a _read-only_ interface? Then, it will be much easier.
> But what is it used for?
Monitoring. It is actually used more than the read-write interface...
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2007-03-08 13:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 18:20 RFC: conversion of ibm-acpi to hwmon sysfs Henrique de Moraes Holschuh
2007-02-26 16:27 ` [lm-sensors] " Jean Delvare
[not found] ` <20070226172716.b2e956b7.khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
2007-02-26 18:06 ` Henrique de Moraes Holschuh
2007-02-27 9:01 ` Jean Delvare
2007-02-27 15:41 ` Henrique de Moraes Holschuh
2007-02-28 14:38 ` Henrique de Moraes Holschuh
2007-03-01 7:10 ` Jean Delvare
2007-02-28 9:31 ` Zhang Rui
2007-02-28 14:34 ` Conversion of ACPI fan+thermal " Henrique de Moraes Holschuh
2007-03-02 1:12 ` Zhang Rui
2007-03-02 11:13 ` Jean Delvare
2007-03-02 11:43 ` Matthew Garrett
2007-03-08 9:28 ` Zhang Rui
2007-03-08 11:13 ` [lm-sensors] " Hans de Goede
2007-03-08 13:13 ` Henrique de Moraes Holschuh [this message]
2007-03-09 8:53 ` Jean Delvare
2007-03-01 7:06 ` [lm-sensors] RFC: conversion of ibm-acpi " 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=20070308131323.GA417@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=khali@linux-fr.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=rui.zhang@intel.com \
--cc=trenn@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).