From: Dmitry Yashin <dmt.yashin@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Dmitry Yashin <dmt.yashin@gmail.com>
Subject: [PATCH 0/3] Add Forlinx OK3588-C
Date: Fri, 15 Mar 2024 19:18:04 +0500 [thread overview]
Message-ID: <cover.1710506373.git.dmt.yashin@gmail.com> (raw)
This series add support for Forlinx RK3588 based SoM and carrier board.
Devicetree split into .dtsi (FET3588-C SoM) and .dts (OK3588-C Board).
Dmitry Yashin (3):
dt-bindings: arm: rockchip: add Forlinx FET3588-C
arm64: dts: rockchip: add Forlinx FET3588-C
arm64: dts: rockchip: add Forlinx OK3588-C
.../devicetree/bindings/arm/rockchip.yaml | 7 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../rockchip/rk3588-forlinx-fet3588-c.dtsi | 556 ++++++++++++++++++
.../boot/dts/rockchip/rk3588-ok3588-c.dts | 390 ++++++++++++
4 files changed, 954 insertions(+)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3588-forlinx-fet3588-c.dtsi
create mode 100644 arch/arm64/boot/dts/rockchip/rk3588-ok3588-c.dts
--
2.44.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-03-15 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 14:18 Dmitry Yashin [this message]
2024-03-15 14:18 ` [PATCH 1/3] dt-bindings: arm: rockchip: add Forlinx FET3588-C Dmitry Yashin
2024-03-17 14:53 ` Conor Dooley
2024-03-15 14:18 ` [PATCH 2/3] arm64: dts: " Dmitry Yashin
2024-03-15 14:18 ` [PATCH 3/3] arm64: dts: rockchip: add Forlinx OK3588-C Dmitry Yashin
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=cover.1710506373.git.dmt.yashin@gmail.com \
--to=dmt.yashin@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).