From: sashiko-bot@kernel.org
To: "Frank Li via B4 Relay" <devnull+Frank.Li.nxp.com@kernel.org>
Cc: krzk+dt@kernel.org, devicetree@vger.kernel.org,
conor+dt@kernel.org, Frank.Li@kernel.org, imx@lists.linux.dev,
robh@kernel.org
Subject: Re: [PATCH 1/6] ARM: dts: imx: add (power|vdd)-supply for related node
Date: Fri, 15 May 2026 21:52:39 +0000 [thread overview]
Message-ID: <20260515215240.7A644C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260515-imx25_dts_simple_warning_2-v1-1-b06bff192a05@nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly added `reg_5v` regulator in `imx53-sk-imx53.dts` incorrectly has `regulator-name = "usb_vbus"`.
--
commit 1eaf7d9176cad41b8d33d56943e5b16020f26bf0
Author: Frank Li <Frank.Li@nxp.com>
ARM: dts: imx: add (power|vdd)-supply for related node
This commit adds required power-supply and vdd-supply properties to fix
CHECK_DTB warnings for several imx devicetrees.
> diff --git a/arch/arm/boot/dts/nxp/imx/imx53-sk-imx53.dts b/arch/arm/boot/dts/nxp/imx/imx53-sk-imx53.dts
> index 1a00d290092ad..c1e065359fd2d 100644
> --- a/arch/arm/boot/dts/nxp/imx/imx53-sk-imx53.dts
> +++ b/arch/arm/boot/dts/nxp/imx/imx53-sk-imx53.dts
> @@ -29,6 +29,13 @@ memory@70000000 {
> reg = <0x70000000 0x20000000>;
> };
>
> + reg_5v: regulator-5v {
> + compatible = "regulator-fixed";
> + regulator-name = "usb_vbus";
Is "usb_vbus" the intended name for this regulator?
Since this regulator is used to power the display panel, the name appears
to be a copy-paste error from the reg_usb1_vbus node directly below it.
Defining multiple regulators with the exact same name can cause sysfs
directory collisions and registration warnings in the regulator subsystem.
Would a unique name like "5V" or "panel-5v" be more appropriate here?
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + };
> +
> reg_usb1_vbus: regulator-usb-vbus {
> compatible = "regulator-fixed";
> regulator-name = "usb_vbus";
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260515-imx25_dts_simple_warning_2-v1-0-b06bff192a05@nxp.com?part=1
next prev parent reply other threads:[~2026-05-15 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 21:40 [PATCH 0/6] ARM: dts: cleanup some CHECK_DTBS warning for imx5/6 (round 2) Frank Li via B4 Relay
2026-05-15 21:40 ` [PATCH 1/6] ARM: dts: imx: add (power|vdd)-supply for related node Frank Li via B4 Relay
2026-05-15 21:52 ` sashiko-bot [this message]
2026-05-15 21:40 ` [PATCH 2/6] ARM: dts: imx: remove redundant bus-width for video-mux Frank Li via B4 Relay
2026-05-15 21:40 ` [PATCH 3/6] ARM: dts: imx: Add bus-type for ov5642/ov5640 Frank Li via B4 Relay
2026-05-15 21:40 ` [PATCH 4/6] ARM: dts: imx6qdl-tx6: remove undocumented karo,imx6qdl-tx6-sgtl5000 and keep only simple-audio-card Frank Li via B4 Relay
2026-05-15 21:40 ` [PATCH 5/6] ARM: dts: imx: replace undocumented compatible string edt,edt-ft5x06 with edt,edt-ft5206 Frank Li via B4 Relay
2026-05-16 0:18 ` sashiko-bot
2026-05-15 21:40 ` [PATCH 6/6] ARM: dts: imx6-display5: replace marvell,88E1510 with ethernet-phy-ieee802.3-c22 Frank Li via B4 Relay
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=20260515215240.7A644C2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+Frank.Li.nxp.com@kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--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