From: Chukun Pan <amadeus@jmu.edu.cn>
To: devnull+hystericaldragons.proton.me@kernel.org
Cc: HystericalDragons@proton.me, conor+dt@kernel.org,
devicetree@vger.kernel.org, heiko@sntech.de,
jensenhuang@friendlyarm.com, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh@kernel.org, Chukun Pan <amadeus@jmu.edu.cn>
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add devicetree for the FriendlyElec NanoPi R28S
Date: Mon, 7 Sep 2026 19:40:10 +0800 [thread overview]
Message-ID: <20260907114010.2166428-1-amadeus@jmu.edu.cn> (raw)
In-Reply-To: <20260905-r28s-upstream-v1-2-f68d5389269a@proton.me>
Hi,
> --- a/arch/arm64/boot/dts/rockchip/Makefile
> +++ b/arch/arm64/boot/dts/rockchip/Makefile
> +dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3528-nanopi-r28s.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3528-nanopi-zero2.dtb
This device tree has many similarities to the nanopi zero2.
Can you create a shared device tree?
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3528-nanopi-r28s.dts
https://wiki.friendlyelec.com/wiki/images/7/7c/NanoPi_R28S_2605_SCH.pdf
Please name the labels according to the schematic.
> + pinctrl-names = "default";
> + pinctrl-0 = <&user_key>;
Schematic label: GPIO4_B2_USR_BTN
> + button-reset {
> + debounce-interval = <50>;
> + gpios = <&gpio4 RK_PB2 GPIO_ACTIVE_LOW>;
> + label = "reset";
> + linux,code = <KEY_RESTART>;
label = "USER";
> + leds {
> + compatible = "gpio-leds";
> + pinctrl-names = "default";
> + pinctrl-0 = <&lan_led_g>, <&sys_led_r>, <&wan_led_g>;
Schematic label: LED1 LED2 LED_SYS
> + sdio_pwrseq: sdio-pwrseq {
> + compatible = "mmc-pwrseq-simple";
> + pinctrl-names = "default";
> + pinctrl-0 = <&wifi_enable_h>;
Schematic label: PWR_WF
> +&pcie {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pcie_reset_h>;
Schematic label: PCIE_ETH_PERSTB
prev parent reply other threads:[~2026-09-07 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 11:17 [PATCH 0/2] arm64: dts: rockchip: Add FriendlyElec NanoPi R28S 安容 via B4 Relay
2026-09-05 11:17 ` [PATCH 1/2] dt-bindings: arm: " 安容 via B4 Relay
2026-09-07 17:35 ` Conor Dooley
2026-09-05 11:17 ` [PATCH 2/2] arm64: dts: rockchip: Add devicetree for the " 安容 via B4 Relay
2026-09-07 11:40 ` Chukun Pan [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=20260907114010.2166428-1-amadeus@jmu.edu.cn \
--to=amadeus@jmu.edu.cn \
--cc=HystericalDragons@proton.me \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+hystericaldragons.proton.me@kernel.org \
--cc=heiko@sntech.de \
--cc=jensenhuang@friendlyarm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
/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