From: Jia Wang <wangjia@ultrarisc.com>
To: sashiko-reviews@lists.linux.dev
Cc: Jia Wang via B4 Relay <devnull+wangjia.ultrarisc.com@kernel.org>,
conor+dt@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 7/9] riscv: dts: ultrarisc: add Rongda M0 board device tree
Date: Wed, 20 May 2026 16:26:42 +0800 [thread overview]
Message-ID: <177926560256.943957.3878687939421695995.b4-reply@b4> (raw)
In-Reply-To: <20260515023740.9BB6FC2BCB3@smtp.kernel.org>
On 2026-05-15 02:37 +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
> - [Medium] Unused hardware blocks (PCIe controllers and UART3) are left enabled without proper configuration.
> - [Low] Board-specific power management features (`gpio-poweroff` and `gpio-restart`) are explicitly disabled.
> - [Low] Unused PCIe link pin configurations conflict with actively used I2C2 pins.
> --
>
> commit 024b81fdfc4200deef00a8435cf80efa58aed943
> Author: Jia Wang <wangjia@ultrarisc.com>
>
> riscv: dts: ultrarisc: add Rongda M0 board device tree
>
> This commit adds the device tree for the Rongda M0 mATX motherboard based
> on the UltraRISC DP1000 SoC. It configures pin controls, aliases, and
> active peripherals like I2C, SPI, UART, and Ethernet.
>
> > diff --git a/arch/riscv/boot/dts/ultrarisc/dp1000-rongda-m0-pinctrl.dtsi b/arch/riscv/boot/dts/ultrarisc/dp1000-rongda-m0-pinctrl.dtsi
> > new file mode 100644
> > index 0000000000000..101b416b10792
> > --- /dev/null
> > +++ b/arch/riscv/boot/dts/ultrarisc/dp1000-rongda-m0-pinctrl.dtsi
> > @@ -0,0 +1,85 @@
> [ ... ]
> > + i2c2_pins: i2c2-pins {
> > + pins = "PC0", "PC1";
> > + function = "func0";
> > + bias-pull-up;
> > + drive-strength = <33>;
> > + };
> [ ... ]
> > + pciex4a_link_pins: pciex4a-link-pins {
> > + pins = "PC0";
> > + function = "func1";
> > + bias-pull-down;
> > + drive-strength = <33>;
> > + };
> > +
> > + pciex4b_link_pins: pciex4b-link-pins {
> > + pins = "PC1";
> > + function = "func1";
> > + bias-pull-down;
> > + drive-strength = <33>;
> > + };
>
> Are these pciex4a_link_pins and pciex4b_link_pins configurations needed?
> They appear to use pins PC0 and PC1, which are also mapped to i2c2_pins and
> actively assigned to i2c2 below.
>
> Since these PCIe link pin configurations are unused in the board device tree
> and conflict with the active I2C pins, could they be removed?
>
Will remove the unused pciex4a/b_link_pins in v2. Thanks.
> > diff --git a/arch/riscv/boot/dts/ultrarisc/dp1000-rongda-m0.dts b/arch/riscv/boot/dts/ultrarisc/dp1000-rongda-m0.dts
> > new file mode 100644
> > index 0000000000000..6f72d60ad55e4
> > --- /dev/null
> > +++ b/arch/riscv/boot/dts/ultrarisc/dp1000-rongda-m0.dts
> > @@ -0,0 +1,111 @@
> [ ... ]
> > + aliases {
> > + serial0 = &uart0;
> > + serial1 = &uart1;
> > + serial2 = &uart2;
> > + serial3 = &uart3;
> > + };
>
> Is uart3 intended to be active on this board? It is aliased here but does
> not appear to be configured with pins or explicitly disabled.
>
> If unused hardware blocks like uart3 or the PCIe controllers are left enabled
> in the generic SoC device tree without being explicitly disabled in the board
> device tree, could probing them waste resources or expose dangling interfaces?
>
> Should unused IP blocks be explicitly marked with status = "disabled" in
> this board-level device tree?
>
uart3 is routed out on this board. I'll keep the alias and add the missing
pinctrl configuration in v2. Thanks.
> > +
> > + chosen {
> > + stdout-path = "serial0:115200n8";
> > + };
> > +
> > + gpio-poweroff {
> > + compatible = "gpio-poweroff";
> > + gpios = <&gpio_b 0 GPIO_ACTIVE_HIGH>;
> > + active-delay-ms = <100>;
> > +
> > + status = "disabled";
> > + };
> > +
> > + gpio-restart {
> > + compatible = "gpio-restart";
> > + gpios = <&gpio_b 1 GPIO_ACTIVE_HIGH>;
> > + active-delay = <100>;
> > +
> > + status = "disabled";
> > + };
>
> Should these gpio-poweroff and gpio-restart nodes be included if they are
> explicitly disabled?
>
> If the board is physically wired to support these features, could they be
> enabled by removing the status lines? If not, does it make sense to omit
> these nodes from the board file entirely?
>
The board relies on the OpenSBI SRST extension as the active reset/poweroff
mechanism, so the disabled gpio-poweroff and gpio-restart nodes are indeed
unnecessary in the board DTS.
I'll drop them in v2.
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260515-ultrarisc-pinctrl-v1-0-bf559589ea8a@ultrarisc.com?part=7
>
next prev parent reply other threads:[~2026-05-20 8:26 UTC|newest]
Thread overview: 58+ 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
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 [this message]
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
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=177926560256.943957.3878687939421695995.b4-reply@b4 \
--to=wangjia@ultrarisc.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+wangjia.ultrarisc.com@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