From: Stefan Wahren <stefan.wahren@i2se.com>
To: Rob Herring <robh+dt@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Nicolas Saenz Julienne <nsaenz@kernel.org>
Cc: Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Phil Elwell <phil@raspberrypi.com>,
devicetree@vger.kernel.org, soc@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: [PATCH V2 0/3] ARM: dts: Add Raspberry Pi Zero 2 W support
Date: Tue, 1 Feb 2022 18:27:44 +0100 [thread overview]
Message-ID: <1643736467-17764-1-git-send-email-stefan.wahren@i2se.com> (raw)
This small series adds support for the Raspberry Pi Zero 2 W.
Changes in V2:
- drop brcmfmac patch, because the driver is already able to handle
the wifi chip
- improve commit message of DTS patch
- add Robs Acked-by
Stefan Wahren (3):
dt-bindings: arm: bcm2835: Add Raspberry Pi Zero 2 W
ARM: dts: Add Raspberry Pi Zero 2 W
arm64: dts: broadcom: Add reference to RPi Zero 2 W
.../devicetree/bindings/arm/bcm/bcm2835.yaml | 1 +
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/bcm2837-rpi-zero-2-w.dts | 136 +++++++++++++++++++++
arch/arm64/boot/dts/broadcom/Makefile | 3 +-
.../boot/dts/broadcom/bcm2837-rpi-zero-2-w.dts | 2 +
5 files changed, 142 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/bcm2837-rpi-zero-2-w.dts
create mode 100644 arch/arm64/boot/dts/broadcom/bcm2837-rpi-zero-2-w.dts
--
2.7.4
next reply other threads:[~2022-02-01 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 17:27 Stefan Wahren [this message]
2022-02-01 17:27 ` [PATCH V2 1/3] dt-bindings: arm: bcm2835: Add Raspberry Pi Zero 2 W Stefan Wahren
2022-02-11 22:25 ` Florian Fainelli
2022-02-01 17:27 ` [PATCH V2 2/3] ARM: dts: " Stefan Wahren
2022-02-11 22:25 ` Florian Fainelli
2022-02-01 17:27 ` [PATCH V2 3/3] arm64: dts: broadcom: Add reference to RPi " Stefan Wahren
2022-02-11 22:25 ` Florian Fainelli
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=1643736467-17764-1-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenz@kernel.org \
--cc=olof@lixom.net \
--cc=phil@raspberrypi.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=soc@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).