From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Janani Sunil" <janani.sunil@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Olivier Moysan" <olivier.moysan@foss.st.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Linus Walleij" <linusw@kernel.org>,
"Bartosz Golaszewski" <brgl@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Michael Walle" <mwalle@kernel.org>,
linux@analog.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
jananisunil.dev@gmail.com,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Subject: Re: [PATCH v4 02/14] dt-bindings: iio: adc: Add AD7768
Date: Sun, 23 Aug 2026 02:45:18 +0100 [thread overview]
Message-ID: <20260823024518.2c75733c@jic23-huawei> (raw)
In-Reply-To: <718f6ead-d1c0-4dc6-82e4-cac49cc73bd6@baylibre.com>
> > + ref2p-supply:
> > + description:
> > + Positive reference input supply for REF2+. The voltage range is from
> > + (AVSS + 1 V) to AVDD1. Together, REF2+ and REF2- must provide a
> > + differential reference voltage from 1 V to |AVDD1 - AVSS|. This
> > + reference is used by channels 4 to 7 on the AD7768 and channels 2 and 3
> > + on the AD7768-4.
> > +
> > + ref2n-supply:
> > + description:
> > + Negative reference input supply for REF2-. The voltage range is from
> > + AVSS to (AVDD1 - 1 V).
>
> For all of the supplies, I don't think we need to repeat so much of what the
> datasheet says. It is getting quite noisy and makes it hard to see the parts
> of the description that are actually relevant to how the devicetree is to be
> interpreted. (includes VCM as well)
Agreed. Keep anything about how being present / not present may matter.
Pretty much anything else isn't really that interesting.
Sometimes
xxx-supply: true
is enough.
>
> > +
> > + reset-gpios:
> > + maxItems: 1
> > + description: GPIO connected to the active-low RESET pin
> > +
> > + start-gpios:
> > + maxItems: 1
> > + description:
> > + GPIO connected to the START pin. An active-low pulse on this pin
> > + synchronizes the device to other AD7768 devices. When not used, this
> > + pin must be tied to a logic high level through a pull-up resistor.
> > + When used, SYNC_OUT must be wired back to SYNC_IN on all devices in
> > + the synchronization chain.
> > +
> > + sync-in-gpios:
> > + maxItems: 1
> > + description:
> > + GPIO connected to the SYNC_IN pin. Receives the synchronization pulse
> > + generated on SYNC_OUT in response to a START pulse. Must be synchronous
> > + to the MCLK clock domain. In multi-device or daisy-chained systems,
> > + two successive synchronization pulses must be applied to guarantee all
> > + ADCs are synchronized.
> > +
> > + sync-out-gpios:
>
> Unusual to have an output pin connected to a GPIO. Usually this would be an
> interrupt or trigger-sources.
>
> > + maxItems: 1
> > + description:
> > + GPIO connected to the SYNC_OUT pin. Outputs a synchronization pulse
> > + synchronous to MCLK in response to a START pulse or SPI_SYNC command.
> > + In single-device configurations this pin must be wired back to SYNC_IN.
> > + In multi-device configurations it can be routed to the SYNC_IN pins of
> > + all devices in the chain.
>
> Although this description makes it sounds like the SYNC_OUT pin is only ever
> wired to SYNC_IN. So wouldn't be described here at all.
We don't have a particularly good way to say "this hardware controlled pin
is wired from this ADC to this second ADC" As you note though GPIO doesn't
work for that.
next prev parent reply other threads:[~2026-08-23 1:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 14:06 [PATCH v4 00/14] iio: adc: Add AD7768/AD7768-4 ADC driver support Janani Sunil
2026-08-21 14:06 ` [PATCH v4 01/14] iio: adc: adi-axi-adc: Initialize state mutex Janani Sunil
2026-08-23 18:52 ` Jonathan Cameron
2026-08-23 19:05 ` Jonathan Cameron
2026-08-21 14:06 ` [PATCH v4 02/14] dt-bindings: iio: adc: Add AD7768 Janani Sunil
2026-08-21 15:57 ` David Lechner
2026-08-23 1:45 ` Jonathan Cameron [this message]
2026-08-21 14:06 ` [PATCH v4 03/14] iio: backend: Add support for CRC Janani Sunil
2026-08-21 16:02 ` David Lechner
2026-08-21 14:06 ` [PATCH v4 04/14] iio: adc: adi-axi-adc: " Janani Sunil
2026-08-21 16:03 ` David Lechner
2026-08-21 14:06 ` [PATCH v4 05/14] iio: adc: Add AD7768 and AD7768-4 core support Janani Sunil
2026-08-22 17:30 ` David Lechner
2026-08-23 8:35 ` Andy Shevchenko
2026-08-23 19:16 ` Jonathan Cameron
2026-08-21 14:06 ` [PATCH v4 06/14] iio: adc: ad7768: Add configurable sampling modes Janani Sunil
2026-08-23 19:25 ` Jonathan Cameron
2026-08-21 14:07 ` [PATCH v4 07/14] iio: adc: ad7768: Add calibration controls Janani Sunil
2026-08-21 14:07 ` [PATCH v4 08/14] iio: adc: ad7768: Add per-channel conversion delay Janani Sunil
2026-08-21 14:07 ` [PATCH v4 09/14] iio: adc: ad7768: Add VCM regulator support Janani Sunil
2026-08-21 14:07 ` [PATCH v4 10/14] iio: adc: ad7768: Register GPIO auxiliary device Janani Sunil
2026-08-21 14:07 ` [PATCH v4 11/14] gpio: regmap: Use regmap_test_bits() for single bit reads Janani Sunil
2026-08-21 14:07 ` [PATCH v4 12/14] gpio: regmap: Add optional runtime PM support Janani Sunil
2026-08-21 14:07 ` [PATCH v4 13/14] gpio: ad7768: Add AD7768 GPIO auxiliary driver Janani Sunil
2026-08-23 19:39 ` Jonathan Cameron
2026-08-21 14:07 ` [PATCH v4 14/14] Documentation: iio: Add AD7768 Documentation Janani Sunil
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=20260823024518.2c75733c@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=janani.sunil@analog.com \
--cc=jananisunil.dev@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=mwalle@kernel.org \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=u.kleine-koenig@baylibre.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