From: "Zhang, Rui" <rui.zhang@intel.com>
To: Hans de Goede <j.w.r.degoede@hhs.nl>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Thomas Renninger <trenn@suse.de>,
"Thomas, Sujith" <sujith.thomas@intel.com>,
"Mark M. Hoffman" <mhoffman@lightlink.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
linux-acpi@vger.kernel.org, lm-sensors@lm-sensors.org,
Jean Delvare <khali@linux-fr.org>, Len Brown <lenb@kernel.org>,
Richard Hughes <hughsient@gmail.com>
Subject: Re: [lm-sensors] The new thermal management sysfs class, and hwmon
Date: Fri, 22 Feb 2008 16:33:26 +0800 [thread overview]
Message-ID: <1203669206.3210.68.camel@localhost.localdomain> (raw)
In-Reply-To: <47BE8105.30301@hhs.nl>
Hi, Hans,
On Fri, 2008-02-22 at 16:00 +0800, Hans de Goede wrote:
> I think all that is really needed and asked for is for the new thermal
> ACPI
> code to:
> 1) provide temp readings in the same format as hwmon (so milli degrees
> celcius,
> not degrees celcius
Agree.
> 2) provide a hwmon interface so that tools like (but not limited too):
> * net-snmp
> * mrtg
> * sensors
> * sensors-applet (gnome)
> * xfce-sensors-applet
> * ksysguard
> * ksensors
> * gkrellm
>
> Can provide temp and fan readings without having to be modified.
hmm, for fan device, maybe something like this?
pwm[1-*]_enable = 1 : manual fan control (using pwm[1-*])
2+: automatic fan control (by acpi thermal driver)
pwm[1-*] = 0 : fan is off.
pwm[1-*] = 255: fan is on.
pwm[1-*] has only two valid values as ACPI fan only support
two states, ON/OFF. and it doesn't need fan[1-*]_input because the fan
speed is not available.
Yes, it can work for ACPI fan although I don't think the existing pwm
hwmon I/F maps well to what we need and it seems like a "forced fit" to
use it. Any better ideas? :)
Thanks,
Rui
> To be clear I am suggesting that the new code exports both:
> 1) the current full fledged thermal acpi zone interface, as designed
> for
> both reading and configuration
> 2) a read only hwmon interface for reporting temps and fans
next prev parent reply other threads:[~2008-02-22 8:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 2:26 The new thermal management sysfs class, and hwmon Henrique de Moraes Holschuh
2008-02-03 9:31 ` 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 [this message]
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=1203669206.3210.68.camel@localhost.localdomain \
--to=rui.zhang@intel.com \
--cc=hmh@hmh.eng.br \
--cc=hughsient@gmail.com \
--cc=j.w.r.degoede@hhs.nl \
--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=mjg59@srcf.ucam.org \
--cc=sujith.thomas@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