From: sashiko-bot@kernel.org
To: "Ettore Chimenti" <ettore.chimenti@linaro.org>
Cc: devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 06/10] ARM: dts: omap: dm816x: Update USB node
Date: Fri, 16 Oct 2026 14:54:23 +0000 [thread overview]
Message-ID: <sashiko-outbox-174501@kernel.org> (raw)
In-Reply-To: <20261016-patch-ektor5-dm8168-dts-v1-6-b4ce30217028@linaro.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dts: unit-address does not match the first address in the reg property
--
commit dbd2586a39796c2f0baed5e3349e527c7000f5a0
Author: Andrew Goodbody <andrew.goodbody@linaro.org>
ARM: dts: omap: dm816x: Update USB node
USB node was not working correctly with DMA enabled as the supporting
code had been updated without updating this SoC's device tree. Bring the
device tree more up to date so that it works with DMA enabled.
> diff --git a/arch/arm/boot/dts/ti/omap/dm816x.dtsi b/arch/arm/boot/dts/ti/omap/dm816x.dtsi
> index 7f3ef3a00ab86..5be9efc607855 100644
> --- a/arch/arm/boot/dts/ti/omap/dm816x.dtsi
> +++ b/arch/arm/boot/dts/ti/omap/dm816x.dtsi
[ ... ]
> @@ -574,18 +574,27 @@ uart3: serial@48024000 {
[ ... ]
> - usb0: usb@47401000 {
> + usb0: usb@1000 {
> compatible = "ti,musb-dm816";
> - reg = <0x47401400 0x400
> - 0x47401000 0x200>;
> + reg = <0x1400 0x400>,
> + <0x1000 0x200>;
[Severity: Low]
Should the unit address match the first address in the reg property? The unit
address is @1000 but the first reg starts at 0x1400. Should this be usb@1400?
[ ... ]
> @@ -622,10 +631,10 @@ &cppi41dma 11 1 &cppi41dma 12 1
> "tx14", "tx15";
> };
>
> - usb1: usb@47401800 {
> + usb1: usb@1800 {
> compatible = "ti,musb-dm816";
> - reg = <0x47401c00 0x400
> - 0x47401800 0x200>;
> + reg = <0x1c00 0x400>,
> + <0x1800 0x200>;
[Severity: Low]
Does this node have a similar mismatch? The unit address is @1800 but the
first reg starts at 0x1c00. Should it be usb@1c00?
[ ... ]
> @@ -662,12 +671,12 @@ &cppi41dma 26 1 &cppi41dma 27 1
> "tx14", "tx15";
> };
>
> - cppi41dma: dma-controller@47402000 {
> + cppi41dma: dma-controller@2000 {
> compatible = "ti,am3359-cppi41";
> - reg = <0x47400000 0x1000>,
> - <0x47402000 0x1000>,
> - <0x47403000 0x1000>,
> - <0x47404000 0x4000>;
> + reg = <0x0000 0x1000>,
> + <0x2000 0x1000>,
> + <0x3000 0x1000>,
> + <0x4000 0x4000>;
[Severity: Low]
Is it expected for the unit address to be @2000 when the first reg starts at
0x0000? Should this be dma-controller@0?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261016-patch-ektor5-dm8168-dts-v1-0-b4ce30217028@linaro.org?part=6
next prev parent reply other threads:[~2026-10-16 14:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 14:41 [PATCH 00/10] ARM: dts: dm816x: fixes and peripheral updates for DM8168 SoC Ettore Chimenti
2026-10-16 14:41 ` [PATCH 01/10] ARM: ti81xx: Prevent USB being put into idle Ettore Chimenti
2026-10-16 14:41 ` [PATCH 02/10] dt-bindings: pinctrl: Add devicetree bindings for DM816x SoC Pinctrl Ettore Chimenti
2026-10-16 14:45 ` sashiko-bot
2026-10-16 14:51 ` Krzysztof Kozlowski
2026-10-16 15:07 ` Ettore Chimenti
2026-10-16 14:41 ` [PATCH 03/10] ARM: dts: omap: dm816x: use dedicated SoC pinctrl Ettore Chimenti
2026-10-16 14:49 ` sashiko-bot
2026-10-16 14:41 ` [PATCH 04/10] ARM: dts: omap: dm816x: Fix pinctrl range Ettore Chimenti
2026-10-16 14:41 ` [PATCH 05/10] ARM: dts: omap: dm816x: refactor and align MMC node Ettore Chimenti
2026-10-16 14:41 ` [PATCH 06/10] ARM: dts: omap: dm816x: Update USB node Ettore Chimenti
2026-10-16 14:54 ` sashiko-bot [this message]
2026-10-16 14:41 ` [PATCH 07/10] ARM: omap: dm816x: Match up capability flags for USB Ettore Chimenti
2026-10-16 14:41 ` [PATCH 08/10] ARM: dts: omap: dm816x: Correct speed for sysclk5 Ettore Chimenti
2026-10-16 14:53 ` sashiko-bot
2026-10-16 14:41 ` [PATCH 09/10] ARM: dts: omap: dm8168-evm: Correct SD card pinmux Ettore Chimenti
2026-10-16 14:41 ` [PATCH 10/10] ARM: dts: omap: dm8168-evm: enable MUSB multipoint support Ettore Chimenti
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-174501@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ettore.chimenti@linaro.org \
--cc=linux-gpio@vger.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