Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kyle Hsieh" <kylehsieh1995@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/3] ARM: dts: aspeed: ventura2: Add LTC2305 ADCs
Date: Fri, 06 Nov 2026 03:09:02 +0000	[thread overview]
Message-ID: <sashiko-outbox-200623@kernel.org> (raw)
In-Reply-To: <20261106-ventura2-dts-update-v1-1-b085ece9bf57@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] ARM: dts: aspeed: ventura2: missing vref-supply violates lltc,ltc2497.yaml
--

commit 13d509351ee73dbf947376a477d0e32c8ab7eea1
Author: Kyle Hsieh <kylehsieh1995@gmail.com>

ARM: dts: aspeed: ventura2: Add LTC2305 ADCs

This commit adds three lltc,ltc2305 ADC nodes to the Facebook Ventura2 BMC
device tree (under i2c0mux0ch2 and i2c3) without vref-supply properties and
wires the i2c3 channels into iio-hwmon.

> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-ventura2.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-ventura2.dts
> index f3dbdece30767..50e652cc37a17 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-ventura2.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-ventura2.dts

[ ... ]

> @@ -392,6 +393,12 @@ i2c0mux0ch2: i2c@2 {
>  			reg = <2>;
>  			#address-cells = <1>;
>  			#size-cells = <0>;
> +
> +			adc@8 {
> +				compatible = "lltc,ltc2305";
> +				reg = <0x08>;
> +				#io-channel-cells = <1>;
> +			};
>  		};
>  
>  		i2c0mux0ch3: i2c@3 {
> @@ -583,6 +590,18 @@ &i2c3 {
>  
>  	status = "okay";
>  
> +	adc_op_fb1: adc@8 {
> +		compatible = "lltc,ltc2305";
> +		reg = <0x08>;
> +		#io-channel-cells = <1>;
> +	};
> +
> +	adc_op_fb2: adc@9 {
> +		compatible = "lltc,ltc2305";
> +		reg = <0x09>;
> +		#io-channel-cells = <1>;
> +	};

[Severity: Low]
Although ltc2309_probe() in drivers/iio/adc/ltc2309.c treats vref-supply as
optional and falls back to LTC2309_INTERNAL_REF_MV when it is absent, the
binding schema in Documentation/devicetree/bindings/iio/adc/lltc,ltc2497.yaml
unconditionally requires vref-supply:

required:
  - compatible
  - reg
  - vref-supply

Doesn't omitting vref-supply on adc@8 under i2c0mux0ch2 and on adc_op_fb1 and
adc_op_fb2 under i2c3 cause make dtbs_check validation errors on
arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-ventura2.dtb unless
Documentation/devicetree/bindings/iio/adc/lltc,ltc2497.yaml is updated first
to make vref-supply optional for lltc,ltc2305 and lltc,ltc2309?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261106-ventura2-dts-update-v1-0-b085ece9bf57@gmail.com?part=1

  reply	other threads:[~2026-11-06  3:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06  3:08 [PATCH 0/3] ARM: dts: aspeed: ventura2: Add LTC2305 ADCs and GPIO line names Kyle Hsieh
2026-11-06  3:08 ` [PATCH 1/3] ARM: dts: aspeed: ventura2: Add LTC2305 ADCs Kyle Hsieh
2026-11-06  3:09   ` sashiko-bot [this message]
2026-11-06  3:08 ` [PATCH 2/3] ARM: dts: aspeed: ventura2: Name the COMe presence GPIO Kyle Hsieh
2026-11-06  3:08 ` [PATCH 3/3] ARM: dts: aspeed: ventura2: Name the USB-UART bridge reset GPIOs Kyle Hsieh

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=sashiko-outbox-200623@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kylehsieh1995@gmail.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