All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Jean Delvare <khali@linux-fr.org>
Cc: "R, Durgadoss" <durgadoss.r@intel.com>,
	"Zhang, Rui" <rui.zhang@intel.com>, Len Brown <lenb@kernel.org>,
	lm-sensors@lm-sensors.org, linux-acpi@vger.kernel.org
Subject: Re: CONFIG_THERMAL_HWMON in thermal_sys.c
Date: Tue, 11 Sep 2012 09:35:17 -0700	[thread overview]
Message-ID: <20120911163517.GA14630@roeck-us.net> (raw)
In-Reply-To: <20120911160538.1fc4d23e@endymion.delvare>

On Tue, Sep 11, 2012 at 04:05:38PM +0200, Jean Delvare wrote:
> On Tue, 11 Sep 2012 06:45:05 -0700, Guenter Roeck wrote:
> > I do wonder what is going to happen with existing hwmon temperature sensor
> > drivers which are needed as thermal drivers. Re-write/copy ?
> 
> Have them register as thermal devices and leave their hwmon interface
> unchanged?
> 
> For simple temperature sensor devices, the current situation (expose
> thermal devices as hwmon devices automatically) works well, but if a
> more complex devices (with, say, voltage sensors) needs to be exposed
> as a thermal device then it doesn't work. If we want to handle this
> case, then I see no alternative to having each driver implement both
> interfaces.
> 
Ok, makes sense.

Guenter

WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Jean Delvare <khali@linux-fr.org>
Cc: "R, Durgadoss" <durgadoss.r@intel.com>,
	"Zhang, Rui" <rui.zhang@intel.com>, Len Brown <lenb@kernel.org>,
	lm-sensors@lm-sensors.org, linux-acpi@vger.kernel.org
Subject: Re: [lm-sensors] CONFIG_THERMAL_HWMON in thermal_sys.c
Date: Tue, 11 Sep 2012 16:35:17 +0000	[thread overview]
Message-ID: <20120911163517.GA14630@roeck-us.net> (raw)
In-Reply-To: <20120911160538.1fc4d23e@endymion.delvare>

On Tue, Sep 11, 2012 at 04:05:38PM +0200, Jean Delvare wrote:
> On Tue, 11 Sep 2012 06:45:05 -0700, Guenter Roeck wrote:
> > I do wonder what is going to happen with existing hwmon temperature sensor
> > drivers which are needed as thermal drivers. Re-write/copy ?
> 
> Have them register as thermal devices and leave their hwmon interface
> unchanged?
> 
> For simple temperature sensor devices, the current situation (expose
> thermal devices as hwmon devices automatically) works well, but if a
> more complex devices (with, say, voltage sensors) needs to be exposed
> as a thermal device then it doesn't work. If we want to handle this
> case, then I see no alternative to having each driver implement both
> interfaces.
> 
Ok, makes sense.

Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2012-09-11 16:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11  5:07 CONFIG_THERMAL_HWMON in thermal_sys.c R, Durgadoss
2012-09-11  5:07 ` [lm-sensors] " R, Durgadoss
2012-09-11  5:30 ` Guenter Roeck
2012-09-11  5:30   ` [lm-sensors] " Guenter Roeck
2012-09-11  8:40   ` R, Durgadoss
2012-09-11  8:40     ` [lm-sensors] " R, Durgadoss
2012-09-11  7:12 ` Jean Delvare
2012-09-11  7:12   ` [lm-sensors] " Jean Delvare
2012-09-11  8:55   ` R, Durgadoss
2012-09-11  8:55     ` [lm-sensors] " R, Durgadoss
2012-09-11  9:03     ` Jean Delvare
2012-09-11  9:03       ` [lm-sensors] " Jean Delvare
2012-09-11  9:24       ` R, Durgadoss
2012-09-11  9:24         ` [lm-sensors] " R, Durgadoss
2012-09-11  9:49         ` Jean Delvare
2012-09-11  9:49           ` [lm-sensors] " Jean Delvare
2012-09-11 13:45           ` Guenter Roeck
2012-09-11 13:45             ` [lm-sensors] " Guenter Roeck
2012-09-11 14:05             ` Jean Delvare
2012-09-11 14:05               ` [lm-sensors] " Jean Delvare
2012-09-11 16:35               ` Guenter Roeck [this message]
2012-09-11 16:35                 ` Guenter Roeck

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=20120911163517.GA14630@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=durgadoss.r@intel.com \
    --cc=khali@linux-fr.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.