From: Christopher Obbard <chris.obbard@collabora.com>
To: linux-rockchip@lists.infradead.org
Cc: kernel@collabora.com,
Christopher Obbard <chris.obbard@collabora.com>,
Andrew Lunn <andrew@lunn.ch>, Andy Yan <andyshrk@163.com>,
Brian Norris <briannorris@chromium.org>,
Chris Morgan <macromorgan@hotmail.com>,
Conor Dooley <conor+dt@kernel.org>,
FUKAUMI Naoki <naoki@radxa.com>, Heiko Stuebner <heiko@sntech.de>,
Jagan Teki <jagan@amarulasolutions.com>,
Jagan Teki <jagan@edgeble.ai>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maya Matuszczyk <maccraft123mc@gmail.com>,
Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Tianling Shen <cnsztl@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] Add support for Radxa ROCK 4SE
Date: Mon, 10 Jul 2023 12:50:22 +0100 [thread overview]
Message-ID: <20230710115025.507439-1-chris.obbard@collabora.com> (raw)
Add support for the RK3399T-based Radxa ROCK 4SE board. This board offers
similar peripherals and form-factor to the ROCK Pi 4B but uses the
cost-optimised RK3399T processor (which has different a OPP table but
otherwise minimal changes) and some other minor hardware changes between
the Rock Pi 4B (described in the devicetree).
The first patch moves the RK3399 OPP table from the generic Radxa ROCK
Pi 4 dtsi into board-specific devicetree files, in preparation for the
ROCK 4SE devicetree file (in later patches).
The second patch adds the devicetree binding documentation for the Radxa
ROCK 4SE.
The third patch adds the board-specific devicetree file for the Radxa ROCK
4SE.
Changes in v2:
- Add Krzysztof Kozlowski's Acked-by tag.
- Set proper interrupt type for brcmf.
Christopher Obbard (3):
arm64: dts: rockchip: Move OPP table from ROCK Pi 4 dtsi
dt-bindings: arm: rockchip: Add Radxa ROCK 4SE
arm64: dts: rockchip: Add Radxa ROCK 4SE
.../devicetree/bindings/arm/rockchip.yaml | 5 ++
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../boot/dts/rockchip/rk3399-rock-4se.dts | 65 +++++++++++++++++++
.../boot/dts/rockchip/rk3399-rock-pi-4.dtsi | 1 -
.../boot/dts/rockchip/rk3399-rock-pi-4a.dts | 1 +
.../boot/dts/rockchip/rk3399-rock-pi-4b.dts | 1 +
.../boot/dts/rockchip/rk3399-rock-pi-4c.dts | 1 +
7 files changed, 74 insertions(+), 1 deletion(-)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-rock-4se.dts
--
2.40.1
next reply other threads:[~2023-07-10 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 11:50 Christopher Obbard [this message]
2023-07-10 11:50 ` [PATCH v2 1/3] arm64: dts: rockchip: Move OPP table from ROCK Pi 4 dtsi Christopher Obbard
2023-07-10 11:50 ` [PATCH v2 2/3] dt-bindings: arm: rockchip: Add Radxa ROCK 4SE Christopher Obbard
2023-07-10 11:50 ` [PATCH v2 3/3] arm64: dts: " Christopher Obbard
2023-07-11 14:48 ` [PATCH v2 0/3] Add support for " Heiko Stuebner
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=20230710115025.507439-1-chris.obbard@collabora.com \
--to=chris.obbard@collabora.com \
--cc=andrew@lunn.ch \
--cc=andyshrk@163.com \
--cc=briannorris@chromium.org \
--cc=cnsztl@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frattaroli.nicolas@gmail.com \
--cc=heiko@sntech.de \
--cc=jagan@amarulasolutions.com \
--cc=jagan@edgeble.ai \
--cc=kernel@collabora.com \
--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=maccraft123mc@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=naoki@radxa.com \
--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).