From: Andy Shevchenko <andriy.shevchenko@intel.com>
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
Subject: Re: [PATCH 1/2] iio: dac: ltc2632: add support for LTC2654 DAC family
Date: Wed, 11 Mar 2026 14:18:32 +0200 [thread overview]
Message-ID: <abFdmNIZYQFUIGIE@ashevche-desk.local> (raw)
In-Reply-To: <82ba84f98db9c32d3fc4efd7ef6697a2@pupin.rs>
On Tue, Mar 10, 2026 at 04:29:48PM +0100, David Marinović wrote:
>
> Add support for the Linear Technology LTC2654 quad DAC family.
> The LTC2654 is a 4-channel, 16-/12-bit DAC with SPI interface,
> sharing the same 24-bit SPI protocol as the existing LTC2632/
> LTC2634/LTC2636 devices supported by this driver.
>
> Add support for the following variants:
> - LTC2654L-16: 16-bit, 2.5V internal reference
> - LTC2654L-12: 12-bit, 2.5V internal reference
> - LTC2654H-16: 16-bit, 4.096V internal reference
> - LTC2654H-12: 12-bit, 4.096V internal reference
...
> enum ltc2632_supported_device_ids {
> ID_LTC2636H12,
> ID_LTC2636H10,
> ID_LTC2636H8,
> + ID_LTC2654L16,
> + ID_LTC2654L12,
> + ID_LTC2654H16,
> + ID_LTC2654H12
You see how nicely the new IDs landed here, but after you it will require an
unneeded churn.
> };
...
> static const struct spi_device_id ltc2632_id[] = {
> { "ltc2636-h12",
> (kernel_ulong_t)<c2632_chip_info_tbl[ID_LTC2636H12] },
> { "ltc2636-h10",
> (kernel_ulong_t)<c2632_chip_info_tbl[ID_LTC2636H10] },
> { "ltc2636-h8", (kernel_ulong_t)<c2632_chip_info_tbl[ID_LTC2636H8]
> },
> + { "ltc2654-l16",
> (kernel_ulong_t)<c2632_chip_info_tbl[ID_LTC2654L16] },
> + { "ltc2654-l12",
> (kernel_ulong_t)<c2632_chip_info_tbl[ID_LTC2654L12] },
> + { "ltc2654-h16",
> (kernel_ulong_t)<c2632_chip_info_tbl[ID_LTC2654H16] },
> + { "ltc2654-h12",
> (kernel_ulong_t)<c2632_chip_info_tbl[ID_LTC2654H12] },
> { }
Can we have a refactor patch to drop that enum and use separate chip_info
static objects?
> };
...
> static const struct of_device_id ltc2632_of_match[] = {
> }, {
> .compatible = "lltc,ltc2636-h8",
> .data = <c2632_chip_info_tbl[ID_LTC2636H8]
> + }, {
> + .compatible = "lltc,ltc2654-l16",
> + .data = <c2632_chip_info_tbl[ID_LTC2654L16]
> + }, {
> + .compatible = "lltc,ltc2654-l12",
> + .data = <c2632_chip_info_tbl[ID_LTC2654L12]
> + }, {
> + .compatible = "lltc,ltc2654-h16",
> + .data = <c2632_chip_info_tbl[ID_LTC2654H16]
> + }, {
> + .compatible = "lltc,ltc2654-h12",
> + .data = <c2632_chip_info_tbl[ID_LTC2654H12]
> },
Ditto.
> { }
> };
...
> 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.
Huh?!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-11 12:18 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 [this message]
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 ` [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=abFdmNIZYQFUIGIE@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=david.marinovic@pupin.rs \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@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 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.