From: sashiko-bot@kernel.org
To: "Chukun Pan" <amadeus@jmu.edu.cn>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: rockchip: Add MangoPi M28K
Date: Sat, 01 Aug 2026 08:13:12 +0000 [thread overview]
Message-ID: <20260801081312.E546B1F00AC4@smtp.kernel.org> (raw)
In-Reply-To: <20260801080018.3220034-3-amadeus@jmu.edu.cn>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Unused pinctrl definition `wifi_wake_host_h` in device tree.
--
--- Patch [2]: [PATCH v2 2/2] arm64: dts: rockchip: Add MangoPi M28K ---
commit 5c35fa24023c282c8d840265113ad72db0aa147d
Author: Chukun Pan <amadeus@jmu.edu.cn>
arm64: dts: rockchip: Add MangoPi M28K
This commit adds device tree support for the MangoPi M28K development
board based on the Rockchip RK3528 SoC. It details various interfaces
such as USB, Ethernet, MMC, and regulators.
Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3528-mangopi-m28k.dts b/arch/arm64/boot/dts/rockchip/rk3528-mangopi-m28k.dts
> new file mode 100644
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3528-mangopi-m28k.dts
[ ... ]
> + wifi {
> + wifi_reg_on_h: wifi-reg-on-h {
> + rockchip,pins = <1 RK_PA6 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + wifi_wake_host_h: wifi-wake-host-h {
> + rockchip,pins = <1 RK_PA7 RK_FUNC_GPIO &pcfg_pull_down>;
> + };
[Severity: Low]
Is this wifi_wake_host_h pinctrl intentionally left orphaned?
It doesn't seem to be referenced by any device node in this file. It looks
like the AIC8800 WiFi module doesn't have a child node under &sdio0 (perhaps
due to lacking an upstream binding), which makes this pinctrl configuration
unused.
Would it be better to omit this pin configuration until the corresponding
WiFi node that uses it can be added to the device tree?
> + };
> +};
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260801080018.3220034-1-amadeus@jmu.edu.cn?part=2
prev parent reply other threads:[~2026-08-01 8:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 8:00 [PATCH v2 0/2] arm64: dts: rockchip: Add MangoPi M28K Chukun Pan
2026-08-01 8:00 ` [PATCH v2 1/2] dt-bindings: arm: " Chukun Pan
2026-08-03 9:34 ` Krzysztof Kozlowski
2026-08-04 6:40 ` Chukun Pan
2026-08-04 6:45 ` Krzysztof Kozlowski
2026-08-04 11:50 ` Chukun Pan
2026-08-05 7:22 ` Krzysztof Kozlowski
2026-08-01 8:00 ` [PATCH v2 2/2] arm64: dts: " Chukun Pan
2026-08-01 8:13 ` sashiko-bot [this message]
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=20260801081312.E546B1F00AC4@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=amadeus@jmu.edu.cn \
--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