From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
arnd@arndb.de, khilman@kernel.org, olof@lixom.net,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/5] Broadcom devicetree-arm64 changes for 5.11
Date: Sat, 28 Nov 2020 08:34:09 -0800 [thread overview]
Message-ID: <20201128163410.1691529-4-f.fainelli@gmail.com> (raw)
In-Reply-To: <20201128163410.1691529-1-f.fainelli@gmail.com>
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.11/devicetree-arm64
for you to fetch changes up to dccb22d078ebd098115e4f66bde1ee2249c8640b:
arm64: add config for Broadcom BCM4908 SoCs (2020-11-25 09:07:49 -0800)
----------------------------------------------------------------
This pull request contains Broadcom ARM64-based SoCs Device Tree changes
for 5.11, please pull the following:
- Rafal adds initial support for the Broadcom 4908 which are SoCs used
in home routers and are based on the DSL architecture and using
Broadcom Brahma-B53 CPUs.
----------------------------------------------------------------
Rafał Miłecki (3):
dt-bindings: arm: bcm: document BCM4908 bindings
arm64: dts: broadcom: add BCM4908 and Asus GT-AC5300 early DTS files
arm64: add config for Broadcom BCM4908 SoCs
.../devicetree/bindings/arm/bcm/brcm,bcm4908.yaml | 38 +++++
arch/arm64/Kconfig.platforms | 8 +
arch/arm64/boot/dts/broadcom/Makefile | 1 +
arch/arm64/boot/dts/broadcom/bcm4908/Makefile | 2 +
.../broadcom/bcm4908/bcm4908-asus-gt-ac5300.dts | 66 ++++++++
arch/arm64/boot/dts/broadcom/bcm4908/bcm4908.dtsi | 187 +++++++++++++++++++++
arch/arm64/configs/defconfig | 1 +
7 files changed, 303 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm4908.yaml
create mode 100644 arch/arm64/boot/dts/broadcom/bcm4908/Makefile
create mode 100644 arch/arm64/boot/dts/broadcom/bcm4908/bcm4908-asus-gt-ac5300.dts
create mode 100644 arch/arm64/boot/dts/broadcom/bcm4908/bcm4908.dtsi
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-28 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 16:34 [GIT PULL 1/5] Broadcom defconfig changes for 5.11 Florian Fainelli
2020-11-28 16:34 ` [GIT PULL 2/5] Broadcom defconfig-arm64 " Florian Fainelli
2020-12-08 16:34 ` Arnd Bergmann
2020-11-28 16:34 ` [GIT PULL 3/5] Broadcom devicetree " Florian Fainelli
2020-12-08 23:09 ` Arnd Bergmann
2020-11-28 16:34 ` Florian Fainelli [this message]
2020-12-08 23:09 ` [GIT PULL 4/5] Broadcom devicetree-arm64 " Arnd Bergmann
2020-11-28 16:34 ` [GIT PULL 5/5] Broadcom drivers " Florian Fainelli
2020-12-08 16:08 ` Arnd Bergmann
2020-12-08 16:34 ` [GIT PULL 1/5] Broadcom defconfig " Arnd Bergmann
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=20201128163410.1691529-4-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=rafal@milecki.pl \
--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).