From: Rodrigo Alencar via B4 Relay <devnull+rodrigo.alencar.analog.com@kernel.org>
To: Michael Auchter <michael.auchter@ni.com>,
linux@analog.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
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>,
Rodrigo Alencar <rodrigo.alencar@analog.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH 1/4] dt-bindings: iio: dac: ad5696: extend device support
Date: Sun, 19 Jul 2026 10:51:57 +0100 [thread overview]
Message-ID: <20260719-ad5686-extend-dev-support-v1-1-841ec75cf5d8@analog.com> (raw)
In-Reply-To: <20260719-ad5686-extend-dev-support-v1-0-841ec75cf5d8@analog.com>
From: Rodrigo Alencar <rodrigo.alencar@analog.com>
Support for AD5316R, AD5673R, AD5675, AD5677R and AD5697R missing from the
device-tree bindings documentation. These devices have different bit
resolutions or different number of channels so no fallback compatibles
are used.
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Signed-off-by: Rodrigo Alencar <rodrigo.alencar@analog.com>
---
Documentation/devicetree/bindings/iio/dac/adi,ad5696.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/iio/dac/adi,ad5696.yaml b/Documentation/devicetree/bindings/iio/dac/adi,ad5696.yaml
index e10f8596f9d3..835fa21c474e 100644
--- a/Documentation/devicetree/bindings/iio/dac/adi,ad5696.yaml
+++ b/Documentation/devicetree/bindings/iio/dac/adi,ad5696.yaml
@@ -16,10 +16,14 @@ properties:
compatible:
enum:
- adi,ad5311r
+ - adi,ad5316r
- adi,ad5337r
- adi,ad5338r
- adi,ad5671r
+ - adi,ad5673r
+ - adi,ad5675
- adi,ad5675r
+ - adi,ad5677r
- adi,ad5691r
- adi,ad5692r
- adi,ad5693
@@ -29,6 +33,7 @@ properties:
- adi,ad5695r
- adi,ad5696
- adi,ad5696r
+ - adi,ad5697r
reg:
maxItems: 1
@@ -84,6 +89,7 @@ allOf:
compatible:
contains:
enum:
+ - adi,ad5675
- adi,ad5693
- adi,ad5694
- adi,ad5696
--
2.43.0
next prev parent reply other threads:[~2026-07-19 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 9:51 [PATCH 0/4] iio: dac: ad5686: extend device support Rodrigo Alencar via B4 Relay
2026-07-19 9:51 ` Rodrigo Alencar via B4 Relay [this message]
2026-07-19 21:18 ` [PATCH 1/4] dt-bindings: iio: dac: ad5696: " Jonathan Cameron
2026-07-19 9:51 ` [PATCH 2/4] dt-bindings: iio: dac: ad5686: " Rodrigo Alencar via B4 Relay
2026-07-19 9:51 ` [PATCH 3/4] iio: dac: ad5686: extend device support with new parts Rodrigo Alencar via B4 Relay
2026-07-19 21:43 ` Jonathan Cameron
2026-07-20 11:16 ` Rodrigo Alencar
2026-07-19 9:52 ` [PATCH 4/4] iio: dac: ad5686: update device list and file header comments Rodrigo Alencar via B4 Relay
2026-07-19 21:30 ` Jonathan Cameron
2026-07-20 11:27 ` Rodrigo Alencar
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=20260719-ad5686-extend-dev-support-v1-1-841ec75cf5d8@analog.com \
--to=devnull+rodrigo.alencar.analog.com@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=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--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