From: efectn@6tel.net
To: linux-rockchip@lists.infradead.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
heiko@sntech.de, sebastian.reichel@collabora.com,
jonas@kwiboo.se, Muhammed Efe Cetin <efectn@protonmail.com>
Subject: [PATCH 0/3] Add Support for NanoPi R6S and R6C boards
Date: Fri, 15 Dec 2023 16:55:20 +0300 [thread overview]
Message-ID: <cover.1702647349.git.efectn@protonmail.com> (raw)
From: Muhammed Efe Cetin <efectn@protonmail.com>
Hi, this series add support for RK3588S based NanoPi R6S and R6C boards.
Muhammed Efe Cetin (3):
dt-bindings: arm: rockchip: Add NanoPi R6 series boards
arm64: dts: rockchip: Add support for NanoPi R6S
arm64: dts: rockchip: Add support for NanoPi R6C
.../devicetree/bindings/arm/rockchip.yaml | 7 +
arch/arm64/boot/dts/rockchip/Makefile | 2 +
.../boot/dts/rockchip/rk3588s-nanopi-r6c.dts | 14 +
.../boot/dts/rockchip/rk3588s-nanopi-r6s.dts | 755 ++++++++++++++++++
4 files changed, 778 insertions(+)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3588s-nanopi-r6c.dts
create mode 100644 arch/arm64/boot/dts/rockchip/rk3588s-nanopi-r6s.dts
--
2.43.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:[~2023-12-15 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 13:55 efectn [this message]
2023-12-15 13:55 ` [PATCH 1/3] dt-bindings: arm: rockchip: Add NanoPi R6 series boards efectn
2023-12-15 20:13 ` Rob Herring
2023-12-15 13:55 ` [PATCH 2/3] arm64: dts: rockchip: Add support for NanoPi R6S efectn
2023-12-18 0:25 ` John Clark
2023-12-18 7:24 ` Krzysztof Kozlowski
2023-12-18 7:24 ` Krzysztof Kozlowski
2023-12-15 13:55 ` [PATCH 3/3] arm64: dts: rockchip: Add support for NanoPi R6C efectn
2023-12-18 7:24 ` Krzysztof Kozlowski
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.1702647349.git.efectn@protonmail.com \
--to=efectn@6tel.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=efectn@protonmail.com \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--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 \
--cc=sebastian.reichel@collabora.com \
/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).