From: Jonathan Cameron <jic23@kernel.org>
To: Kim Seer Paller <kimseer.paller@analog.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@analog.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/4] iio: dac: ad3530r: Refactor setup to table-driven register bank approach
Date: Sun, 21 Jun 2026 17:49:30 +0100 [thread overview]
Message-ID: <20260621174930.35c2091f@jic23-huawei> (raw)
In-Reply-To: <20260615-iio-ad3532r-support-v2-1-84a0af8b83fa@analog.com>
On Mon, 15 Jun 2026 14:20:15 +0800
Kim Seer Paller <kimseer.paller@analog.com> wrote:
> Replace direct register calls in ad3530r_setup() with per-chip register
> address arrays and bank helpers (ad3530r_set_reg_bank_bits,
> ad3530r_write_reg_banks). Convert sw_ldac_trig_reg from a static
> register address to a function pointer for per-bank LDAC trigger
> register selection. Switch spi_device_id to named initializers.
>
> Signed-off-by: Kim Seer Paller <kimseer.paller@analog.com>
>
> static const struct spi_device_id ad3530r_id[] = {
> - { "ad3530", (kernel_ulong_t)&ad3530_chip },
> - { "ad3530r", (kernel_ulong_t)&ad3530r_chip },
> - { "ad3531", (kernel_ulong_t)&ad3531_chip },
> - { "ad3531r", (kernel_ulong_t)&ad3531r_chip },
> + { .name = "ad3530", .driver_data = (kernel_ulong_t)&ad3530_chip },
> + { .name = "ad3530r", .driver_data = (kernel_ulong_t)&ad3530r_chip },
> + { .name = "ad3531", .driver_data = (kernel_ulong_t)&ad3531_chip },
> + { .name = "ad3531r", .driver_data = (kernel_ulong_t)&ad3531r_chip },
There is a high chance this will cross with Uwe's series that does
this change for all SPI drivers. Before you send each version have
a quick look to see if I've already picked that up. Or perhaps
better to just pick that up your self as a dependency to make
life easy. Just say you have done that in the cover letter.
> { }
> };
> MODULE_DEVICE_TABLE(spi, ad3530r_id);
>
next prev parent reply other threads:[~2026-06-21 16:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 6:20 [PATCH v2 0/4] Add support for AD3532R/AD3532 Kim Seer Paller
2026-06-15 6:20 ` [PATCH v2 1/4] iio: dac: ad3530r: Refactor setup to table-driven register bank approach Kim Seer Paller
2026-06-15 6:30 ` sashiko-bot
2026-06-15 7:22 ` Joshua Crofts
2026-06-15 10:08 ` Andy Shevchenko
2026-06-26 8:44 ` Paller, Kim Seer
2026-06-26 10:12 ` Andy Shevchenko
2026-06-21 16:49 ` Jonathan Cameron [this message]
2026-06-15 6:20 ` [PATCH v2 2/4] iio: ABI: add DAC 10kohm_to_gnd powerdown mode Kim Seer Paller
2026-06-15 6:32 ` sashiko-bot
2026-06-15 6:20 ` [PATCH v2 3/4] dt-bindings: iio: dac: add support for AD3532R/AD3532 Kim Seer Paller
2026-06-15 6:33 ` sashiko-bot
2026-06-15 6:20 ` [PATCH v2 4/4] iio: dac: ad3530r: Add " Kim Seer Paller
2026-06-15 6:33 ` sashiko-bot
2026-06-15 10:05 ` Andy Shevchenko
2026-06-21 16:45 ` Jonathan Cameron
2026-06-25 10:07 ` Paller, Kim Seer
2026-06-25 14:22 ` Andy Shevchenko
2026-06-25 10:06 ` Paller, Kim Seer
2026-06-26 10:11 ` Andy Shevchenko
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=20260621174930.35c2091f@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=kimseer.paller@analog.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@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