From: sashiko-bot@kernel.org
To: "Janani Sunil" <janani.sunil@analog.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v11 3/3] iio: dac: Add AD5529R DAC driver support
Date: Wed, 02 Sep 2026 09:39:08 +0000 [thread overview]
Message-ID: <20260902093908.A1DF51F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260902-ad5529r-driver-v11-3-301c491a0719@analog.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Selecting REGMAP_SPI without inheriting its dependency on SPI causes unmet direct dependency warnings.
--
commit 4f95e4db1e621b9be7d174948b61e89bec2d8d32
Author: Janani Sunil <janani.sunil@analog.com>
iio: dac: Add AD5529R DAC driver support
This commit adds support for the Analog Devices AD5529R 16-channel, 12/16 bit DAC.
The device communicates over SPI and supports per-channel output range
configuration and an optional external reference.
> diff --git a/drivers/iio/dac/Kconfig b/drivers/iio/dac/Kconfig
> --- a/drivers/iio/dac/Kconfig
> +++ b/drivers/iio/dac/Kconfig
[ ... ]
> +config AD5529R
> + tristate "Analog Devices AD5529R High Voltage DAC driver"
> + depends on SPI_MASTER
> + select REGMAP_SPI
[Severity: Low]
Will this cause Kconfig unmet direct dependency warnings and subsequent
linker errors if a user configures SPI=m?
When SPI=m, the boolean SPI_MASTER evaluates to y. This allows AD5529R to
be configured as y, which in turn forces REGMAP_SPI to y.
Since REGMAP_SPI depends on the SPI tristate symbol, selecting it without
inheriting its dependency on SPI can lead to undefined references to SPI
core functions during the vmlinux linking stage.
> + help
> + Say yes here to build support for Analog Devices AD5529R 16-Channel,
> + 12-Bit/16-Bit, 40V High Voltage Precision Digital to Analog Converter.
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260902-ad5529r-driver-v11-0-301c491a0719@analog.com?part=3
next prev parent reply other threads:[~2026-09-02 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 9:26 [PATCH v11 0/3] iio: dac: Add support for AD5529R DAC Janani Sunil
2026-09-02 9:26 ` [PATCH v11 1/3] spi: dt-bindings: Add spi-device-addr peripheral property Janani Sunil
2026-09-02 9:26 ` [PATCH v11 2/3] dt-bindings: iio: dac: Add AD5529R Janani Sunil
2026-09-02 9:36 ` sashiko-bot
2026-09-02 9:26 ` [PATCH v11 3/3] iio: dac: Add AD5529R DAC driver support Janani Sunil
2026-09-02 9:39 ` sashiko-bot [this message]
2026-09-02 11:04 ` Andy Shevchenko
2026-09-02 12:56 ` 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=20260902093908.A1DF51F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=janani.sunil@analog.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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