From: Jean Delvare <khali@linux-fr.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
linux-acpi@vger.kernel.org, lm-sensors@lm-sensors.org,
lenb@kernel.org, konstantin.a.karasyov@intel.com
Subject: Re: Conversion of ACPI fan+thermal to hwmon sysfs
Date: Fri, 2 Mar 2007 12:13:04 +0100 [thread overview]
Message-ID: <20070302121304.9db20131.khali@linux-fr.org> (raw)
In-Reply-To: <1172797936.14827.33.camel@localhost.localdomain>
Hi Zhang,
> On Thu, 2007-03-01 at 08:06 +0100, Jean Delvare wrote:
> > Indeed, ACPI thermal zone may have more thermal trip points than the
> > hwmon interface specifies. Two of the trip points can be mapped to
> > temp1_max and temp1_crit, respectively. If we want to handle them all,
> > then probably we have to implement Henrique's suggestion and really
> > think in terms of thermal zones, i.e. the trip points would be mapped
> > to temp1_auto_point[1-*]_temp and possibly associated with a fan speed
> > output.
>
> Well, ACPI thermal zones are not only a logical collection of interfaces
> to temperature sensors, trip points and thermal property information,
> but also take charge of thermal controls, i.e. setting platform's
> cooling mode policies.
> I don't know if I missed something, but from Documentation/hwmon/sysfs-
> interface, I can't find any interface that make it possible.
As I don't know what these "cooling mode policies" are, I can't really
tell. Trip points in hwmon let the user define the desired fan speed
depending on a temperature measurement, and that's about it. You can't
associate other actions at the moment, essentially because hardware
monitoring chips themselves can't do anything else. If it would be
convenient for the ACPI case to add something else, we can discuss
additional interface files.
> And, porting ACPI fan and thermal zones to the hwmon model? That is
> really complicated.
> Add Len and Konstantin to cc list and see if they have any ideas. :)
My original idea was to simply add a read-only hwmon-like interface to
the acpi fan and thermal modules. I didn't plan to replace the current
interfaces offered by these modules, at least not directly. There must
be many user-space tools and scripts relying on these at the moment, so
we need a transition period anyway.
--
Jean Delvare
next prev parent reply other threads:[~2007-03-02 11:15 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 [this message]
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
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=20070302121304.9db20131.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=hmh@hmh.eng.br \
--cc=konstantin.a.karasyov@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--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;
as well as URLs for NNTP newsgroup(s).