From: sashiko-bot@kernel.org
To: "Chukun Pan" <amadeus@jmu.edu.cn>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/1] riscv: dts: spacemit: enable QSPI for OrangePi RV2
Date: Sat, 16 May 2026 08:06:46 +0000 [thread overview]
Message-ID: <20260516080646.94E4DC2BCB7@smtp.kernel.org> (raw)
In-Reply-To: <20260516080030.1736836-1-amadeus@jmu.edu.cn>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Mismatch between node unit-address and 'reg' property for the uboot partition.
--
commit ac1df28fb4536a816c17f35ce989f0804943afb5
Author: Chukun Pan <amadeus@jmu.edu.cn>
riscv: dts: spacemit: enable QSPI for OrangePi RV2
This commit enables the QSPI controller and the XM25QU128C SPI NOR flash
on the OrangePi RV2 board. It also adds a flash partition layout derived
from the vendor U-Boot.
> diff --git a/arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts b/arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts
> --- a/arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts
> +++ b/arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts
[ ... ]
> + opensbi@70000 {
> + reg = <0x70000 0x030000>;
> + };
> +
> + uboot@a00000 {
> + reg = <0xa0000 0x760000>;
Is there a mismatch between the unit-address and the reg property here?
The node name uses a00000 (implying an address of 0xa00000), but the reg
property specifies a start address of 0xa0000.
This difference will usually trigger a unit_address_vs_reg warning when
compiling the device tree with dtc. Should the node name or the reg address
be updated so they match exactly?
> + };
> + };
> + };
> +};
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260516080030.1736836-1-amadeus@jmu.edu.cn?part=1
next prev parent reply other threads:[~2026-05-16 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 8:00 [PATCH 1/1] riscv: dts: spacemit: enable QSPI for OrangePi RV2 Chukun Pan
2026-05-16 8:06 ` sashiko-bot [this message]
2026-05-16 12:58 ` Yixun Lan
2026-05-16 13:03 ` Yixun Lan
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=20260516080646.94E4DC2BCB7@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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