Devicetree
 help / color / mirror / Atom feed
From: Jia Wang <wangjia@ultrarisc.com>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: Jia Wang <wangjia@ultrarisc.com>, Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <pjw@kernel.org>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	 Alexandre Ghiti <alex@ghiti.fr>,
	Linus Walleij <linusw@kernel.org>,
	 Bartosz Golaszewski <brgl@kernel.org>,
	 Samuel Holland <samuel.holland@sifive.com>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	 Palmer Dabbelt <palmer@sifive.com>,
	Conor Dooley <conor@kernel.org>,
	 devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	 linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH 5/9] riscv: dts: ultrarisc: Add initial device tree for UltraRISC DP1000
Date: Wed, 20 May 2026 10:51:29 +0800	[thread overview]
Message-ID: <177924548998.823562.8301642486475031179.b4-reply@b4> (raw)
In-Reply-To: <20260515-morbidity-rule-d8504467b252@wendy>

On 2026-05-15 11:26 +0100, Conor Dooley wrote:
> On Fri, May 15, 2026 at 09:18:01AM +0800, Jia Wang wrote:
> > Add the base device tree for the UltraRISC DP1000 SoC. It describes the
> > 8×CP100 CPU cores and essential SoC peripherals including the interrupt
> > controller, pinctrl, GPIO, UART, SPI, I2C, PCIe, GMAC and the DMA
> > controller.
> > 
> > Link: https://lore.kernel.org/lkml/20260427-ultrarisc-pcie-v4-2-98935f6cdfb5@ultrarisc.com/
> > Link: https://lore.kernel.org/lkml/20260429-ultrarisc-serial-v7-3-e475cce9e274@ultrarisc.com/
> > 
> 
> No blank line here FYI.
>

Thanks for the review.

I'll remove the blank line in v2.
 
