Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Marek Vasut" <marex@nabladev.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: st: Add UCPD node on stm32mp231
Date: Wed, 19 Aug 2026 16:42:20 +0000	[thread overview]
Message-ID: <20260819164220.7472B1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260819163410.119755-3-marex@nabladev.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Duplicate unit-address for sibling NVMEM cell nodes 'package-otp@1e8' and 'atrim3@1e8'.
--

--- Patch [3]: [PATCH 3/4] arm64: dts: st: Add UCPD node on stm32mp231 ---
commit 73383f2b2e9f887b4df27458fed89459eba124e2
Author: Marek Vasut <marex@nabladev.com>

arm64: dts: st: Add UCPD node on stm32mp231

This commit adds the ST UCPD Type-C block node to the stm32mp231 device tree.
It also adds the UCPD Rp/Rd resistor trimming values as a new nvmem cell
subnode pointing to the OTP registers.

> diff --git a/arch/arm64/boot/dts/st/stm32mp231.dtsi b/arch/arm64/boot/dts/st/stm32mp231.dtsi
> index 9e1d240888ff2..5049e031a38dd 100644
> --- a/arch/arm64/boot/dts/st/stm32mp231.dtsi
> +++ b/arch/arm64/boot/dts/st/stm32mp231.dtsi
[ ... ]
> @@ -794,6 +809,11 @@ package-otp@1e8 {
>  				reg = <0x1e8 0x1>;
>  				bits = <0 3>;
>  			};
> +
> +			ucpdtrim: atrim3@1e8 {

[Severity: Low]
Does this duplicate unit address cause a dtc warning during the build?

Both package-otp and the newly added atrim3 node share the @1e8 unit address,
which violates the device tree specification requirement for unique sibling
unit addresses.

> +				reg = <0x1e8 0x4>;
> +				bits = <4 16>;
> +			};
>  		};
>  
>  		rcc: clock-controller@44200000 {

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260819163410.119755-1-marex@nabladev.com?part=3

  reply	other threads:[~2026-08-19 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19 16:33 [PATCH 1/4] dt-bindings: usb: Document ST UCPD Marek Vasut
2026-08-19 16:33 ` [PATCH 2/4] usb: typec: ucpd: Add ST UCPD driver Marek Vasut
2026-08-19 16:47   ` sashiko-bot
2026-08-19 16:33 ` [PATCH 3/4] arm64: dts: st: Add UCPD node on stm32mp231 Marek Vasut
2026-08-19 16:42   ` sashiko-bot [this message]
2026-08-19 16:33 ` [PATCH 4/4] arm64: dts: st: Add UCPD node on stm32mp251 Marek Vasut
2026-08-19 16:44 ` [PATCH 1/4] dt-bindings: usb: Document ST UCPD sashiko-bot

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=20260819164220.7472B1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=marex@nabladev.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