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>,
Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-hsien Lin <chi-hsien.lin@infineon.com>,
Wright Feng <wright.feng@infineon.com>,
Chung-hsien Hsu <chung-hsien.hsu@infineon.com>,
Kalle Valo <kvalo@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-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: [PATCH RFC 0/4] ARM: dts: Add Raspberry Pi Zero 2 W support
Date: Sat, 1 Jan 2022 21:26:48 +0100 [thread overview]
Message-ID: <1641068812-5851-1-git-send-email-stefan.wahren@i2se.com> (raw)
This small series tries to add support for the Raspberry Pi Zero 2 W.
Stefan Wahren (4):
brcmfmac: use separate firmware for 43430 revision 4
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 +
.../wireless/broadcom/brcm80211/brcmfmac/sdio.c | 4 +-
6 files changed, 145 insertions(+), 2 deletions(-)
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-01-01 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 20:26 Stefan Wahren [this message]
2022-01-01 20:26 ` [PATCH RFC 1/4] brcmfmac: use separate firmware for 43430 revision 4 Stefan Wahren
2022-01-22 12:35 ` Stefan Wahren
2022-01-24 9:43 ` Arend van Spriel
2022-01-30 11:35 ` Stefan Wahren
2022-01-30 12:56 ` Arend Van Spriel
2022-01-31 17:25 ` Stefan Wahren
2022-01-01 20:26 ` [PATCH RFC 2/4] dt-bindings: arm: bcm2835: Add Raspberry Pi Zero 2 W Stefan Wahren
2022-01-10 20:53 ` Rob Herring
2022-01-01 20:26 ` [PATCH RFC 3/4] ARM: dts: " Stefan Wahren
2022-01-01 20:26 ` [PATCH RFC 4/4] arm64: dts: broadcom: Add reference to RPi " Stefan Wahren
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=1641068812-5851-1-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=arnd@arndb.de \
--cc=aspriel@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=chi-hsien.lin@infineon.com \
--cc=chung-hsien.hsu@infineon.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-wireless@vger.kernel.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 \
--cc=wright.feng@infineon.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).