From: Conor Dooley <conor@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: Xincheng Ji <jixincheng@ultrarisc.com>,
devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 5/7] riscv: dts: ultrarisc: Add initial device tree for UltraRISC DP1000
Date: Wed, 14 Oct 2026 17:53:22 +0100 [thread overview]
Message-ID: <20261014-ramp-dioxide-63e1d5e0499f@spud> (raw)
In-Reply-To: <sashiko-outbox-169523@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2411 bytes --]
On Tue, Oct 13, 2026 at 10:36:18AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] dts: L2 cache nodes are incorrectly nested as children of cpu nodes
> --
>
> commit 72d6d58d85f9aab9e46d9c7167175451c2551346
> Author: Jia Wang <wangjia@ultrarisc.com>
>
> riscv: dts: ultrarisc: Add initial device tree for UltraRISC DP1000
>
> Add the base device tree for the UltraRISC DP1000 SoC. It describes
> eight CP100 CPU cores, their cache topology, and essential 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..86d7f5533aa84
> > --- /dev/null
> > +++ b/arch/riscv/boot/dts/ultrarisc/dp1000.dtsi
> > @@ -0,0 +1,899 @@
> [ ... ]
> > + cpus {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + timebase-frequency = <10000000>;
> > +
> > + cpu0: cpu@0 {
> > + compatible = "ultrarisc,cp100", "riscv";
> [ ... ]
> > + cpu0_intc: interrupt-controller {
> > + compatible = "riscv,cpu-intc";
> > + interrupt-controller;
> > + #interrupt-cells = <1>;
> > + };
> > +
> > + l2_cache0: l2-cache {
>
> [Severity: Medium]
> Does this incorrectly nest the L2 cache nodes as children of the cpu nodes?
>
> Standard Devicetree topologies for CPU schemas require cache nodes to be
> defined as siblings under the /cpus node or globally, rather than as direct
> children of the cpu nodes. Instantiating l2-cache here can cause
> dt_binding_check validation failures and break generic kernel cache topology
> parsers that expect the cache nodes at the root of /cpus and referenced via
> the next-level-cache phandle.
>
> Should these cache nodes be moved outside of the cpu@0 node?
This seems like a fairly reasonable comment from Sashiko. Does keeping it
here lead to hwloc incorrectly displaying your topology?
>
> > + /*
> > + * L2 cache:
> > + * cache-unified, block-size 64B
> > + * 8-way set associative, size 512KB
> > + * per-core.
> > + */
> > + compatible = "cache";
> > + cache-block-size = <64>;
> > + cache-level = <2>;
> > + cache-size = <0x80000>;
> > + cache-sets = <1024>;
> > + cache-unified;
> > + next-level-cache = <&cluster0_l3>;
> > + };
> > + };
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-10-14 16:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 10:21 [PATCH v3 0/7] riscv: Add device tree support for UltraRISC DP1000 Xincheng Ji via B4 Relay
2026-10-13 10:21 ` [PATCH v3 1/7] dt-bindings: vendor-prefixes: Add shenrongda Xincheng Ji via B4 Relay
2026-10-13 10:21 ` [PATCH v3 2/7] dt-bindings: riscv: cpus: Add UltraRISC CP100 compatible Xincheng Ji via B4 Relay
2026-10-13 10:21 ` [PATCH v3 3/7] dt-bindings: riscv: Add UltraRISC DP1000 board compatibles Xincheng Ji via B4 Relay
2026-10-13 10:21 ` [PATCH v3 4/7] dt-bindings: timer: Add UltraRISC DP1000 CLINT Xincheng Ji via B4 Relay
2026-10-13 10:21 ` [PATCH v3 5/7] riscv: dts: ultrarisc: Add initial device tree for UltraRISC DP1000 Xincheng Ji via B4 Relay
2026-10-13 10:36 ` sashiko-bot
2026-10-14 16:53 ` Conor Dooley [this message]
2026-10-13 10:21 ` [PATCH v3 6/7] riscv: dts: ultrarisc: Add Shenzhen Rongda M0 board device tree Xincheng Ji via B4 Relay
2026-10-13 10:21 ` [PATCH v3 7/7] riscv: dts: ultrarisc: Add Milk-V Titan " Xincheng Ji via B4 Relay
2026-10-13 10:31 ` sashiko-bot
2026-10-13 17:34 ` Conor Dooley
2026-10-13 18:08 ` Andrew Lunn
2026-10-14 7:53 ` Xincheng Ji
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=20261014-ramp-dioxide-63e1d5e0499f@spud \
--to=conor@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox