From: Jonas Karlman <jonas@kwiboo.se>
To: HystericalDragons@proton.me
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Chukun Pan <amadeus@jmu.edu.cn>,
jensen <jensenhuang@friendlyarm.com>,
Andrey Korshunov <razor1702@gmail.com>,
Diederik de Haas <diederik@cknow-tech.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v6 1/3] dt-bindings: arm: rockchip: Add FriendlyElec NanoPi R28S
Date: Sat, 19 Sep 2026 11:38:11 +0200 [thread overview]
Message-ID: <a558ca88-6981-428c-943d-6fd904d8ef2b@kwiboo.se> (raw)
In-Reply-To: <20260914-r28s-upstream-v6-1-ea9edd75c126@proton.me>
Hi,
On 9/14/2026 3:35 PM, 安容 via B4 Relay wrote:
> From: 安容 <HystericalDragons@proton.me>
>
> The NanoPi R28S is a dual gigabit Ethernet router board based on the
> Rockchip RK3528 SoC. It shares its base devicetree with the NanoPi
> Zero2, so list both boards in a single entry.
>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: 安容 <HystericalDragons@proton.me>
> ---
> Documentation/devicetree/bindings/arm/rockchip.yaml | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
> index 81744fbee9..dc04946db0 100644
> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
> @@ -347,6 +347,13 @@ properties:
> - friendlyarm,nanopi-r2s-plus
> - const: rockchip,rk3328
>
> + - description: FriendlyElec NanoPi R28S/Zero2
Maybe name this something like 'FriendlyElec NanoPi RK3528 series boards'
to closer match other NanoPi/PC entries? That would also prevents
re-ordering once more when NanoPi NEO3 Plus is added.
Regards,
Jonas
> + items:
> + - enum:
> + - friendlyarm,nanopi-r28s
> + - friendlyarm,nanopi-zero2
> + - const: rockchip,rk3528
> +
> - description: FriendlyElec NanoPi R3S
> items:
> - const: friendlyarm,nanopi-r3s
> @@ -388,11 +395,6 @@ properties:
> - const: friendlyarm,nanopi-r76s
> - const: rockchip,rk3576
>
> - - description: FriendlyElec NanoPi Zero2
> - items:
> - - const: friendlyarm,nanopi-zero2
> - - const: rockchip,rk3528
> -
> - description: FriendlyElec NanoPC T6 series boards
> items:
> - enum:
>
next prev parent reply other threads:[~2026-09-19 9:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 13:35 [PATCH v6 0/3] arm64: dts: rockchip: Add FriendlyElec NanoPi R28S 安容 via B4 Relay
2026-09-14 13:35 ` [PATCH v6 1/3] dt-bindings: arm: " 安容 via B4 Relay
2026-09-19 9:38 ` Jonas Karlman [this message]
2026-09-14 13:35 ` [PATCH v6 2/3] arm64: dts: rockchip: Split out the common NanoPi RK3528 parts 安容 via B4 Relay
2026-09-19 9:39 ` Jonas Karlman
2026-09-14 13:35 ` [PATCH v6 3/3] arm64: dts: rockchip: Add devicetree for the FriendlyElec NanoPi R28S 安容 via B4 Relay
2026-09-19 9:40 ` Jonas Karlman
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=a558ca88-6981-428c-943d-6fd904d8ef2b@kwiboo.se \
--to=jonas@kwiboo.se \
--cc=HystericalDragons@proton.me \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=diederik@cknow-tech.com \
--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=razor1702@gmail.com \
--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