From: Krzysztof Kozlowski <krzk@kernel.org>
To: "David Marinović" <david.marinovic@pupin.rs>
Cc: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
michael.hennerich@analog.com, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: iio: dac: ltc2632: add LTC2654 compatible strings
Date: Wed, 11 Mar 2026 14:03:55 +0100 [thread overview]
Message-ID: <20260311-warping-ruby-marmoset-3d494a@quoll> (raw)
In-Reply-To: <4915e1023c72d2681b0c4ae028ec609e@pupin.rs>
On Tue, Mar 10, 2026 at 04:32:05PM +0100, David Marinović wrote:
> Add DT compatible strings for the LTC2654 DAC family variants
> supported by the ltc2632 driver.
Describe hardware, not driver.
>
> Signed-off-by: David Marinovic <david.marinovic@pupin.rs>
> ---
> .../devicetree/bindings/iio/dac/lltc,ltc2632.yaml | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/iio/dac/lltc,ltc2632.yaml
> b/Documentation/devicetree/bindings/iio/dac/lltc,ltc2632.yaml
> index 733edc7d6d17..7ec663beec1a 100644
> --- a/Documentation/devicetree/bindings/iio/dac/lltc,ltc2632.yaml
> +++ b/Documentation/devicetree/bindings/iio/dac/lltc,ltc2632.yaml
> @@ -4,14 +4,15 @@
> $id: http://devicetree.org/schemas/iio/dac/lltc,ltc2632.yaml#
> $schema: http://devicetree.org/meta-schemas/core.yaml#
>
> -title: Linear Technology LTC263x 12-/10-/8-Bit Rail-to-Rail DAC
> +title: Linear Technology LTC263x 12-/10-/8-Bit, LTC2654 16-/12-Bit,
> Rail-to-Rail DAC
There are multiple patch errors here. This is unmergeable.
>
> maintainers:
> - Michael Hennerich <michael.hennerich@analog.com>
>
> description: |
> - Bindings for the Linear Technology LTC2632/2634/2636 DAC
> + Bindings for the Linear Technology LTC2632/2634/2636/2654 DAC
> Datasheet can be found here: https://www.analog.com/media/en/technical-documentation/data-sheets/LTC263[246].pdf
> + Datasheet can be found here:
> https://www.analog.com/media/en/technical-documentation/data-sheets/2654f.pdf
>
> properties:
> compatible:
> @@ -34,6 +35,10 @@ properties:
> - lltc,ltc2636-h12
> - lltc,ltc2636-h10
> - lltc,ltc2636-h8
> + - lltc,ltc2654-l16
> + - lltc,ltc2654-l12
> + - lltc,ltc2654-h16
> + - lltc,ltc2654-h12
Several look compatible to me, so express it with fallback and drop
unneeded entries in the driver.
>
> reg:
> maxItems: 1
> --
> 2.50.1
>
>
>
>
> -------- Original Message --------
> Subject: [PATCH 0/2] iio: dac: ltc2632: add support for LTC2654 DAC family
> Date: 10.03.2026 16:27
> From: David Marinović <david.marinovic@pupin.rs>
> To: jic23@kernel.org
>
> This patch series adds support for the Linear Technology LTC2654
> quad DAC family to the existing ltc2632 driver.
>
> The LTC2654 shares the same 24-bit SPI protocol as the existing
> LTC2632/2634/2636 devices, requiring minimal additions to the
> driver.
>
> The LTC2654L-16 variant has been tested on a Phytec phyCORE-STM32MP1
> board with the DAC connected via SPI1. The driver probes successfully
> and all 4 channels are accessible via the IIO sysfs interface.
>
> Patch 1 adds the driver support.
> Patch 2 updates the DT bindings documentation.
>
> David Marinovic (2):
> iio: dac: ltc2632: add support for LTC2654 DAC family
> dt-bindings: iio: dac: ltc2632: add LTC2654 compatible strings
>
> Signed-off-by: David Marinovic <david.marinovic@pupin.rs>
What is this?
next prev parent reply other threads:[~2026-03-11 13:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 15:27 [PATCH 0/2] iio: dac: ltc2632: add support for LTC2654 DAC family David Marinović
2026-03-10 15:29 ` [PATCH 1/2] " David Marinović
2026-03-11 12:18 ` Andy Shevchenko
2026-03-10 15:32 ` [PATCH 2/2] dt-bindings: iio: dac: ltc2632: add LTC2654 compatible strings David Marinović
2026-03-11 13:03 ` Krzysztof Kozlowski [this message]
2026-03-11 13:04 ` Krzysztof Kozlowski
2026-03-18 13:57 ` [PATCH v2 0/3] iio: dac: ltc2632: add support for LTC2654 DAC family David Marinović
2026-03-18 13:57 ` [PATCH 1/3] iio: dac: ltc2632: drop enum and use individual chip_info objects David Marinović
2026-03-18 14:57 ` Andy Shevchenko
2026-03-18 13:57 ` [PATCH 2/3] dt-bindings: iio: dac: ltc2632: add LTC2654 compatible strings David Marinović
2026-03-18 17:38 ` Conor Dooley
2026-03-18 13:57 ` [PATCH 3/3] iio: dac: ltc2632: add support for LTC2654 DAC family David Marinović
2026-03-20 15:09 ` [PATCH v3 0/3] " David Marinović
2026-03-20 15:09 ` [PATCH v3 1/3] iio: dac: ltc2632: drop enum and use individual chip_info objects David Marinović
2026-03-20 15:09 ` [PATCH v3 2/3] dt-bindings: iio: dac: ltc2632: add LTC2654 compatible strings David Marinović
2026-03-20 17:20 ` Conor Dooley
2026-03-21 15:39 ` Jonathan Cameron
2026-03-20 15:09 ` [PATCH v3 3/3] iio: dac: ltc2632: add support for LTC2654 DAC family David Marinović
2026-03-21 15:38 ` Jonathan Cameron
2026-03-21 15:30 ` [PATCH v3 0/3] " Jonathan Cameron
2026-03-21 15:41 ` Jonathan Cameron
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=20260311-warping-ruby-marmoset-3d494a@quoll \
--to=krzk@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david.marinovic@pupin.rs \
--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=michael.hennerich@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.