From: sashiko-bot@kernel.org
To: "Kim Seer Paller" <kimseer.paller@analog.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/4] dt-bindings: iio: dac: add adi,ad5710r.yaml
Date: Sat, 29 Aug 2026 06:10:54 +0000 [thread overview]
Message-ID: <20260829061055.2F4A91F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260829-iio-ad5710r-upstream-v4-2-8af3121c7d21@analog.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The device tree example and schema documentation incorrectly require and include a header from an unrelated device (`adi,ad74413r.h`) to configure the AD5710R's channel functions.
--
commit 3746051355b5551010e58f435b49ff4409ec4699
Author: Kim Seer Paller <kimseer.paller@analog.com>
dt-bindings: iio: dac: add adi,ad5710r.yaml
This commit introduces device tree bindings for the Analog Devices
AD5710R/AD5711R DACs. It defines properties for power supplies, SPI
configuration, and per-channel output types.
> diff --git a/Documentation/devicetree/bindings/iio/dac/adi,ad5710r.yaml b/Documentation/devicetree/bindings/iio/dac/adi,ad5710r.yaml
> new file mode 100644
> index 0000000000000..259866ca87cff
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/dac/adi,ad5710r.yaml
[ ... ]
> + adi,ch-func:
> + description:
> + Channel output type. Use CH_FUNC_VOLTAGE_OUTPUT for voltage
> + output or CH_FUNC_CURRENT_OUTPUT for current output.
[Severity: Low]
Does this documentation suggest macros that don't exist for this specific
device? It seems these macros are not provided in any device-specific
header for the AD5710R, which might confuse users trying to configure the
channel output type.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [1, 2]
[ ... ]
> +examples:
> + - |
> + #include <dt-bindings/iio/addac/adi,ad74413r.h>
[Severity: Low]
Is this include directive for an unrelated device intentional here?
Including a device-specific header for an entirely different component
creates an illogical dependency. This masks the missing macro definitions
mentioned above by coupling the configuration to an inappropriate source.
Could this break or cause confusion if the ad74413r bindings are ever
refactored?
> +
> + spi {
> + #address-cells = <1>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260829-iio-ad5710r-upstream-v4-0-8af3121c7d21@analog.com?part=2
next prev parent reply other threads:[~2026-08-29 6:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 5:59 [PATCH v4 0/4] Add support for AD5710R/AD5711R DAC Kim Seer Paller
2026-08-29 5:59 ` [PATCH v4 1/4] iio: ABI: Add DAC current powerdown attributes and 15kohm_to_gnd mode Kim Seer Paller
2026-08-29 6:05 ` sashiko-bot
2026-08-29 5:59 ` [PATCH v4 2/4] dt-bindings: iio: dac: add adi,ad5710r.yaml Kim Seer Paller
2026-08-29 6:10 ` sashiko-bot [this message]
2026-08-31 17:04 ` Conor Dooley
2026-09-01 3:14 ` Jonathan Cameron
2026-09-01 17:45 ` Conor Dooley
2026-08-29 5:59 ` [PATCH v4 3/4] iio: dac: ad3530r: parameterize DAC resolution Kim Seer Paller
2026-08-29 5:59 ` [PATCH v4 4/4] iio: dac: ad3530r: add support for AD5710R/AD5711R Kim Seer Paller
2026-08-29 17:36 ` Jonathan Cameron
2026-08-31 7:39 ` 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=20260829061055.2F4A91F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kimseer.paller@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