From: sashiko-bot@kernel.org
To: 安容 <HystericalDragons@proton.me>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v7 3/3] arm64: dts: rockchip: Add devicetree for the FriendlyElec NanoPi R28S
Date: Sat, 19 Sep 2026 10:36:02 +0000 [thread overview]
Message-ID: <20260919103602.E84DA1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260919-r28s-upstream-v7-3-e80a6f8ef521@proton.me>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dts: unused pinctrl definitions for wifi and bluetooth pins
--
commit 745cf672aded254ac32cf444a084e38df95384e1
Author: 安容 <HystericalDragons@proton.me>
arm64: dts: rockchip: Add devicetree for the FriendlyElec NanoPi R28S
This commit adds devicetree support for the NanoPi R28S router board based on
the RK3528 SoC. It shares most of its design with the NanoPi Zero2 and enables
various peripherals including SDIO, UART, and networking interfaces.
> diff --git a/arch/arm64/boot/dts/rockchip/rk3528-nanopi-r28s.dts b/arch/arm64/boot/dts/rockchip/rk3528-nanopi-r28s.dts
> new file mode 100644
> index 0000000000000..294b66f60e47b
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3528-nanopi-r28s.dts
[ ... ]
> +&pinctrl {
> + bluetooth {
> + bt_wake_host: bt-wake-host {
> + rockchip,pins = <1 RK_PB5 RK_FUNC_GPIO &pcfg_pull_down>;
> + };
> +
> + host_wake_bt: host-wake-bt {
> + rockchip,pins = <1 RK_PB4 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> + };
[Severity: Low]
Are these bluetooth pinctrl nodes intended to be used or configured as hogs?
They are defined here but appear to never be referenced by any device node.
Without an explicit reference, such as a pinctrl-0 property on a device or
a hog definition, the configured pull states will not be applied.
[ ... ]
> + wifi {
> + host_wake_wl: host-wake-wl {
> + rockchip,pins = <1 RK_PA6 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + pwr_wf: pwr-wf {
> + rockchip,pins = <1 RK_PC2 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + wl_wake_host: wl-wake-host {
> + rockchip,pins = <1 RK_PA7 RK_FUNC_GPIO &pcfg_pull_down>;
> + };
> + };
> +};
[Severity: Low]
Similarly, are the host_wake_wl and wl_wake_host nodes meant to be referenced
somewhere? Like the bluetooth pins, they are defined but do not seem to be
used by any device or set up as a hog, meaning their pull states will not take
effect.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260919-r28s-upstream-v7-0-e80a6f8ef521@proton.me?part=3
next prev parent reply other threads:[~2026-09-19 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 10:28 [PATCH v7 0/3] arm64: dts: rockchip: Add FriendlyElec NanoPi R28S 安容 via B4 Relay
2026-09-19 10:28 ` [PATCH v7 1/3] dt-bindings: arm: " 安容 via B4 Relay
2026-09-19 10:28 ` [PATCH v7 2/3] arm64: dts: rockchip: Split out the common NanoPi RK3528 parts 安容 via B4 Relay
2026-09-19 10:28 ` [PATCH v7 3/3] arm64: dts: rockchip: Add devicetree for the FriendlyElec NanoPi R28S 安容 via B4 Relay
2026-09-19 10:36 ` sashiko-bot [this message]
2026-09-30 18:49 ` [PATCH v7 0/3] arm64: dts: rockchip: Add " Heiko Stuebner
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=20260919103602.E84DA1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=HystericalDragons@proton.me \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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