From: Jonathan Cameron <jic23@kernel.org>
To: Hungyu Lin <dennylin0707@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] dt-bindings: iio: adc: add AD7816/AD7817/AD7818 binding
Date: Mon, 11 May 2026 17:52:00 +0100 [thread overview]
Message-ID: <20260511175200.40f809d1@jic23-huawei> (raw)
In-Reply-To: <20260509022718.82957-2-dennylin0707@gmail.com>
On Sat, 9 May 2026 02:27:18 +0000
Hungyu Lin <dennylin0707@gmail.com> wrote:
> Add Device Tree binding documentation for the Analog Devices
> AD7816, AD7817 and AD7818 SPI ADC devices.
>
> The AD7816 provides temperature monitoring only, while the
> AD7817 and AD7818 provide analog input channels with an
> on-chip temperature sensor.
>
> The devices use control GPIOs for RD/WR and CONVST. BUSY is required for
> AD7816 and AD7817 variants.
>
> Signed-off-by: Hungyu Lin <dennylin0707@gmail.com>
Subject to the discussion you had with David about us only normally
adding a dt-binding as part of the final series that moves a driver
out of staging. This looks fine to me.
Note I've been hopefully checking analog.com every 6 months or so for
the ad7817 to go obsolete - (no luck yet!) - hence I haven't deleted
the driver despite no one getting it into a reasonable state for
many years. If you are interested in doing that work then great!
Maybe the Analog devices folk can help you out with testing etc.
Jonathan
next prev parent reply other threads:[~2026-05-11 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 2:27 [PATCH v3 0/1] dt-bindings: iio: adc: add AD7816/AD7817/AD7818 binding Hungyu Lin
2026-05-09 2:27 ` [PATCH v3 1/1] " Hungyu Lin
2026-05-09 22:13 ` David Lechner
2026-05-10 1:37 ` Denny Lin
2026-05-11 14:51 ` David Lechner
2026-05-11 16:23 ` Denny Lin
2026-05-11 16:31 ` David Lechner
2026-05-12 11:22 ` Jonathan Cameron
2026-05-11 16:52 ` Jonathan Cameron [this message]
2026-05-09 22:21 ` [PATCH v3 0/1] " David Lechner
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=20260511175200.40f809d1@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dennylin0707@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
/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