From: Jonathan Cameron <jic23@kernel.org>
To: Rodrigo Alencar via B4 Relay
<devnull+rodrigo.alencar.analog.com@kernel.org>
Cc: rodrigo.alencar@analog.com,
Michael Auchter <michael.auchter@ni.com>,
linux@analog.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Hennerich <Michael.Hennerich@analog.com>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v2 0/6] iio: dac: ad5686: extend device support
Date: Mon, 27 Jul 2026 02:13:35 +0100 [thread overview]
Message-ID: <20260727021335.09c3287a@jic23-huawei> (raw)
In-Reply-To: <20260724-ad5686-extend-dev-support-v2-0-cfc2b30ce988@analog.com>
On Fri, 24 Jul 2026 13:03:10 +0100
Rodrigo Alencar via B4 Relay <devnull+rodrigo.alencar.analog.com@kernel.org> wrote:
> This is the third series of three on updating the AD5686 driver.
>
> Initially, a big patch series was sent:
> https://lore.kernel.org/r/20260422-ad5313r-iio-support-v1-0-ed7dca001d1b@analog.com
>
> Then, the first patch series added fixes and cleanups:
> https://lore.kernel.org/all/20260524-ad5686-fixes-v7-0-b6bf395d08bd@analog.com/
>
> The second series introduced new features:
> https://lore.kernel.org/all/20260716-ad5686-new-features-v8-0-ebb0051af5e5@analog.com/
>
> This series adds support for:
> - SPI: AD5313R, AD5317R, AD5674, AD5679, AD5687, AD5687R, AD5689, AD5689R;
> - I2C: AD5316R, AD5675, AD5697R
>
> Signed-off-by: Rodrigo Alencar <rodrigo.alencar@analog.com>
> ---
Nice set. Applied to the testing branch of iio.git
Thanks,
Jonathan
> Changes in v2:
> - Missing devices in I2C drivers as cleanup patches.
> - Refactor of Kconfig device list as a cleanup patch.
> - Link to v1: https://lore.kernel.org/r/20260719-ad5686-extend-dev-support-v1-0-841ec75cf5d8@analog.com
>
> ---
> Rodrigo Alencar (6):
> dt-bindings: iio: dac: ad5696: add AD5673R/AD5677R support
> iio: dac: ad5696: add AD5673R/AD5677R entries to of_match table
> iio: dac: ad5686: refactor device list and file header comments
> dt-bindings: iio: dac: ad5696: extend device support
> dt-bindings: iio: dac: ad5686: extend device support
> iio: dac: ad5686: extend device support with new parts
>
> .../devicetree/bindings/iio/dac/adi,ad5686.yaml | 14 +++++-
> .../devicetree/bindings/iio/dac/adi,ad5696.yaml | 6 +++
> drivers/iio/dac/Kconfig | 31 +++++++++---
> drivers/iio/dac/ad5686-spi.c | 21 ++++++--
> drivers/iio/dac/ad5686.c | 57 +++++++++++++++++++++-
> drivers/iio/dac/ad5686.h | 7 +++
> drivers/iio/dac/ad5696-i2c.c | 12 +++--
> 7 files changed, 132 insertions(+), 16 deletions(-)
> ---
> base-commit: 1258e8ca13866b1a60895abf0ab8a4dd77bf4bfd
> change-id: 20260719-ad5686-extend-dev-support-e0ddd119f19c
>
> Best regards,
prev parent reply other threads:[~2026-07-27 1:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 12:03 [PATCH v2 0/6] iio: dac: ad5686: extend device support Rodrigo Alencar via B4 Relay
2026-07-24 12:03 ` [PATCH v2 1/6] dt-bindings: iio: dac: ad5696: add AD5673R/AD5677R support Rodrigo Alencar via B4 Relay
2026-07-24 16:53 ` Conor Dooley
2026-07-24 12:03 ` [PATCH v2 2/6] iio: dac: ad5696: add AD5673R/AD5677R entries to of_match table Rodrigo Alencar via B4 Relay
2026-07-24 12:03 ` [PATCH v2 3/6] iio: dac: ad5686: refactor device list and file header comments Rodrigo Alencar via B4 Relay
2026-07-24 12:03 ` [PATCH v2 4/6] dt-bindings: iio: dac: ad5696: extend device support Rodrigo Alencar via B4 Relay
2026-07-24 16:53 ` Conor Dooley
2026-07-24 12:03 ` [PATCH v2 5/6] dt-bindings: iio: dac: ad5686: " Rodrigo Alencar via B4 Relay
2026-07-24 12:03 ` [PATCH v2 6/6] iio: dac: ad5686: extend device support with new parts Rodrigo Alencar via B4 Relay
2026-07-27 1: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=20260727021335.09c3287a@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=devnull+rodrigo.alencar.analog.com@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=michael.auchter@ni.com \
--cc=robh@kernel.org \
--cc=rodrigo.alencar@analog.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