From: Anand Gore <anand.gore@broadcom.com>
To: linux-arm-kernel@lists.infradead.org
Cc: dan.beygelman@broadcom.com, joel.peshkin@broadcom.com,
florian.fainelli@broadcom.com,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
kursad.oney@broadcom.com,
William Zhang <william.zhang@broadcom.com>,
Anand Gore <anand.gore@broadcom.com>,
Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Olof Johansson <olof@lixom.net>, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
soc@kernel.org
Subject: [PATCH 0/3] Broadband SoC BCM63178.
Date: Mon, 16 May 2022 10:38:05 -0700 [thread overview]
Message-ID: <20220516173808.1391482-1-anand.gore@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
The initial support includes a bare-bone dts
for quad core ARM v7 with a ARM PL011 uart. Linux kernel image can be
built with the ARM defconfig.
Anand Gore (3):
ARM: dts: add dts files for bcmbca soc 63178
dt-bindings: arm: add BCM63178 soc to binding document
MAINTAINERS: add bcm63178 to bcmbca arch entry
.../bindings/arm/bcm/brcm,bcmbca.yaml | 7 ++
MAINTAINERS | 3 +-
arch/arm/boot/dts/Makefile | 3 +-
arch/arm/boot/dts/bcm63178.dtsi | 118 ++++++++++++++++++
arch/arm/boot/dts/bcm963178.dts | 30 +++++
5 files changed, 158 insertions(+), 3 deletions(-)
create mode 100644 arch/arm/boot/dts/bcm63178.dtsi
create mode 100644 arch/arm/boot/dts/bcm963178.dts
--
2.25.1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4203 bytes --]
next reply other threads:[~2022-05-16 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 17:38 Anand Gore [this message]
2022-05-16 17:38 ` [PATCH 1/3] ARM: dts: add dts files for bcmbca soc 63178 Anand Gore
2022-05-18 20:02 ` Florian Fainelli
2022-05-16 17:38 ` [PATCH 2/3] dt-bindings: arm: add BCM63178 soc to binding document Anand Gore
2022-05-17 7:55 ` Krzysztof Kozlowski
2022-05-18 20:02 ` 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=20220516173808.1391482-1-anand.gore@broadcom.com \
--to=anand.gore@broadcom.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.beygelman@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=joel.peshkin@broadcom.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=william.zhang@broadcom.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).