All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Xincheng Ji" <jixincheng@ultrarisc.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v6 5/7] riscv: dts: ultrarisc: Add initial device tree for UltraRISC DP1000
Date: Sat, 24 Oct 2026 09:43:21 +0000	[thread overview]
Message-ID: <sashiko-outbox-183627@kernel.org> (raw)
In-Reply-To: <20261024-ultrarisc-dts-v6-5-c62994d8a114@ultrarisc.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] riscv: dts: ultrarisc: duplicate unit-address in dp1000.dtsi plic node name
--

commit 65da27c69d1760ac79d94c2145794b0d0a24ad1f
Author: Jia Wang <wangjia@ultrarisc.com>

riscv: dts: ultrarisc: Add initial device tree for UltraRISC DP1000

This commit adds the initial base device tree for the UltraRISC DP1000 SoC,
describing the eight CP100 CPU cores, cache hierarchy, and core peripherals.

> diff --git a/arch/riscv/boot/dts/ultrarisc/dp1000.dtsi b/arch/riscv/boot/dts/ultrarisc/dp1000.dtsi
> new file mode 100644
> index 0000000000000..f8f29df1801f4
> --- /dev/null
> +++ b/arch/riscv/boot/dts/ultrarisc/dp1000.dtsi
> @@ -0,0 +1,865 @@

[ ... ]

> +	soc {
> +		compatible = "simple-bus";
> +		ranges;
> +		#address-cells = <2>;
> +		#size-cells = <2>;

[ ... ]

> +		plic: interrupt-controller@9000000@9000000 {
> +			compatible = "ultrarisc,dp1000-plic", "ultrarisc,cp100-plic";
> +			reg = <0x0 0x9000000 0x0 0x4000000>;

[Severity: Low]
Should the plic node name be interrupt-controller@9000000 instead of
interrupt-controller@9000000@9000000?

The duplicated @9000000 suffix causes dtc to fail compilation in
scripts/dtc/checks.c:check_node_name_format() when building any board
device tree that includes dp1000.dtsi:

    if (strchr(get_unitname(node), '@'))
        FAIL(c, dti, node, "multiple '@' characters in node name");

It also causes check_simple_bus_reg() and dtbs_check validation to fail
because the unit-address does not match the reg property address.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261024-ultrarisc-dts-v6-0-c62994d8a114@ultrarisc.com?part=5

  reply	other threads:[~2026-10-24  9:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24  9:27 [PATCH v6 0/7] riscv: Add device tree support for UltraRISC DP1000 Xincheng Ji
2026-10-24  9:27 ` Xincheng Ji via B4 Relay
2026-10-24  9:27 ` Xincheng Ji via B4 Relay
2026-10-24  9:27 ` [PATCH v6 1/7] dt-bindings: vendor-prefixes: Add shenrongda Xincheng Ji
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:27 ` [PATCH v6 2/7] dt-bindings: riscv: cpus: Add UltraRISC CP100 compatible Xincheng Ji
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:27 ` [PATCH v6 3/7] dt-bindings: riscv: Add UltraRISC DP1000 board compatibles Xincheng Ji
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:27 ` [PATCH v6 4/7] dt-bindings: timer: Add UltraRISC DP1000 CLINT Xincheng Ji
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:27 ` [PATCH v6 5/7] riscv: dts: ultrarisc: Add initial device tree for UltraRISC DP1000 Xincheng Ji
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:43   ` sashiko-bot [this message]
2026-10-24 10:18     ` Xincheng Ji
2026-10-24  9:27 ` [PATCH v6 6/7] riscv: dts: ultrarisc: Add Shenzhen Rongda M0 board device tree Xincheng Ji
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:41   ` sashiko-bot
2026-10-24  9:27 ` [PATCH v6 7/7] riscv: dts: ultrarisc: Add Milk-V Titan " Xincheng Ji
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:27   ` Xincheng Ji via B4 Relay
2026-10-24  9:50   ` 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=sashiko-outbox-183627@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jixincheng@ultrarisc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.