Linux IIO development
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Mike Frysinger <vapier@gentoo.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"device-drivers-devel@blackfin.uclinux.org"
	<device-drivers-devel@blackfin.uclinux.org>,
	Sonic Zhang <sonic.zhang@analog.com>
Subject: Re: [PATCH 12/14] staging: iio: adc: new driver for ADT7408 temperature sensors
Date: Mon, 25 Oct 2010 07:12:35 -0700	[thread overview]
Message-ID: <20101025141235.GA18016@ericsson.com> (raw)
In-Reply-To: <4CC56D50.3000804@cam.ac.uk>

On Mon, Oct 25, 2010 at 07:43:12AM -0400, Jonathan Cameron wrote:
[ ... ]

> > I did not refer to the chips with generic ADC sensors.
> > The chips I referred to are AD7414/15, ADT75, ADT7310, ADT7408, and ADT7410,
> > though I may have missed some.
> You clearly got further through the set than I have so far! (I'd only come across
> the first 2 of those)  Agreed, all of these appear to be temperature only and at
> a quick look they are typically slow and low resolution so that set definitely
> want to be in hwmon.
> 
> For those parts with actual hwmon drivers, ad7414/15 and adt7408 (based on a quick
> grep unless Guenter has others queued). Lets drop them for now from the merge.
> 

Nothing queued here. Not that I would mind doing the driver conversions for ADT7310
and ADT7410 if needed, but I would need HW (eval boards) for testing.

> For the others lets put a todo in place to convert them to hwmon.  Nothing wrong
> with putting them in staging (under IIO or otherwise) in the meantime as far
> as I am concerned.
> 
> > 
> >> We went through this in a lot of depth back when IIO first came about.
> >> There is a boundary. We just need to pin down where it is.
> > 
> > For the ambient temperature sensors on the other chips - did you consider
> > adding hwmon device entries for those ? There may of course be reasons against
> > doing that, but it may be an option. There are other drivers outside the hwmon 
> > directory which call hwmon_device_register(), so it is not a new concept.
> It depends on whether they are generally useful for temperature monitoring.
> On the whole they are giving one the value on a particular bit of silicon
> in the chip (not the ambient temperature near by). They aren't reading it for
> monitoring purposes, but because it is needed to calibrate the other sensors in
> the package.  We even have devices with multiple temperature sensors, one on
> each MEMs device. Also they often get read into a buffer with all the rest
> of the channels.
> 
> Lets leave the decision on this up to individual driver writers.  If they are using
> the device to do hwmon stuff as well as whatever else it is for then we encourage them
> to register it with hwmon as you suggest.
> 
Ok, makes sense.

Thanks,
Guenter

  reply	other threads:[~2010-10-25 14:12 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-23 20:29 [PATCH 01/14] staging: iio: adc: new driver for AD7152/3 devices Mike Frysinger
2010-10-23 20:29 ` [PATCH 02/14] staging: iio: adc: new driver for AD7291 devices Mike Frysinger
2010-10-24 21:32   ` Jonathan Cameron
2010-10-23 20:29 ` [PATCH 03/14] staging: iio: adc: new driver for AD7298 devices Mike Frysinger
2010-10-24 21:49   ` Jonathan Cameron
2010-10-23 20:29 ` [PATCH 04/14] staging: iio: adc: new driver for AD7314 devices Mike Frysinger
2010-10-24 21:56   ` Jonathan Cameron
2010-10-26  3:35     ` Zhang, Sonic
2010-10-23 20:29 ` [PATCH 05/14] staging: iio: adc: new driver for AD7414/5 devices Mike Frysinger
2010-10-24 22:03   ` Jonathan Cameron
2010-10-23 20:29 ` [PATCH 06/14] staging: iio: adc: new driver for AD7416/7/8 devices Mike Frysinger
2010-10-24 22:19   ` Jonathan Cameron
2010-10-23 20:29 ` [PATCH 07/14] staging: iio: adc: new driver for AD7475/6/6A/7/7A/8/8A and AD7495 devices Mike Frysinger
2010-10-24 21:14   ` [Device-drivers-devel] " Mike Frysinger
2010-10-24 22:21   ` Jonathan Cameron
2010-10-23 20:29 ` [PATCH 08/14] staging: iio: adc: new driver for AD7745/6/7 devices Mike Frysinger
2010-10-24 22:36   ` Jonathan Cameron
2010-10-23 20:29 ` [PATCH 09/14] staging: iio: adc: new driver for AD7816 devices Mike Frysinger
2010-10-23 20:29 ` [PATCH 10/14] staging: iio: adc: new driver for ADT75 temperature sensors Mike Frysinger
2010-10-23 20:29 ` [PATCH 11/14] staging: iio: adc: new driver for ADT7310 " Mike Frysinger
2010-10-23 20:29 ` [PATCH 12/14] staging: iio: adc: new driver for ADT7408 " Mike Frysinger
2010-10-24 22:53   ` Jonathan Cameron
2010-10-24 23:47     ` Guenter Roeck
2010-10-25 10:28       ` Jonathan Cameron
2010-10-26  4:20       ` Zhang, Sonic
2010-10-26  5:08         ` Guenter Roeck
2010-10-26  5:38           ` Zhang, Sonic
2010-10-26  9:14         ` Jonathan Cameron
2010-10-25  0:46     ` Guenter Roeck
2010-10-25 10:32       ` Jonathan Cameron
2010-10-25 11:19         ` Guenter Roeck
2010-10-25 11:43           ` Jonathan Cameron
2010-10-25 14:12             ` Guenter Roeck [this message]
2010-10-25 16:18               ` Hennerich, Michael
2010-10-25 11:47           ` [Device-drivers-devel] " Hennerich, Michael
2010-10-26  3:21             ` Zhang, Sonic
2010-10-26  3:27     ` Zhang, Sonic
2010-10-26  3:52       ` Guenter Roeck
2010-10-26  9:15       ` Jonathan Cameron
2010-10-26 14:33         ` Guenter Roeck
2010-11-01 10:56           ` Jonathan Cameron
2010-11-01 14:37             ` Guenter Roeck
2010-11-01 15:19               ` Jonathan Cameron
2010-10-23 20:29 ` [PATCH 13/14] staging: iio: adc: new driver for ADT7410 " Mike Frysinger
2010-10-23 20:29 ` [PATCH 14/14] staging: iio: adc: new ad799x driver Mike Frysinger
2010-10-24 21:14   ` [Device-drivers-devel] " Mike Frysinger
2010-10-24 22:55   ` Jonathan Cameron
2010-10-24 21:09 ` [PATCH 01/14] staging: iio: adc: new driver for AD7152/3 devices Jonathan Cameron

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=20101025141235.GA18016@ericsson.com \
    --to=guenter.roeck@ericsson.com \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=jic23@cam.ac.uk \
    --cc=linux-iio@vger.kernel.org \
    --cc=sonic.zhang@analog.com \
    --cc=vapier@gentoo.org \
    /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