From: Stefan Wahren <stefan.wahren@i2se.com>
To: Rob Herring <robh+dt@kernel.org>,
Nicolas Saenz Julienne <nsaenz@kernel.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
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>,
soc@kernel.org, Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-watchdog@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: [PATCH 0/6] ARM: dts: Add Raspberry Pi 400 support
Date: Sun, 30 May 2021 11:26:09 +0200 [thread overview]
Message-ID: <1622366775-5309-1-git-send-email-stefan.wahren@i2se.com> (raw)
This series adds support for the Raspberry Pi 400.
Stefan Wahren (6):
ARM: dts: bcm283x: Fix up MMC node names
watchdog: bcm2835_wdt: consider system-power-controller property
ARM: dts: Move BCM2711 RPi specific into separate dtsi
dt-bindings: arm: bcm2835: Add Raspberry Pi 400 to DT schema
ARM: dts: Add Raspberry Pi 400 support
arm64: dts: broadcom: Add reference to RPi 400
.../devicetree/bindings/arm/bcm/bcm2835.yaml | 1 +
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 62 +----
arch/arm/boot/dts/bcm2711-rpi-400.dts | 271 +++++++++++++++++++++
arch/arm/boot/dts/bcm2711-rpi.dtsi | 75 ++++++
arch/arm/boot/dts/bcm2711.dtsi | 2 +-
arch/arm/boot/dts/bcm283x.dtsi | 2 +-
arch/arm64/boot/dts/broadcom/Makefile | 3 +-
arch/arm64/boot/dts/broadcom/bcm2711-rpi-400.dts | 2 +
drivers/watchdog/bcm2835_wdt.c | 10 +-
10 files changed, 362 insertions(+), 67 deletions(-)
create mode 100644 arch/arm/boot/dts/bcm2711-rpi-400.dts
create mode 100644 arch/arm/boot/dts/bcm2711-rpi.dtsi
create mode 100644 arch/arm64/boot/dts/broadcom/bcm2711-rpi-400.dts
--
2.7.4
next reply other threads:[~2021-05-30 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 9:26 Stefan Wahren [this message]
2021-05-30 9:26 ` [PATCH 1/6] ARM: dts: bcm283x: Fix up MMC node names Stefan Wahren
2021-05-30 9:26 ` [PATCH 2/6] watchdog: bcm2835_wdt: consider system-power-controller property Stefan Wahren
2021-06-02 10:37 ` Guenter Roeck
[not found] ` <e61ba6f5b906fd26a61e9c79ef4dcf4792a364d7.camel@kernel.org>
2021-06-02 10:40 ` Guenter Roeck
2021-05-30 9:26 ` [PATCH 3/6] ARM: dts: Move BCM2711 RPi specific into separate dtsi Stefan Wahren
[not found] ` <86a7cded6e3e17b0ab347e55b38a44e10bc4e46a.camel@kernel.org>
2021-06-01 18:51 ` Stefan Wahren
2021-05-30 9:26 ` [PATCH 4/6] dt-bindings: arm: bcm2835: Add Raspberry Pi 400 to DT schema Stefan Wahren
2021-06-04 21:31 ` Rob Herring
2021-05-30 9:26 ` [PATCH 5/6] ARM: dts: Add Raspberry Pi 400 support Stefan Wahren
2021-05-30 9:26 ` [PATCH 6/6] arm64: dts: broadcom: Add reference to RPi 400 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=1622366775-5309-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=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nsaenz@kernel.org \
--cc=olof@lixom.net \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=soc@kernel.org \
--cc=wim@linux-watchdog.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).