All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Mario Domenech Goulart <mario@ossystems.com.br>,
	Jonathan Cameron <jic23@kernel.org>,
	linux-iio@vger.kernel.org
Subject: Re: RFC: driver for TI ADS124x ADC series
Date: Wed, 31 Jul 2013 08:54:54 +0200	[thread overview]
Message-ID: <51F8B4BE.8000308@metafoo.de> (raw)
In-Reply-To: <CAP9ODKqt35M833c990JhGeYvQJgK77_my01qdFwahF4xF-iEQw@mail.gmail.com>

On 07/31/2013 12:46 AM, Otavio Salvador wrote:
> On Fri, Jul 26, 2013 at 6:10 PM, Mario Domenech Goulart
> <mario@ossystems.com.br> wrote:
>> Hi,
>>
>> We are working on a driver for TI ADS124x ADC series (ADS1246,
>> ADS1247 and ADS1248.  Datasheet: http://www.ti.com/litv/pdf/sbas426g)
>>
>> The attached patch is what we have so far.  It is by no means
>> finished.  We are actually submitting it in the hope you can
>> review it and provide feedback.
>>
>> Some observations and questions in advance:
>>
>> * we've set the chip to only convert on-demand.  I.e., it is not
>>    constantly converting.  Conversions are only performed when
>>    requested via sysfs.  We are not sure about the best approach
>>    with regard to that behavior.  Should it be constantly
>>    converting?
>>
>> * we've set the device as IIO_TEMP, although what is currently
>>    exposed in sysfs is voltage. The chip is targeted to
>>    temperature sensors, but the actual output of the ADC is
>>    voltage, so we don't know exactly what to use as type.
>>
>> * we are aware of some ugly hacks like wait_for_drdy. :-) What's
>>    the best approach to wait for the data ready signal?
>>
>> * in fact we've been mostly working with ADS1247 and haven't
>>    concentrated on supporting ADS1246 and ADS1248 for now, but we
>>    intend to do so.
>
> Could someone give us some feedback on this?
>
> We are really looking for some initial review on this patch so we can
> clean it up and do the need changes to send it for official review
> later.
>

Can you send the patch inline instead of as an attachment?

- Lars


  reply	other threads:[~2013-07-31  6:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 21:10 RFC: driver for TI ADS124x ADC series Mario Domenech Goulart
2013-07-30 22:46 ` Otavio Salvador
2013-07-31  6:54   ` Lars-Peter Clausen [this message]
2013-07-31 11:42     ` Mario Domenech Goulart
2013-08-04 13:54       ` Lars-Peter Clausen
2013-07-31 21:08 ` Jonathan Cameron
2013-08-08 13:53   ` Mario Domenech Goulart

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=51F8B4BE.8000308@metafoo.de \
    --to=lars@metafoo.de \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=mario@ossystems.com.br \
    --cc=otavio@ossystems.com.br \
    /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.