From: Andre Przywara <andre.przywara@arm.com>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: "Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Samuel Holland" <samuel@sholland.org>,
"Clément Péron" <peron.clem@gmail.com>,
"Peter Robinson" <pbrobinson@gmail.com>,
"Chen-Yu Tsai" <wens@csie.org>,
u-boot@lists.denx.de, linux-sunxi@lists.linux.dev
Subject: [PATCH 0/3] sunxi: dts: Update H3/H5/H6 devicetree from Linux
Date: Thu, 27 May 2021 01:44:35 +0100 [thread overview]
Message-ID: <20210527004438.19783-1-andre.przywara@arm.com> (raw)
This syncs the SoC .dtsi and board .dts files from the Linux 5.12 release.
For the H3 and H5 this brings us the proper RGMII modes for the boards
with Gigabit Ethernet PHYs.
The rest are smaller updates, but bring us port 0 USB support on the
H6 boards in U-Boot.
I know it's a bit late in the game, but those changes look innocent
enough to make it into the v2021.07 release still. This way we have all
64-bit boards using Linux 5.12 DTs.
Cheers,
Andre
Andre Przywara (3):
arm: dts: sunxi: h6: Update DT files
arm: dts: sunxi: h5: Update DT files
arm: dts: sunxi: h3: Update DT files
.../dts/sun50i-h5-bananapi-m2-plus-v1.2.dts | 1 +
arch/arm/dts/sun50i-h5-cpu-opp.dtsi | 79 +++++++++++++++
.../arm/dts/sun50i-h5-libretech-all-h3-cc.dts | 1 +
.../arm/dts/sun50i-h5-libretech-all-h5-cc.dts | 2 +-
arch/arm/dts/sun50i-h5-nanopi-neo-plus2.dts | 6 +-
arch/arm/dts/sun50i-h5-nanopi-neo2.dts | 4 +-
arch/arm/dts/sun50i-h5-orangepi-pc2.dts | 27 +++++-
arch/arm/dts/sun50i-h5-orangepi-prime.dts | 6 +-
arch/arm/dts/sun50i-h5-orangepi-zero-plus.dts | 4 +-
.../arm/dts/sun50i-h5-orangepi-zero-plus2.dts | 38 ++++++++
arch/arm/dts/sun50i-h5.dtsi | 61 ++++++++++--
arch/arm/dts/sun50i-h6-beelink-gs1.dts | 6 +-
arch/arm/dts/sun50i-h6-cpu-opp.dtsi | 20 ++--
arch/arm/dts/sun50i-h6-orangepi-3.dts | 4 +-
arch/arm/dts/sun50i-h6-orangepi.dtsi | 4 +-
arch/arm/dts/sun50i-h6-pine-h64.dts | 7 +-
arch/arm/dts/sun50i-h6.dtsi | 26 +++++
.../dts/sun8i-h2-plus-bananapi-m2-zero.dts | 96 ++++++++++++++++++-
arch/arm/dts/sun8i-h3-beelink-x2.dts | 4 +-
arch/arm/dts/sun8i-h3-nanopi-duo2.dts | 4 +-
arch/arm/dts/sun8i-h3-nanopi-neo-air.dts | 4 +-
arch/arm/dts/sun8i-h3-nanopi.dtsi | 4 +-
arch/arm/dts/sun8i-h3-orangepi-pc-plus.dts | 5 -
arch/arm/dts/sun8i-h3-orangepi-plus2e.dts | 2 +-
arch/arm/dts/sun8i-h3-orangepi-zero-plus2.dts | 38 ++++++++
arch/arm/dts/sun8i-h3.dtsi | 49 +++++++++-
arch/arm/dts/sunxi-h3-h5.dtsi | 42 +++++++-
27 files changed, 483 insertions(+), 61 deletions(-)
create mode 100644 arch/arm/dts/sun50i-h5-cpu-opp.dtsi
--
2.17.5
next reply other threads:[~2021-05-27 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 0:44 Andre Przywara [this message]
2021-05-27 0:44 ` [PATCH 1/3] arm: dts: sunxi: h6: Update DT files Andre Przywara
2021-05-27 0:44 ` [PATCH 2/3] arm: dts: sunxi: h5: " Andre Przywara
2021-05-27 0:44 ` [PATCH 3/3] arm: dts: sunxi: h3: " Andre Przywara
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=20210527004438.19783-1-andre.przywara@arm.com \
--to=andre.przywara@arm.com \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=pbrobinson@gmail.com \
--cc=peron.clem@gmail.com \
--cc=samuel@sholland.org \
--cc=u-boot@lists.denx.de \
--cc=wens@csie.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).