From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, linux@analog.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: adc: ad4080: add support for AD4885
Date: Mon, 21 Sep 2026 03:13:21 +0100 [thread overview]
Message-ID: <20260921031321.45893860@jic23-hlaptop> (raw)
In-Reply-To: <20260913232155.5b8d226f@jic23-hlaptop>
On Sun, 13 Sep 2026 23:21:55 +0100
Jonathan Cameron <jic23@kernel.org> wrote:
> On Mon, 7 Sep 2026 13:19:44 +0300
> Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
>
> > Add support for the AD4885, a dual-channel, 16-bit, 10 MSPS SAR ADC.
> >
> > The AD4885 is the dual-channel variant of the AD4085, sharing the same
> > register map and SPI interface as the rest of the AD4080 family. Like
> > the AD4884, it uses two independent ADC channels, each with its own SPI
> > configuration interface, but it runs at a lower maximum throughput and
> > therefore uses the same maximum LVDS conversion clock count as the
> > AD4085.
> >
> > Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> LGTM. I'll leave it on list a few days though as we still
> need a DT ack.
I'm not entirely sure why but it jumped directly to handled
elsewhere in the dt-binding patchwork.
Works for me ;)
Applied,
Thanks,
Jonathan
>
> Jonathan
>
prev parent reply other threads:[~2026-09-21 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 10:19 [PATCH 0/2] iio: adc: ad4080: add support for AD4885 Antoniu Miclaus
2026-09-07 10:19 ` [PATCH 1/2] dt-bindings: iio: adc: ad4080: add AD4885 support Antoniu Miclaus
2026-09-07 10:28 ` sashiko-bot
2026-09-07 10:19 ` [PATCH 2/2] iio: adc: ad4080: add support for AD4885 Antoniu Miclaus
2026-09-13 22:21 ` Jonathan Cameron
2026-09-21 2:13 ` 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=20260921031321.45893860@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--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