From: Andre Przywara <andre.przywara@arm.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Chen-Yu Tsai <wens@csie.org>
Cc: Marc Zyngier <maz@kernel.org>,
Piotr Oniszczuk <piotr.oniszczuk@gmail.com>,
linux-sunxi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH 0/2] arm64: dts: allwinner: Add Orange Pi Zero 2W support
Date: Fri, 20 Oct 2023 15:57:04 +0100 [thread overview]
Message-ID: <20231020145706.705420-1-andre.przywara@arm.com> (raw)
Hi,
this adds support for the Orange Pi Zero 2W, a small board in the
Raspberry Pi Zero form factor, but with an Allwinner H618 Soc and up to
4 GB of DRAM.
This is just for the base board, created by looking at the schematics.
There is an FPC connector, which connects to a stackable expansion
board, that provides two additional USB-A sockets and an Ethernet jack,
among other connectors.
What is the recommended way to model this, via a DT overlay, applied
dynamically by the bootloader, or using a separate .dts file, that
includes this base board file?
Cheers,
Andre
Andre Przywara (2):
dt-bindings: arm: sunxi: add Orange Pi Zero 2W
arm64: dts: allwinner: h616: add Orange Pi Zero 2W support
.../devicetree/bindings/arm/sunxi.yaml | 5 +
.../allwinner/sun50i-h618-orangepi-zero2w.dts | 176 ++++++++++++++++++
2 files changed, 181 insertions(+)
create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h618-orangepi-zero2w.dts
--
2.25.1
next reply other threads:[~2023-10-20 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 14:57 Andre Przywara [this message]
2023-10-20 14:57 ` [PATCH 1/2] dt-bindings: arm: sunxi: add Orange Pi Zero 2W Andre Przywara
2023-10-20 15:39 ` Conor Dooley
2023-10-20 14:57 ` [PATCH 2/2] arm64: dts: allwinner: h616: add Orange Pi Zero 2W support Andre Przywara
2023-10-21 6:22 ` Jernej Škrabec
2023-10-21 21:47 ` Andre Przywara
2023-10-21 6:25 ` [PATCH 0/2] arm64: dts: allwinner: Add " Jernej Škrabec
2023-11-18 22:19 ` Jernej Škrabec
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=20231020145706.705420-1-andre.przywara@arm.com \
--to=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=maz@kernel.org \
--cc=piotr.oniszczuk@gmail.com \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--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