From: Drew Fustini <drew@beagleboard.org>
To: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
Cc: Sean Nyekjaer <sean@geanix.com>,
Gregory Clement <gregory.clement@bootlin.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
David Lechner <david@lechnology.com>,
linux-iio@vger.kernel.org
Subject: Re: iio: adc: anyone working on TI ADS7066?
Date: Mon, 22 Mar 2021 21:39:17 -0700 [thread overview]
Message-ID: <20210323043917.GA517382@x1> (raw)
In-Reply-To: <20210320182609.5e4e7f3c@jic23-huawei>
On Sat, Mar 20, 2021 at 06:26:24PM +0000, Jonathan Cameron wrote:
> On Fri, 19 Mar 2021 20:52:34 -0700
> Drew Fustini <drew@beagleboard.org> wrote:
>
> > I have a board with a TI ADS7066 8-channel ADC [1] that I want to get
> > working in Linux. I see there is already driver support in iio for
> > ADS1015, ADS79xx, ADS8344, ADS868x and ADS124S0x.
> >
> > Is anyone already working with the ADS7066 or a similar part in that
> > series?
> >
> > If not, I'll take one of the existing TI drivers as a template for the
> > ADS7066 driver.
> >
> > Thank you,
> > Drew
>
> Hi Drew,
>
> I've not seen anything for this part.
>
> From a 10 second glance at the data sheet I see it's capable of
> ADC / GPIO on each pin. If you plan to support that functionality
> at somepoint make sure to define dt bindings and similar to specify
> which channels are enabled and dynamically create the iio_chan_spec
> array to match. It can be a bit ugly to retrofit later.
Thanks for the feedback. The GPIO functionality is not used on the
custom hardware that I have, so I am thinking I would only implement
the ADC functionality. Is that too short sighted?
> Oh. It does daisy chaining as well. That is always fun to support
> though I guess you may well not have it wired up to do that.
> Oversampling as well - though that looks nice and simple for once.
The hardware I have has two ADS7066 wired up in parallel so I don't
think I would be looking at implementing dasiy chain initially.
Is that ok just implement what I am actually using or is the preference
to have a driver implement all the latent functionality before it would
be merged?
Thanks,
Drew
next prev parent reply other threads:[~2021-03-23 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 3:52 iio: adc: anyone working on TI ADS7066? Drew Fustini
2021-03-20 18:26 ` Jonathan Cameron
2021-03-20 18:26 ` Jonathan Cameron
2021-03-20 18:26 ` Jonathan Cameron
2021-03-23 4:39 ` Drew Fustini [this message]
2021-03-23 11:38 ` 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=20210323043917.GA517382@x1 \
--to=drew@beagleboard.org \
--cc=daniel.baluta@nxp.com \
--cc=david@lechnology.com \
--cc=gregory.clement@bootlin.com \
--cc=jic23@jic23.retrosnub.co.uk \
--cc=linux-iio@vger.kernel.org \
--cc=sean@geanix.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.