From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Cc: Hartmut Knaack <knaack.h@gmx.de>, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio:adc: Add support for AD7766/AD7767
Date: Thu, 22 Sep 2016 18:14:25 +0100 [thread overview]
Message-ID: <55dbdb2b-9f62-2ec0-f8d7-a941b8c241ab@kernel.org> (raw)
In-Reply-To: <eb7179b0-12ff-5c10-1e33-9d230009dbd2@metafoo.de>
On 20/09/16 21:27, Lars-Peter Clausen wrote:
> On 09/20/2016 05:35 PM, Peter Meerwald-Stadler wrote:
>> On Tue, 20 Sep 2016, Lars-Peter Clausen wrote:
>>
>>> Add support for the AD7766, AD7766-1, AD7766-2, AD7767, AD7767-1, AD7767-2
>>> Analog to Digital converters. It's a family of single channel 24-bit SAR
>>> ADCs. They are all digital interface compatible and the main difference is
>>> the internal decimation rate and analog performance. For communication with
>>> the host processor a SPI interface is used.
>>
>> looks good, nitpicking below
>
> Thanks for the review.
>
>>> +static const struct iio_chan_spec ad7766_channels[] = {
>>> + {
>>> + .type = IIO_VOLTAGE,
>>> + .indexed = 1,
>>
>> have only one channel and still indexed?
>
> To be honest I prefer to make all channels indexed. There is no inherent
> value added by using un-indexed channels. The only thing that changes is the
> naming scheme of the channel attributes. This makes things more complex and
> also adds ambiguity between shared attributes and channel attributes, which
> makes it harder to parse by machines (and maybe also some humans).
Yeah, one of those design decisions from way back that I kind of regret.
Making the modifier optional made sense, but should probably just have had
everything indexed. Ah well, we're stuck now ;)
Anyhow, happy to have indexes if people prefer them.
Jonathan
>
> - Lars
>
prev parent reply other threads:[~2016-09-22 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 15:15 [PATCH] iio:adc: Add support for AD7766/AD7767 Lars-Peter Clausen
2016-09-20 15:35 ` Peter Meerwald-Stadler
2016-09-20 20:27 ` Lars-Peter Clausen
2016-09-22 17:14 ` Jonathan Cameron [this message]
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=55dbdb2b-9f62-2ec0-f8d7-a941b8c241ab@kernel.org \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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;
as well as URLs for NNTP newsgroup(s).