From: Quentin Schulz <quentin.schulz@cherry.de>
To: Hsun Lai <i@chainsx.cn>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: heiko@sntech.de, andrew@lunn.ch, inindev@gmail.com,
jonas@kwiboo.se, sfr@canb.auug.org.au,
nicolas.frattaroli@collabora.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, krzysztof.kozlowski@linaro.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v4 1/2] dt-bindings: arm: rockchip: Add Firefly ROC-RK3588S-PC
Date: Mon, 19 May 2025 12:20:08 +0200 [thread overview]
Message-ID: <9b215ab9-cdb5-4567-9e4d-97ee4fdb65aa@cherry.de> (raw)
In-Reply-To: <20250519075432.2239713-2-i@chainsx.cn>
Hi Hsun Lai,
On 5/19/25 9:54 AM, Hsun Lai wrote:
> [You don't often get email from i@chainsx.cn. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> This documents Firefly ROC-RK3588S-PC which is a SBC based on RK3588S SoC.
>
> Link: https://wiki.t-firefly.com/en/Station-M3/index.html
>
> Signed-off-by: Hsun Lai <i@chainsx.cn>
> ---
>
> (no changes since v1)
>
> Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
> index 115c3ca43..701d68aca 100644
> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
> @@ -258,6 +258,11 @@ properties:
> - const: firefly,rk3566-roc-pc
> - const: rockchip,rk3566
>
> + - description: Firefly Station M3
> + items:
> + - const: firefly,rk3588s-roc-pc
Interesting that the product seems to have two names :)
But considering the other Firefly RK35xx products do the same, I guess
it is fine?
So:
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Would you know what the actual differences are? For the Station M2 they
say "Based on ROC-RK3566-PC" which may indicate there are some
additional things or changes? Same for the Station P2: "Based on
ROC-RK3568-PC".
Thanks!
Quentin
next prev parent reply other threads:[~2025-05-19 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 7:54 [PATCH v4 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC Hsun Lai
2025-05-19 7:54 ` [PATCH v4 1/2] dt-bindings: arm: rockchip: Add Firefly ROC-RK3588S-PC Hsun Lai
2025-05-19 10:20 ` Quentin Schulz [this message]
2025-05-20 2:12 ` [v3,1/3] dt-bindings: vendor-prefixes: Add SakuraPi prefix Hsun Lai
2025-05-19 7:54 ` [PATCH v4 2/2] arm64: dts: rockchip: add DTs for Firefly ROC-RK3588S-PC Hsun Lai
2025-05-23 7:00 ` Chukun Pan
2025-05-23 7:12 ` Krzysztof Kozlowski
2025-05-23 10:26 ` Heiko Stübner
2025-05-19 13:01 ` [PATCH v4 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC Rob Herring (Arm)
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=9b215ab9-cdb5-4567-9e4d-97ee4fdb65aa@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=i@chainsx.cn \
--cc=inindev@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nicolas.frattaroli@collabora.com \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
/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