From: Jonathan Cameron <jic23@kernel.org>
To: "David Marinović" <david.marinovic@pupin.rs>
Cc: andriy.shevchenko@intel.com, dlechner@baylibre.com,
nuno.sa@analog.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, michael.hennerich@analog.com,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] iio: dac: ltc2632: add support for LTC2654 DAC family
Date: Sat, 21 Mar 2026 15:30:40 +0000 [thread overview]
Message-ID: <20260321153040.2494aa9c@jic23-huawei> (raw)
In-Reply-To: <20260320150957.105571-1-david.marinovic@pupin.rs>
On Fri, 20 Mar 2026 16:09:45 +0100
David Marinović <david.marinovic@pupin.rs> wrote:
> From: David Marinovic <david.marinovic@pupin.rs>
>
> Greetings!
>
> This is v3 of the LTC2654 DAC support patch series.
>
> The LTC2654 is a quad-channel, 16-/12-bit DAC with internal
> reference voltage and SPI interface, sharing the same 24-bit
> SPI protocol as the LTC2632/2634/2636 family.
>
> The LTC2654L-16 variant was tested on a Phytec phyCORE-STM32MP1
> board with the DAC connected via SPI1. The driver probes successfully
> and all 4 channels are accessible via IIO sysfs.
>
Process comment. Don't send new versions in reply to a previous one.
It leads to them being well back in people's email history (depending
on the client and how it gets sorted) and leads to hard to read threads.
Convention is new version, new email thread.
Thanks,
Jonathan
> Changes in v3:
> - Patch 1 unchanged
> - DT bindings use fallback compatibles for LTC2654-L12 and
> LTC2654-H12, which are register-compatible with LTC2634-L12
> and LTC2634-H12
> - LTC2654-L16 and LTC2654-H16 keep separate compatible strings
> as no existing compatible supports 16-bit resolution
> - 12-bit variants reuse existing LTC2634 chip_info structures,
> so only two new chip_info structures are added for 16-bit variants
>
>
> David Marinovic (3):
> iio: dac: ltc2632: drop enum and use individual chip_info objects
> dt-bindings: iio: dac: ltc2632: add LTC2654 compatible strings
> iio: dac: ltc2632: add support for LTC2654 DAC family
>
> .../bindings/iio/dac/lltc,ltc2632.yaml | 12 +-
> drivers/iio/dac/ltc2632.c | 367 +++++++++---------
> 2 files changed, 188 insertions(+), 191 deletions(-)
>
next prev parent reply other threads:[~2026-03-21 15:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d4fb8998d9634c3e5a8ed17b80dae07@pupin.rs>
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
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 ` Jonathan Cameron [this message]
2026-03-21 15:41 ` [PATCH v3 0/3] " 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=20260321153040.2494aa9c@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=conor+dt@kernel.org \
--cc=david.marinovic@pupin.rs \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox