Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: michael.hennerich@analog.com
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Drivers <Drivers@analog.com>,
	"device-drivers-devel@blackfin.uclinux.org"
	<device-drivers-devel@blackfin.uclinux.org>
Subject: Re: [PATCH] IIO: ADC: New driver for the AD7298 8-channel SPI ADC
Date: Wed, 23 Feb 2011 11:02:19 +0000	[thread overview]
Message-ID: <4D64E93B.1030509@cam.ac.uk> (raw)
In-Reply-To: <4D6426ED.3090101@analog.com>

On 02/22/11 21:13, Michael Hennerich wrote:
> On 02/22/2011 03:34 PM, Jonathan Cameron wrote:
>> On 02/14/11 14:03, michael.hennerich@analog.com wrote:
>>   
>>> From: Michael Hennerich <michael.hennerich@analog.com>
>>>
>>> This patch adds support for the
>>> AD7298:  8-Channel, 1MSPS, 12-Bit SAR ADC with Temperature Sensor
>>> via SPI bus.
>>>
>>> This patch replaces the existing ad7298.c driver completely.
>>> It was necessary since, the old driver did not comply with the
>>> IIO ABI for such devices.
>>>     
>> Guess that's one approach to fixing up a driver!
>> Anyhow, it's nice and clean now.
>>   
> Rewrite is sometimes easier than fix ;-)
> 
>> Couple of trivial points inline.  You may need some locking
>> in the temperature read function, fix that or explain what
>> I'm missing before sending on to Greg, the other bits are up
>> to you.
>>   
> Good point.
>> I see the original driver used a busy pin. For the record, could you
>> also explain any disadvantages in this new one not doing that?
>>   
> Well the busy pin is only used to for on-die temperature measurements.
> The busy time is pretty deterministic, wasting a GPIO or interrupt line
> is pointless!
> Sleep for at least 100us, does the job. I see no point what this task
> could do useful otherwise,
> since it would also result in a sleep.
> 
> Last but not least - this is a 8-Channel ADC, the temperature diode is
> only the hard wired 9th channel,
> with pretty limited use. The busy pin might be useful for none OS 8-bit
> micro systems, but here
> we simply put the task asleep.
Good, that gives us a clean explanation to refer people to if they ask
this question in the future.  Thanks for clearing that up.

...

  reply	other threads:[~2011-02-23 11:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 14:03 [PATCH] IIO: ADC: New driver for the AD7298 8-channel SPI ADC michael.hennerich
2011-02-15 11:47 ` Shubhrajyoti
2011-02-15 12:02   ` Michael Hennerich
2011-02-22 14:34 ` Jonathan Cameron
2011-02-22 21:13   ` Michael Hennerich
2011-02-23 11:02     ` Jonathan Cameron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-24 11:32 michael.hennerich

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=4D64E93B.1030509@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=Drivers@analog.com \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=michael.hennerich@analog.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