From: sashiko-bot@kernel.org
To: "Tommaso Merciai" <tommaso.merciai.xr@bp.renesas.com>
Cc: robh@kernel.org, wsa+renesas@sang-engineering.com,
conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: renesas: r9a09g047: Add USB2.0 support
Date: Tue, 18 Aug 2026 14:38:10 +0000 [thread overview]
Message-ID: <20260818143810.BF6541F000E9@smtp.kernel.org> (raw)
In-Reply-To: <d72dcffe5427f03d1de8b8e50069a5fa0e4b7edc.1787062965.git.tommaso.merciai.xr@bp.renesas.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Device Tree nodes are not sorted by unit-address.
--
--- Patch [2]: [PATCH 2/3] arm64: dts: renesas: r9a09g047: Add USB2.0 support ---
commit d34912c9041670ddb50206c7be9fec96e890adfb
Author: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
arm64: dts: renesas: r9a09g047: Add USB2.0 support
This commit adds support for the USB2.0 channels on the Renesas RZ/G3E
SoC, including EHCI, OHCI, PHY, and reset control nodes.
> diff --git a/arch/arm64/boot/dts/renesas/r9a09g047.dtsi b/arch/arm64/boot/dts/renesas/r9a09g047.dtsi
> --- a/arch/arm64/boot/dts/renesas/r9a09g047.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r9a09g047.dtsi
> @@ -1773,6 +1773,130 @@ usb3_phy: usb-phy@15870000 {
> status = "disabled";
> };
>
> + ohci0: usb@15800000 {
> + compatible = "generic-ohci";
[ ... ]
> + ohci1: usb@15810000 {
> + compatible = "generic-ohci";
[ ... ]
> + ehci0: usb@15800100 {
[Severity: Low]
This isn't a bug, but should these newly added device tree nodes be sorted by
their unit-address?
The new nodes (starting with usb@15800000) are appended after the existing
usb-phy@15870000 node, which breaks the ascending unit-address order.
Additionally, within the new block itself, the nodes appear to be grouped by
peripheral type rather than being sorted numerically by their unit-address,
resulting in usb@15810000 being placed before usb@15800100.
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1787062965.git.tommaso.merciai.xr@bp.renesas.com?part=2
next prev parent reply other threads:[~2026-08-18 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 14:28 [PATCH 0/3] Add USB2.0 support for RZ/G3E Tommaso Merciai
2026-08-18 14:28 ` [PATCH 1/3] arm64: dts: renesas: r9a08g046: Add USB2.0 placeholder nodes Tommaso Merciai
2026-08-18 14:35 ` sashiko-bot
2026-08-18 14:29 ` [PATCH 2/3] arm64: dts: renesas: r9a09g047: Add USB2.0 support Tommaso Merciai
2026-08-18 14:38 ` sashiko-bot [this message]
2026-08-18 14:29 ` [PATCH 3/3] arm64: dts: renesas: r9a09g047e57-smarc: Enable " Tommaso Merciai
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=20260818143810.BF6541F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tommaso.merciai.xr@bp.renesas.com \
--cc=wsa+renesas@sang-engineering.com \
/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