From: Frank Wunderlich <linux@fw-web.de>
To: linux-rockchip@lists.infradead.org
Cc: Frank Wunderlich <frank-w@public-files.de>,
Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Peter Geis <pgwipeout@gmail.com>,
Johan Jonker <jbx6244@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/3] Add BananaPi R2 Pro board
Date: Sun, 16 Jan 2022 13:49:08 +0100 [thread overview]
Message-ID: <20220116124911.65203-1-linux@fw-web.de> (raw)
From: Frank Wunderlich <frank-w@public-files.de>
This Series adds RK3568 based Bananapi R2 Board.
While testing new dts with dtbs_check we've found an issue with
mainline gmac0 node in rk3568.dtsi which breaks dtbs_check. So first
Patch fixes this problem.
Frank Wunderlich (3):
dts64: rk3568: drop pclk_xpcs from gmac0
dt-bindings: rockchip: Add BananaPi R2 Pro Board
dts64: rockchip: Add Bananapi R2 Pro
.../devicetree/bindings/arm/rockchip.yaml | 5 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../boot/dts/rockchip/rk3568-bpi-r2-pro.dts | 428 ++++++++++++++++++
arch/arm64/boot/dts/rockchip/rk3568.dtsi | 6 +-
4 files changed, 436 insertions(+), 4 deletions(-)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts
--
2.25.1
next reply other threads:[~2022-01-16 12:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 12:49 Frank Wunderlich [this message]
2022-01-16 12:49 ` [PATCH v1 1/3] dts64: rk3568: drop pclk_xpcs from gmac0 Frank Wunderlich
2022-01-17 6:54 ` Michael Riesch
2022-01-17 10:47 ` Johan Jonker
2022-01-17 11:51 ` Heiko Stübner
2022-01-17 11:59 ` Aw: " Frank Wunderlich
2022-01-17 18:26 ` Peter Geis
2022-01-17 21:05 ` Heiko Stübner
2022-01-22 14:50 ` Aw: " Frank Wunderlich
2022-01-23 13:38 ` Heiko Stuebner
2022-01-16 12:49 ` [PATCH v1 2/3] dt-bindings: rockchip: Add BananaPi R2 Pro Board Frank Wunderlich
2022-01-16 12:49 ` [PATCH v1 3/3] dts64: rockchip: Add Bananapi R2 Pro Frank Wunderlich
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=20220116124911.65203-1-linux@fw-web.de \
--to=linux@fw-web.de \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--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).