From: Jonathan Santos <Jonathan.Santos@analog.com>
To: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Cc: Jonathan Santos <Jonathan.Santos@analog.com>, <lars@metafoo.de>,
<Michael.Hennerich@analog.com>, <jic23@kernel.org>,
<dlechner@baylibre.com>, <nuno.sa@analog.com>, <andy@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Subject: [PATCH v3 0/5] Add support for AD4129-4/8, AD4130-4, and AD4131-4/8
Date: Wed, 1 Apr 2026 08:57:47 -0300 [thread overview]
Message-ID: <cover.1774996100.git.Jonathan.Santos@analog.com> (raw)
This patch series extends the AD4130 driver to support additional variants
in the AD4130 family: AD4129-4/8, AD4130-4, and AD4131-4/8.
The series introduces a chip info architecture to handle device-specific
differences. The AD4129 series provides 16-bit resolution with FIFO
support, while the AD4131 series offers 24-bit resolution but without
FIFO capability, requiring triggered buffer implementation. The 4-channel
variants feature reduced analog inputs, fewer GPIOs, and sparse pin
mappings.
---
Changes in v3:
* Since we have either FIFO or triggered buffer configured, create
a union struct with the FIFO buffers and the triggered buffer
scan channel declaration to save memory.
* Some lines in the ad4130_trigger_handler() were ending in comma instead
of a semicolon. Replaced the commas with semicolons for those cases.
* Inverted logic for wait_for_completion_timeout() check in
ad4130_trigger_handler(). It was warning on success.
* Addressed other minor suggestions. See individual patches.
* Link to v2: https://lore.kernel.org/linux-iio/cover.1773311639.git.Jonathan.Santos@analog.com/T/#t/
Changes in v2:
* Add patch documenting the interrupts property.
* Add patch for the SPI id table, moving its content from the chip info
patch.
* Addressed other minor suggestions. See individual patches.
* Link to v1: https://lore.kernel.org/linux-iio/cover.1772078999.git.Jonathan.Santos@analog.com/T/#t/
Jonathan Santos (5):
dt-bindings: iio: adc: ad4130: Document interrupts property
dt-bindings: iio: adc: ad4130: Add new supported parts
iio: adc: ad4130: Add SPI device ID table
iio: adc: ad4130: introduce chip info for future multidevice support
iio: adc: ad4130: add new supported parts
.../bindings/iio/adc/adi,ad4130.yaml | 19 +-
drivers/iio/adc/ad4130.c | 493 +++++++++++++++---
2 files changed, 427 insertions(+), 85 deletions(-)
base-commit: d2a4ec19d2a2e54c23b5180e939994d3da4a6b91
--
2.34.1
next reply other threads:[~2026-04-01 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 11:57 Jonathan Santos [this message]
2026-04-01 11:58 ` [PATCH v3 1/5] dt-bindings: iio: adc: ad4130: Document interrupts property Jonathan Santos
2026-04-01 11:58 ` [PATCH v3 2/5] dt-bindings: iio: adc: ad4130: Add new supported parts Jonathan Santos
2026-04-01 11:58 ` [PATCH v3 3/5] iio: adc: ad4130: Add SPI device ID table Jonathan Santos
2026-04-01 11:58 ` [PATCH v3 4/5] iio: adc: ad4130: introduce chip info for future multidevice support Jonathan Santos
2026-04-01 11:58 ` [PATCH v3 5/5] iio: adc: ad4130: add new supported parts Jonathan Santos
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=cover.1774996100.git.Jonathan.Santos@analog.com \
--to=jonathan.santos@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--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