From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: linux-acpi@vger.kernel.org, lm-sensors@lm-sensors.org
Cc: Zhang Rui <rui.zhang@intel.com>,
"Mark M. Hoffman" <mhoffman@lightlink.com>,
Jean Delvare <khali@linux-fr.org>, Len Brown <lenb@kernel.org>
Subject: The new thermal management sysfs class, and hwmon
Date: Sun, 3 Feb 2008 00:26:22 -0200 [thread overview]
Message-ID: <20080203022622.GA995@khazad-dum.debian.net> (raw)
The new thermal managemeny sysfs class that was just merged into acpi-test,
especially when dealing with temperature measurement and fan control, has a
lot of common ground with the hwmon interface.
However, the ACPI model for thermal cooling devices (fans, etc) and thermal
zones (temp sensors) as currently implemented in the sysfs class appears at
first glance to be a lot more simplified than what is available through the
hwmon sysfs ABI (for a lack of a better term to describe the sysfs attribute
specifications).
And the two sysfs ABIs are incompatible. The ACPI one uses low-precision
units, (temperature in 10^0 degrees Celcius), while the hwmon ABI uses
medium precision units (10^-3 degrees Celcius), for example. There is also
no tachometer feedback for fans, etc.
Missing functionality in the new thermal class are apparently mainly related
to the idea of hardware-based temperature limits and alarms, plus any
non-trivial fan control schemes (many chips, and in case of thinkpad-acpi,
EC firmware, have auto-cruise modes, some have more than one automatic fan
control scheme, etc). If I am wrong about this, please correct me.
IMHO, we can probably do better than two incompatible sysfs ABIs for what
ammounts to the same functionality for many userspace applications (i.e.
thermal monitor apps, and fan control and monitoring apps). And it would be
really neat if the new thermal management stuff could just plug into the
already available temperature sensors and fan controllers that follow the
hwmon sysfs ABI.
Any thoughs on this?
--
"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 reply other threads:[~2008-02-03 2:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 2:26 Henrique de Moraes Holschuh [this message]
2008-02-03 9:31 ` The new thermal management sysfs class, and hwmon Zhang Rui
2008-02-03 16:44 ` Mark M. Hoffman
2008-02-03 17:50 ` Henrique de Moraes Holschuh
2008-02-05 10:14 ` Thomas, Sujith
2008-02-05 13:57 ` Mark M. Hoffman
2008-02-05 14:55 ` [lm-sensors] " Henrique de Moraes Holschuh
2008-02-07 7:01 ` Len Brown
2008-02-07 12:30 ` Henrique de Moraes Holschuh
2008-02-06 5:23 ` Thomas, Sujith
2008-02-13 15:10 ` Thomas Renninger
2008-02-14 14:08 ` Matthew Garrett
2008-02-15 11:04 ` Thomas, Sujith
2008-02-15 11:56 ` Matthew Garrett
2008-02-15 12:19 ` [lm-sensors] " Henrique de Moraes Holschuh
2008-02-22 5:47 ` zhangrui
2008-02-22 8:00 ` [lm-sensors] " Hans de Goede
2008-02-22 8:33 ` Zhang, Rui
2008-02-22 10:54 ` Hans de Goede
2008-02-23 7:43 ` Len Brown
2008-02-23 8:29 ` Jean Delvare
2008-02-24 22:52 ` Zhang, Rui
2008-02-25 8:53 ` Hans de Goede
2008-02-23 20:39 ` [lm-sensors] " Henrique de Moraes Holschuh
2008-02-07 6:41 ` Len Brown
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=20080203022622.GA995@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=mhoffman@lightlink.com \
--cc=rui.zhang@intel.com \
/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