From: Conor Dooley <conor@kernel.org>
To: Changhuang Liang <changhuang.liang@starfivetech.com>
Cc: Thomas Gleixner <tglx@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Samuel Holland <samuel.holland@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Yixun Lan <dlan@kernel.org>,
Joel Stanley <jms@oss.tenstorrent.com>,
Drew Fustini <dfustini@oss.tenstorrent.com>,
Darshan Prajapati <darshan.prajapati@einfochips.com>,
Guodong Xu <guodong@riscstar.com>,
Michal Simek <michal.simek@amd.com>,
Junhui Liu <junhui.liu@pigmoral.tech>,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
E Shattow <e@freeshell.de>, Icenowy Zheng <uwu@icenowy.me>,
Anup Patel <anup@brainfault.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org,
Ji Sheng Teoh <jisheng.teoh@starfivetech.com>,
Hal Feng <hal.feng@starfivetech.com>,
Ley Foon Tan <leyfoon.tan@starfivetech.com>,
Michael Zhu <michael.zhu@starfivetech.com>
Subject: Re: [PATCH v1 5/5] riscv: dts: starfive: jhb100: Add JHB100 base DT
Date: Thu, 2 Apr 2026 13:25:41 +0100 [thread overview]
Message-ID: <20260402-shakable-hefty-0164a042b748@spud> (raw)
In-Reply-To: <20260402084019.440708-6-changhuang.liang@starfivetech.com>
[-- Attachment #1: Type: text/plain, Size: 5222 bytes --]
On Thu, Apr 02, 2026 at 01:40:19AM -0700, Changhuang Liang wrote:
> From: Ley Foon Tan <leyfoon.tan@starfivetech.com>
>
> Add JHB100 base dtsi and dts. Consist of 4 Dubhe-70 cores, CLINT, PLIC,
> PMU, UART and 1GB DDR.
>
> Signed-off-by: Ley Foon Tan <leyfoon.tan@starfivetech.com>
> Signed-off-by: Changhuang Liang <changhuang.liang@starfivetech.com>
> ---
> MAINTAINERS | 6 +
> arch/riscv/boot/dts/starfive/Makefile | 2 +
> .../boot/dts/starfive/jhb100-evb1-eth.dts | 6 +
> arch/riscv/boot/dts/starfive/jhb100-evb1.dtsi | 32 ++
> arch/riscv/boot/dts/starfive/jhb100.dtsi | 326 ++++++++++++++++++
> 5 files changed, 372 insertions(+)
> create mode 100644 arch/riscv/boot/dts/starfive/jhb100-evb1-eth.dts
> create mode 100644 arch/riscv/boot/dts/starfive/jhb100-evb1.dtsi
> create mode 100644 arch/riscv/boot/dts/starfive/jhb100.dtsi
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7d10988cbc62..b1892a480c31 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -25306,6 +25306,12 @@ S: Supported
> F: Documentation/devicetree/bindings/interrupt-controller/starfive,jh8100-intc.yaml
> F: drivers/irqchip/irq-starfive-jh8100-intc.c
>
> +STARFIVE JHB100 DEVICETREES
> +M: Changhuang Liang <changhuang.liang@starfivetech.com>
> +L: linux-riscv@lists.infradead.org
> +S: Maintained
Supported, no?
> +F: arch/riscv/boot/dts/starfive/jhb100*
> +
> STATIC BRANCH/CALL
> M: Peter Zijlstra <peterz@infradead.org>
> M: Josh Poimboeuf <jpoimboe@kernel.org>
> diff --git a/arch/riscv/boot/dts/starfive/Makefile b/arch/riscv/boot/dts/starfive/Makefile
> index 3dd1f05283f7..7cdb75788053 100644
> --- a/arch/riscv/boot/dts/starfive/Makefile
> +++ b/arch/riscv/boot/dts/starfive/Makefile
> @@ -18,3 +18,5 @@ dtb-$(CONFIG_ARCH_STARFIVE) += jh7110-starfive-visionfive-2-lite.dtb
> dtb-$(CONFIG_ARCH_STARFIVE) += jh7110-starfive-visionfive-2-lite-emmc.dtb
> dtb-$(CONFIG_ARCH_STARFIVE) += jh7110-starfive-visionfive-2-v1.2a.dtb
> dtb-$(CONFIG_ARCH_STARFIVE) += jh7110-starfive-visionfive-2-v1.3b.dtb
> +
> +dtb-$(CONFIG_ARCH_STARFIVE) += jhb100-evb1-eth.dtb
> diff --git a/arch/riscv/boot/dts/starfive/jhb100-evb1-eth.dts b/arch/riscv/boot/dts/starfive/jhb100-evb1-eth.dts
> new file mode 100644
> index 000000000000..62cd046e1224
> --- /dev/null
> +++ b/arch/riscv/boot/dts/starfive/jhb100-evb1-eth.dts
> @@ -0,0 +1,6 @@
> +// SPDX-License-Identifier: GPL-2.0 OR MIT
> +/*
> + * Copyright (c) 2024-2026 StarFive Technology Co., Ltd.
> + */
> +
> +#include "jhb100-evb1.dtsi"
What is the point of this file? Is this the base-board?
Shouldn't it have a specific compatible?
Can the SoM be used without a base board? I've got no info about this
board appearing on google, do you even have pictures of it or any
documentation?
I see this
https://www.starfivetech.com/en/index.php?s=hardware&c=show&id=22
and
https://www.starfivetech.com/en/index.php?s=hardware&c=show&id=23
but the former doesn't look like it needs a base-board and the latter is
called "evb3", so is not what's here?
Not got enough info to really do any kind of review here.
> diff --git a/arch/riscv/boot/dts/starfive/jhb100-evb1.dtsi b/arch/riscv/boot/dts/starfive/jhb100-evb1.dtsi
> new file mode 100644
> index 000000000000..462b6fb7953b
> --- /dev/null
> +++ b/arch/riscv/boot/dts/starfive/jhb100-evb1.dtsi
> @@ -0,0 +1,32 @@
> +// SPDX-License-Identifier: GPL-2.0 OR MIT
> +/*
> + * Copyright (c) 2024-2026 StarFive Technology Co., Ltd.
> + */
> +
> +#include "jhb100.dtsi"
> +
> +/ {
> + model = "StarFive JHB100 EVB-1";
> + compatible = "starfive,jhb100-evb1", "starfive,jhb100";
> +
> + aliases {
> + serial6 = &uart6;
> + };
> +
> + chosen {
> + stdout-path = "serial6:115200n8";
> + };
> +
> + cpus {
> + timebase-frequency = <5000000>;
> + };
> +
> + memory@40000000 {
> + device_type = "memory";
> + reg = <0x0 0x40000000 0x0 0x40000000>; /* 1GB */
> + };
> +};
> +
> +&uart6 {
> + status = "okay";
> +};
> + cpu2: cpu@2 {
> + compatible = "starfive,dubhe-70", "riscv";
> + riscv,isa = "rv64imafdcbh";
> + riscv,isa-base = "rv64i";
> + riscv,isa-extensions = "i", "m", "a", "f", "d", "c", "b", "h", "zba", "zbb",
> + "zbc", "zbs", "zicbom", "zicbop", "zicboz", "zicntr",
> + "zicond", "zicsr", "zifencei", "zihintpause",
> + "zihpm", "svinval", "svnapot", "sscofpmf";
> + riscv,cbom-block-size = <64>;
> + riscv,cbop-block-size = <64>;
> + riscv,cboz-block-size = <64>;
> + d-cache-block-size = <64>;
> + d-cache-sets = <512>;
> + d-cache-size = <32768>;
> + d-tlb-sets = <1>;
> + d-tlb-size = <16>;
> + device_type = "cpu";
> + i-cache-block-size = <64>;
> + i-cache-sets = <512>;
> + i-cache-size = <32768>;
> + i-tlb-sets = <1>;
> + i-tlb-size = <24>;
> + mmu-type = "riscv,sv48";
> + next-level-cache = <&l2c2>;
> + reg = <0x2>;
reg after compatible please.
> + tlb-split;
> +
> + cpu2_intc: interrupt-controller {
> + compatible = "riscv,cpu-intc";
> + interrupt-controller;
> + #interrupt-cells = <1>;
> + };
> + };
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-04-02 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 8:40 [PATCH v1 0/5] Initial device tree support for StarFive JHB100 SoC Changhuang Liang
2026-04-02 8:40 ` [PATCH v1 1/5] dt-bindings: riscv: Add StarFive Dubhe-70 compatibles Changhuang Liang
2026-04-02 8:40 ` [PATCH v1 2/5] dt-bindings: timer: Add StarFive JHB100 clint Changhuang Liang
2026-04-02 8:40 ` [PATCH v1 3/5] dt-bindings: interrupt-controller: Add StarFive JHB100 plic Changhuang Liang
2026-04-02 8:40 ` [PATCH v1 4/5] dt-bindings: riscv: Add StarFive JHB100 SoC Changhuang Liang
2026-04-02 8:40 ` [PATCH v1 5/5] riscv: dts: starfive: jhb100: Add JHB100 base DT Changhuang Liang
2026-04-02 12:25 ` Conor Dooley [this message]
2026-04-03 3:06 ` Changhuang Liang
2026-04-03 8:49 ` Conor Dooley
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=20260402-shakable-hefty-0164a042b748@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@kernel.org \
--cc=darshan.prajapati@einfochips.com \
--cc=devicetree@vger.kernel.org \
--cc=dfustini@oss.tenstorrent.com \
--cc=dlan@kernel.org \
--cc=e@freeshell.de \
--cc=guodong@riscstar.com \
--cc=hal.feng@starfivetech.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=jisheng.teoh@starfivetech.com \
--cc=jms@oss.tenstorrent.com \
--cc=junhui.liu@pigmoral.tech \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michael.zhu@starfivetech.com \
--cc=michal.simek@amd.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@kernel.org \
--cc=uwu@icenowy.me \
/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