From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
linux-kernel@vger.kernel.org,
"Stefan Popa" <stefan.popa@analog.com>,
"Julien Stephan" <jstephan@baylibre.com>
Subject: Re: [PATCH v4 2/2] iio: adc: ad7380: new driver for AD7380 ADCs
Date: Sat, 24 Feb 2024 11:06:40 +0000 [thread overview]
Message-ID: <20240224110640.03f3b857@jic23-huawei> (raw)
In-Reply-To: <CAMknhBGkUP2Tdze5Fa_0qTcCP_OgcTxtczKYZiH1icfuTAEe+g@mail.gmail.com>
On Mon, 19 Feb 2024 13:47:03 -0600
David Lechner <dlechner@baylibre.com> wrote:
> On Wed, Jan 10, 2024 at 2:29 PM David Lechner <dlechner@baylibre.com> wrote:
>
> ...
>
> > +
> > +/* fully differential */
> > +DEFINE_AD7380_DIFFERENTIAL_2_CHANNEL(ad7380_channels, 16);
> > +DEFINE_AD7380_DIFFERENTIAL_2_CHANNEL(ad7381_channels, 14);
> > +/* pseudo differential */
> > +DEFINE_AD7380_DIFFERENTIAL_2_CHANNEL(ad7383_channels, 16);
> > +DEFINE_AD7380_DIFFERENTIAL_2_CHANNEL(ad7384_channels, 14);
> > +
>
> Similar question to [1] in light of [2]: Since AD7383 and AD7384 are
> pseudo-differential, should we handle them differently? I.e. add
> aina-supply and ainb-supply DT properties for the negative inputs
> (typically a V_REF / 2 supply) and remove the differential flag from
> the channel spec.
>
> [1]: https://lore.kernel.org/linux-iio/CAMknhBH2Pqa9xpPxnTCxJegVTbOG-QDeJA4YrQUPfj+hfSs73A@mail.gmail.com/
> [2]: https://lore.kernel.org/linux-iio/CAMknhBF5mAsN1c-194Qwa5oKmqKzef2khXnqA1cSdKpWHKWp0w@mail.gmail.com/
Yes. I think that gives a more intuitive interface for users.
I don't think we need to 'fix' any drivers already upstream as
presenting these as differential is not an ABI error as far as I
am concerned. It's just less than ideal choices given our views
now! (as a result of these discussions on what pseudo differential
means in practice)
Jonathan
next prev parent reply other threads:[~2024-02-24 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 20:28 [PATCH v4 0/2] iio: adc: add new ad7380 driver David Lechner
2024-01-10 20:28 ` [PATCH v4 1/2] dt-bindings: iio: adc: Add binding for AD7380 ADCs David Lechner
2024-01-11 16:38 ` Conor Dooley
2024-01-10 20:28 ` [PATCH v4 2/2] iio: adc: ad7380: new driver " David Lechner
2024-02-16 20:34 ` David Lechner
2024-02-17 16:20 ` Jonathan Cameron
2024-02-18 21:57 ` David Lechner
2024-02-19 19:47 ` David Lechner
2024-02-24 11:06 ` Jonathan Cameron [this message]
2024-01-13 16:14 ` [PATCH v4 0/2] iio: adc: add new ad7380 driver 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=20240224110640.03f3b857@jic23-huawei \
--to=jic23@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jstephan@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.com \
--cc=robh+dt@kernel.org \
--cc=stefan.popa@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