From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: <robh@kernel.org>, <conor+dt@kernel.org>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 0/6] iio: adc: ad4080: add support for AD4081 and AD4084
Date: Sun, 12 Oct 2025 19:11:41 +0100 [thread overview]
Message-ID: <20251012191141.427110d8@jic23-huawei> (raw)
In-Reply-To: <20251007111525.25711-1-antoniu.miclaus@analog.com>
On Tue, 7 Oct 2025 11:15:19 +0000
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
> Add support for AD4081 (16-bit, 4 LVDS CNV clock max) and AD4084
> (18-bit, 6 LVDS CNV clock max) ADC variants to the existing AD4080
> driver.
>
> Changes:
> - Update device tree bindings to include AD4081 and AD4084
> - Add chip_info entries for AD4081 and AD4084 with appropriate
> resolution and LVDS CNV clock count
> - Modify channel definitions to accommodate different resolutions
> - Ensure backward compatibility with existing AD4080 functionality
>
> Antoniu Miclaus (6):
> iio: adc: ad4080: fix chip identification
> iio: adc: ad4080: prepare driver for multi-part support
> dt-bindings: iio: adc: adi,ad4080: add support for AD4084
> iio: adc: ad4080: add support for AD4084
> dt-bindings: iio: adc: adi,ad4080: add support for AD4081
> iio: adc: ad4080: add support for AD4081
>
> .../bindings/iio/adc/adi,ad4080.yaml | 2 +
> drivers/iio/adc/ad4080.c | 80 ++++++++++++++-----
> 2 files changed, 60 insertions(+), 22 deletions(-)
>
Series applied to the testing branch of iio.git. I marked patch 1
for stable. See that patch discussion for why I did things this way.
thanks
Jonathan
prev parent reply other threads:[~2025-10-12 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 11:15 [PATCH v3 0/6] iio: adc: ad4080: add support for AD4081 and AD4084 Antoniu Miclaus
2025-10-07 11:15 ` [PATCH v3 1/6] iio: adc: ad4080: fix chip identification Antoniu Miclaus
2025-10-07 14:41 ` Nuno Sá
2025-10-12 18:10 ` Jonathan Cameron
2025-10-07 11:15 ` [PATCH v3 2/6] iio: adc: ad4080: prepare driver for multi-part support Antoniu Miclaus
2025-10-07 11:15 ` [PATCH v3 3/6] dt-bindings: iio: adc: adi,ad4080: add support for AD4084 Antoniu Miclaus
2025-10-07 11:15 ` [PATCH v3 4/6] iio: adc: ad4080: " Antoniu Miclaus
2025-10-07 11:15 ` [PATCH v3 5/6] dt-bindings: iio: adc: adi,ad4080: add support for AD4081 Antoniu Miclaus
2025-10-07 11:15 ` [PATCH v3 6/6] iio: adc: ad4080: " Antoniu Miclaus
2025-10-12 18:11 ` 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=20251012191141.427110d8@jic23-huawei \
--to=jic23@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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