> > Signed-off-by: Jia Wang <wangjia@ultrarisc.com>
> > ---
> >  MAINTAINERS                               |   1 +
> >  arch/riscv/boot/dts/ultrarisc/dp1000.dtsi | 851 ++++++++++++++++++++++++++++++
> >  2 files changed, 852 insertions(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index baaaa46b1a56..832e01898ae5 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -23087,6 +23087,7 @@ M:	Jia Wang <wangjia@ultrarisc.com>
> >  L:	linux-riscv@lists.infradead.org
> >  S:	Maintained
> >  F:	Documentation/devicetree/bindings/riscv/ultrarisc.yaml
> > +F:	arch/riscv/boot/dts/ultrarisc/
> >  
> >  RNBD BLOCK DRIVERS
> >  M:	Md. Haris Iqbal <haris.iqbal@ionos.com>
> > diff --git a/arch/riscv/boot/dts/ultrarisc/dp1000.dtsi b/arch/riscv/boot/dts/ultrarisc/dp1000.dtsi
> > new file mode 100644
> > index 000000000000..1aae53fc1a2b
> > --- /dev/null
> > +++ b/arch/riscv/boot/dts/ultrarisc/dp1000.dtsi
> > @@ -0,0 +1,851 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +/*
> > + * Copyright(C) 2026 UltraRISC Technology (Shanghai) Co., Ltd.
> > + */
> > +
> > +/dts-v1/;
> > +
> > +/ {
> > +	compatible = "ultrarisc,dp1000";
> > +	#address-cells = <2>;
> > +	#size-cells = <2>;
> > +
> > +	cpus {
> > +		#address-cells = <1>;
> > +		#size-cells = <0>;
> > +		timebase-frequency = <10000000>;
> > +
> > +		cpu0: cpu@0 {
> > +			compatible = "ultrarisc,cp100", "riscv";
> > +			reg = <0x0>;
> > +			device_type = "cpu";
> > +			riscv,isa = "rv64imafdcbh";
> 
> Drop this property, its replacements (below) should be supported by all
> users.
> 

Will drop it in v2, thanks.

> > +			riscv,isa-base = "rv64i";
> > +			riscv,isa-extensions = "i", "m", "a", "f", "d", "c", "b", "h",
> > +					       "zba", "zbb", "zbc", "zbs", "zicntr",
> > +					       "zicsr", "zifencei", "zihpm", "ziccif",
> > +					       "ziccrse", "ziccamoa", "za64rs", "zicbom",
> > +					       "zicbop", "zicboz", "zkt", "svade",
> > +					       "ssccptr", "sstvecd", "sscounterenw",
> > +					       "shcounterenw", "shtvala", "shvstvecd",
> > +					       "shvsatpa", "svvptc";
> > +			mmu-type = "riscv,sv48";
> > +			clock-frequency = <2000000000>;
> > +			/* L1 I-cache and D-cache:
> 
> FYI, the comment format outside of drivers/net/ has a newline after /*.
> 

Will fix the comment style in v2.

> > +			 * block-size 64B
> > +			 * 4-way set associative, size 64KB
> > +			 * per-core.
> > +			 */
> > +			d-cache-block-size = <64>;
> > +			d-cache-sets = <256>;
> > +			d-cache-size = <0x10000>;
> > +			i-cache-block-size = <64>;
> > +			i-cache-sets = <256>;
> > +			i-cache-size = <0x10000>;
> > +			next-level-cache = <&l2_cache0>;
> > +			riscv,cbom-block-size = <64>;
> > +			riscv,cboz-block-size = <64>;
> > +
> > +			cpu0_intc: interrupt-controller {
> > +				compatible = "riscv,cpu-intc";
> > +				interrupt-controller;
> > +				#interrupt-cells = <0x01>;
> > +			};
> > +
> > +			l2_cache0: l2-cache {
> > +				/* 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>;
> > +			};
> > +		};
> 
> > +		cpu4: cpu@4 {
> > +			compatible = "ultrarisc,cp100", "riscv";
> > +			reg = <0x10>;
> 
> Sashiko correctly pointed out that this is wrong.
> 
> > +		cpu5: cpu@5 {
> > +			compatible = "ultrarisc,cp100", "riscv";
> > +			reg = <0x11>;
> 
> And so is this.
> 
> > +		cpu6: cpu@6 {
> > +			compatible = "ultrarisc,cp100", "riscv";
> > +			reg = <0x12>;
> 
> And this.
> 
> > +		cpu7: cpu@7 {
> > +			compatible = "ultrarisc,cp100", "riscv";
> > +			reg = <0x13>;
> 
> And this.
> 

Will fix the unit addresses (cpu@10..cpu@13) in v2.

> > +	clocks {
> 
> I've commented on this in the cover letter.
> 

Thanks, I saw your comment in the cover letter. I’ll address it in v2.

> > +		device_clk: device_clk {
> > +			compatible = "fixed-clock";
> > +			clock-frequency = <62500000>;
> > +			#clock-cells = <0>;
> > +		};
> > +
> > +		timer_clk: timer_clk {
> > +			compatible = "fixed-clock";
> > +			clock-frequency = <50000000>;
> > +			#clock-cells = <0>;
> > +		};
> > +
> > +		csr_clk: csr_clk {
> > +			compatible = "fixed-clock";
> > +			clock-frequency = <250000000>;
> > +			#clock-cells = <0>;
> > +		};
> > +	};
> 
> > +	memory@80000000 {
> > +		device_type = "memory";
> > +		reg = <0x00 0x80000000 0x4 0x00000000>;
> > +	};
> 
> This looks incorrectly placed, memory should be in the board dts unless
> it is actually a part of the chip.
> 

Will move the memory node to the board dts in v2.

> > +
> > +	soc {
> > +		compatible = "simple-bus";
> > +		ranges;
> > +		#address-cells = <0x02>;
> > +		#size-cells = <0x02>;
> > +
> > +		clint: clint@8000000 {
> > +			compatible = "sifive,clint0", "riscv,clint0";
> 
> Missing a device-specific clint compatible.
> 
> > +			reg = <0x00 0x8000000 0x00 0x100000>;
> > +			interrupts-extended = <&cpu0_intc 0x03>, <&cpu0_intc 0x07>,
> > +					      <&cpu1_intc 0x03>, <&cpu1_intc 0x07>,
> > +					      <&cpu2_intc 0x03>, <&cpu2_intc 0x07>,
> > +					      <&cpu3_intc 0x03>, <&cpu3_intc 0x07>,
> > +					      <&cpu4_intc 0x03>, <&cpu4_intc 0x07>,
> > +					      <&cpu5_intc 0x03>, <&cpu5_intc 0x07>,
> > +					      <&cpu6_intc 0x03>, <&cpu6_intc 0x07>,
> > +					      <&cpu7_intc 0x03>, <&cpu7_intc 0x07>;
> > +		};
> > +
> > +		plic: plic@9000000 {
> > +			compatible = "ultrarisc,dp1000-plic", "ultrarisc,cp100-plic";
> > +			reg = <0x00 0x9000000 0x00 0x4000000>;
> > +			#interrupt-cells = <1>;
> > +			#address-cells = <0>;
> > +			interrupt-controller;
> > +			interrupts-extended = <&cpu0_intc 0xb>, <&cpu0_intc 0x9>, <&cpu0_intc 0xa>,
> > +					      <&cpu1_intc 0xb>, <&cpu1_intc 0x9>, <&cpu1_intc 0xa>,
> > +					      <&cpu2_intc 0xb>, <&cpu2_intc 0x9>, <&cpu2_intc 0xa>,
> > +					      <&cpu3_intc 0xb>, <&cpu3_intc 0x9>, <&cpu3_intc 0xa>,
> > +					      <&cpu4_intc 0xb>, <&cpu4_intc 0x9>, <&cpu4_intc 0xa>,
> > +					      <&cpu5_intc 0xb>, <&cpu5_intc 0x9>, <&cpu5_intc 0xa>,
> > +					      <&cpu6_intc 0xb>, <&cpu6_intc 0x9>, <&cpu6_intc 0xa>,
> > +					      <&cpu7_intc 0xb>, <&cpu7_intc 0x9>, <&cpu7_intc 0xa>;
> > +			riscv,ndev = <160>;
> > +		};
> > +
> > +		pmx0: pinmux@11081000 {
> > +			compatible = "ultrarisc,dp1000-pinctrl";
> > +			reg = <0x0 0x11081000  0x0 0x1000>;
>                                              ^^ extra space here btw
> 

Will fix it in v2.

> > +			#pinctrl-cells = <2>;
> > +		};
> > +
> > +		spi0: spi@20320000 {
> > +			compatible = "snps,dw-apb-ssi";
> 
> Missing a device-specific compatible here, can just fall abck to the
> dw-apb-ssi one, so no need to make driver changes.
> 
> > +			reg = <0x0 0x20320000 0x0 0x1000>;
> > +			#address-cells = <1>;
> > +			#size-cells = <0>;
> > +			clocks = <&device_clk>;
> > +			interrupt-parent = <&plic>;
> > +			interrupts = <19>;
> > +			num-cs = <3>;
> > +		};
> 
> > +
> > +		i2c0: i2c@20330000 {
> > +			compatible = "snps,designware-i2c";
> 
> Same applies here.
> 
> > +			reg = <0x0 0x20330000 0x0 0x100>;
> > +			#address-cells = <1>;
> > +			#size-cells = <0>;
> > +			clock-frequency = <400000>;
> > +			clocks = <&device_clk>;
> > +			interrupt-parent = <&plic>;
> > +			interrupts = <20>;
> > +		};
> 
> > +
> > +		ethernet: ethernet@38000000 {
> > +			compatible = "snps,dwmac", "snps,dwmac-5.10a";
> 
> Surprised this passes dtbs_check. Same here, you need a specific
> compatible.
> 
> > +			reg = <0x00 0x38000000 0x00 0x1000000>;
> > +			clocks = <&csr_clk>;
> > +			clock-names = "stmmaceth";
> > +			interrupt-parent = <&plic>;
> > +			interrupts = <84>;
> > +			interrupt-names = "macirq";
> > +			local-mac-address = [ff ff ff ff ff ff];
> > +			max-speed = <1000>;
> > +			phy-mode = "rgmii-id";
> > +			snps,txpbl = <8>;
> > +			snps,rxpbl = <8>;
> > +		};
> > +
> > +		dmac: dma-controller@39000000 {
> > +			compatible = "snps,axi-dma-1.01a";
> 
> Same thing here, I'd like to see a device specific compatible too.
> 

Got it. I’ll add device-specific compatible strings for the relevant
peripherals and update the corresponding dt-bindings in v2, including
clint, spi, i2c, ethernet, and the dma-controller.

> > +			reg = <0x0 0x39000000 0x0 0x400>;
> > +			clocks = <&device_clk>, <&device_clk>;
> 
> This kind of thing is what makes me think that you're over simplifying
> your clock tree. Sure, maybe you do use the same clock here for both
> ports, but it's suspect.
>

Thanks for the review. I’ll re-examine the clock topology to avoid
oversimplification and ensure the DT matches the actual hardware in v2.
 
> Cheers,
> Conor.
> 
> > +			clock-names = "core-clk", "cfgr-clk";
> > +			#dma-cells = <1>;
> > +			dma-channels = <8>;
> > +			interrupt-parent = <&plic>;
> > +			interrupts = <152>;
> > +			snps,dma-masters = <1>;
> > +			snps,data-width = <4>;
> > +			snps,block-size = <512 512 512 512 512 512 512 512>;
> > +			snps,priority = <0 1 2 3 4 5 6 7>;
> > +			snps,axi-max-burst-len = <256>;
> > +		};
> > +	};
> > +};
> > 
> > -- 
> > 2.34.1
> > 

Best Regards,
Jia Wang



  reply	other threads:[~2026-05-20  2:51 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  1:17 [PATCH 0/9] riscv: ultrarisc: add DP1000 SoC DT and pinctrl support Jia Wang via B4 Relay
2026-05-15  1:17 ` [PATCH 1/9] dt-bindings: vendor-prefixes: add Rongda Jia Wang via B4 Relay
2026-05-15  1:20   ` sashiko-bot
2026-05-15  1:25     ` Jia Wang
2026-05-21 20:51   ` Krzysztof Kozlowski
2026-05-26  7:12     ` Jia Wang
2026-05-15  1:17 ` [PATCH 2/9] dt-bindings: riscv: cpus: Add UltraRISC CP100 compatible Jia Wang via B4 Relay
2026-05-15 10:06   ` Conor Dooley
2026-05-15  1:17 ` [PATCH 3/9] dt-bindings: riscv: Add UltraRISC DP1000 bindings Jia Wang via B4 Relay
2026-05-15 10:08   ` Conor Dooley
2026-05-18  3:06     ` Jia Wang
2026-05-15  1:18 ` [PATCH 4/9] dt-bindings: pinctrl: Add UltraRISC DP1000 pinctrl bindings Jia Wang via B4 Relay
2026-05-15  1:49   ` sashiko-bot
2026-05-15  8:43     ` Jia Wang
2026-05-15 10:12   ` Conor Dooley
2026-05-18  6:03     ` Jia Wang
2026-05-21 20:56   ` Krzysztof Kozlowski
2026-05-27  1:34     ` Jia Wang
2026-05-25  9:23   ` Linus Walleij
2026-05-27  1:37     ` Jia Wang
2026-05-15  1:18 ` [PATCH 5/9] riscv: dts: ultrarisc: Add initial device tree for UltraRISC DP1000 Jia Wang via B4 Relay
2026-05-15  2:02   ` sashiko-bot
2026-05-19  6:55     ` Jia Wang
2026-05-15 10:26   ` Conor Dooley
2026-05-20  2:51     ` Jia Wang [this message]
2026-05-21 21:05   ` Krzysztof Kozlowski
2026-05-27  7:04     ` Jia Wang
2026-05-15  1:18 ` [PATCH 6/9] pinctrl: ultrarisc: Add UltraRISC DP1000 pinctrl driver Jia Wang via B4 Relay
2026-05-15  2:28   ` sashiko-bot
2026-05-20  7:15     ` Jia Wang
2026-05-21 21:09   ` Krzysztof Kozlowski
2026-05-27  7:07     ` Jia Wang
2026-05-25  9:28   ` Linus Walleij
2026-05-25 10:10     ` Conor Dooley
2026-05-28  7:46       ` Jia Wang
2026-05-28  8:55         ` Conor Dooley
2026-05-29  5:43           ` Jia Wang
2026-05-27  7:28     ` Jia Wang
2026-05-15  1:18 ` [PATCH 7/9] riscv: dts: ultrarisc: add Rongda M0 board device tree Jia Wang via B4 Relay
2026-05-15  2:37   ` sashiko-bot
2026-05-20  8:26     ` Jia Wang
2026-05-15 10:28   ` Conor Dooley
2026-05-20  8:40     ` Jia Wang
2026-05-21 20:59   ` Krzysztof Kozlowski
2026-05-28  8:02     ` Jia Wang
2026-05-15  1:18 ` [PATCH 8/9] riscv: dts: ultrarisc: add Milk-V Titan " Jia Wang via B4 Relay
2026-05-15  2:50   ` sashiko-bot
2026-05-20  9:39     ` Jia Wang
2026-05-15  1:18 ` [PATCH 9/9] riscv: defconfig: enable ARCH_ULTRARISC Jia Wang via B4 Relay
2026-05-15  2:59   ` sashiko-bot
2026-05-20  9:49     ` Jia Wang
2026-05-21 20:57   ` Krzysztof Kozlowski
2026-05-28  8:05     ` Jia Wang
2026-07-08 17:38       ` Paul Walmsley
2026-05-15 10:05 ` [PATCH 0/9] riscv: ultrarisc: add DP1000 SoC DT and pinctrl support Conor Dooley
2026-05-21  9:52   ` Jia Wang
2026-05-21 10:23     ` Conor Dooley
2026-05-22  1:41       ` Jia Wang
2026-08-03 10:05 ` Igor Sakulin

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=177924548998.823562.8301642486475031179.b4-reply@b4 \
    --to=wangjia@ultrarisc.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=palmer@sifive.com \
    --cc=paul.walmsley@sifive.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=samuel.holland@sifive.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