From: Len Brown <lenb@kernel.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Mark M. Hoffman" <mhoffman@lightlink.com>,
"Thomas, Sujith" <sujith.thomas@intel.com>,
lm-sensors@lm-sensors.org, linux-acpi@vger.kernel.org, "Zhang,
Rui" <rui.zhang@intel.com>
Subject: Re: [lm-sensors] The new thermal management sysfs class, and hwmon
Date: Thu, 7 Feb 2008 02:01:35 -0500 [thread overview]
Message-ID: <200802070201.36016.lenb@kernel.org> (raw)
In-Reply-To: <20080205145550.GA24128@khazad-dum.debian.net>
On Tuesday 05 February 2008 09:55, Henrique de Moraes Holschuh wrote:
> > > The only duplication which I can see of is in the "reporting of
> > > temperature", which is quite reasonable for a thermal management module
> > > to have.
> >
> > Well, HdMH and I apparently disagree about this. All I really care
> > about is that the temp info should be available through /sys/class/hwmon.
> > Many people just want to check their temps, without diving into the fine
> > details of a "thermal management solution".
>
> Well, I strongly care for not having to duplicate the entire sysfs code of
> the thinkpad-acpi thermal management subdrivers (fan control, thermal
> readings) to a new interface AND maybe even finding myself in need to add a
> *third* platform device and driver to thinkpad-acpi just because the new
> interface didn't even try to be as compatible with hwmon as possible :-(
I expect that Thinpads will continue to be optimized primarily for
Windows via ACPI. I don't expect thinkpads to suddenly switch over
to OSPM user-space thermal control -- because Windows doesn't do that.
So I don't think any bad things will happen if thinkpad-acpi
doesn't respond to this.
I do agree that we should make the I/F the same, where possible,
(that was my original proposal)
I'm delighted to hear that the hwmon community is open minded
about expanding the capabilities of hwmon. We should definately
look into that. While Menlo will likely start shipping with
the current solution, there is no reason we can't evolve it over time --
for we know the guys writing the software that will use this I/F...
thanks,
-Len
next prev parent reply other threads:[~2008-02-07 7:03 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 [this message]
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=200802070201.36016.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
--cc=rui.zhang@intel.com \
--cc=sujith.thomas@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