From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Phil Pokorny <ppokorny@penguincomputing.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Location for thermal drivers
Date: Fri, 12 Nov 2010 14:06:40 -0800 [thread overview]
Message-ID: <1289599600.22931.406.camel@groeck-laptop> (raw)
In-Reply-To: <AANLkTimERGh2yGGX_E_N4ajxg_-0QTFS54QSKj2+AAfF@mail.gmail.com>
On Fri, 2010-11-12 at 16:53 -0500, Phil Pokorny wrote:
> On Fri, Nov 12, 2010 at 12:33 PM, Guenter Roeck
> <guenter.roeck@ericsson.com> wrote:
> > I think a better location for the driver would be drivers/thermal.
> > drivers/hwmon is not really a good fit, since hwmon support for thermal
> > drivers is optional. Potential problem with drivers/thermal is that
> > there are no thermal drivers in there (yet), and there does not seem to
> > be a maintainer.
>
> What is the difference between a "thermal" sensor and a "temperature"
> sensor? Aren't they the same thing?
>
The thermal framework is much more extensive than the hwmon framework.
See Documentation/thermal/sysfs-api.txt for details.
> Why does drivers/thermal exist if there are no drivers in it and no maintainer?
>
The framework resides there. Drivers supporting it are in various
platform directories.
As for why there are no drivers - only the framework - in
drivers/thermal, and why there is no maintainer - no idea.
Guenter
next prev parent reply other threads:[~2010-11-12 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 20:33 Location for thermal drivers Guenter Roeck
2010-11-12 21:53 ` [lm-sensors] " Phil Pokorny
2010-11-12 22:06 ` Guenter Roeck [this message]
2010-11-12 22:39 ` Alan Cox
2010-11-12 23:11 ` Guenter Roeck
2010-11-13 7:21 ` Phil Pokorny
2010-11-13 14:40 ` Guenter Roeck
2010-11-13 17:01 ` 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=1289599600.22931.406.camel@groeck-laptop \
--to=guenter.roeck@ericsson.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=ppokorny@penguincomputing.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