From: "Rob Herring (Arm)" <robh@kernel.org>
To: Hsun Lai <i@chainsx.cn>
Cc: sfr@canb.auug.org.au, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
heiko@sntech.de
Subject: Re: [PATCH v3 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC
Date: Sat, 17 May 2025 08:18:25 -0500 [thread overview]
Message-ID: <174748776864.930436.6066844378633879191.robh@kernel.org> (raw)
In-Reply-To: <20250516012402.580468-1-i@chainsx.cn>
On Fri, 16 May 2025 09:24:00 +0800, Hsun Lai wrote:
> This series add support for Firefly Station-M3/ROC-RK3588S-PC.
>
> Info of device can be found at:
> https://wiki.t-firefly.com/en/Station-M3/index.html
>
> Changes in v3:
> - Update the name of leds
> - Add more cpu nodes
> - Update mdio compatible
> - Fix the order in the node
> - Add the default serial port(uart2)
>
> Changes in v2:
> - Fix rgmii delays
>
> Changes in v1:
> - Add support for Firefly ROC-RK3588S-PC
>
> Hsun Lai (2):
> dt-bindings: arm: rockchip: Add Firefly ROC-RK3588S-PC
> arm64: dts: rockchip: add DTs for Firefly ROC-RK3588S-PC
>
> .../devicetree/bindings/arm/rockchip.yaml | 5 +
> arch/arm64/boot/dts/rockchip/Makefile | 1 +
> .../boot/dts/rockchip/rk3588s-roc-pc.dts | 926 ++++++++++++++++++
> 3 files changed, 932 insertions(+)
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3588s-roc-pc.dts
>
> --
> 2.34.1
>
>
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
This patch series was applied (using b4) to base:
Base: attempting to guess base-commit...
Base: remotes/arm-soc/rockchip/dt64-31-ge463625af7f9 (exact match)
If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)
New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/rockchip/' for 20250516012402.580468-1-i@chainsx.cn:
arch/arm64/boot/dts/rockchip/rk3588s-roc-pc.dtb: /edp@fdec0000: failed to match any schema with compatible: ['rockchip,rk3588-edp']
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-05-17 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 1:24 [PATCH v3 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC Hsun Lai
2025-05-16 1:24 ` [PATCH v3 1/2] dt-bindings: arm: rockchip: Add Firefly ROC-RK3588S-PC Hsun Lai
2025-05-16 1:24 ` [PATCH v3 2/2] arm64: dts: rockchip: add DTs for " Hsun Lai
2025-05-16 2:04 ` Jimmy Hon
2025-05-17 13:18 ` Rob Herring (Arm) [this message]
2025-05-17 18:08 ` [PATCH v3 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC Heiko Stübner
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=174748776864.930436.6066844378633879191.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=i@chainsx.cn \
--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=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