From: Linus Walleij <linus.walleij@linaro.org>
To: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"William Zhang" <william.zhang@broadcom.com>,
"Anand Gore" <anand.gore@broadcom.com>,
"Kursad Oney" <kursad.oney@broadcom.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Olivia Mackall" <olivia@selenic.com>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
"Florian Fainelli" <f.fainelli@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH 00/12] ARM: bcm: Add some BCMBCA peripherals
Date: Fri, 28 Mar 2025 08:43:50 +0100 [thread overview]
Message-ID: <20250328-bcmbca-peripherals-arm-v1-0-e4e515dc9b8c@linaro.org> (raw)
This adds a bunch peripherals to the Broadcom BRCMBCA
SoC:s that I happened to find documentation for in some
vendor header files.
It started when I added a bunch of peripherals for the
BCM6846, and this included really helpful peripherals
such as the PL081 DMA, for which I think the most common
usecase is to be used as a memcpy engine to offload
transfer of blocks from NAND flash to/from the NAND
flash controller (at least this is how the STMicro
FSMC controller was using it).
So I took a sweep and added all the stuff that has
bindings to:
ARM:
- BCM6846
- BCM6855
- BCM6878
- BCM63138
- BCM63148
- BCM63178
ARM64:
- BCM4908
- BCM6856
- BCM6858
- BCM63158
There are several "holes" in this SoC list, I simply
just fixed those that I happened to run into documentation
for.
Unfortunately while very similar, some IP blocks vary
slightly in version, the GPIO block is differently
integrated on different systems, and the interrupt assignments
are completely different, so it's safest to add these to each
DTSI individually.
I add the interrupt binding for the RNG block in the
process as this exists even if Linux isn't using the
IRQ, and I put the RNG and DMA engines as default-enabled
because they are not routed to the outside and should
"just work" so why not.
I did a rogue patch adding some stuff to BCM6756 based
on guessed but eventually dropped it. If someone has
docs for this SoC I can add it.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
Linus Walleij (12):
ARM: dts: bcm6878: Correct UART0 IRQ number
dt-bindings: rng: r200: Add interrupt property
ARM: dts: bcm6846: Add interrupt to RNG
ARM: dts: bcm6855: Add BCMBCA peripherals
ARM: dts: bcm6878: Add BCMBCA peripherals
ARM: dts: bcm63138: Add BCMBCA peripherals
ARM: dts: bcm63148: Add BCMBCA peripherals
ARM: dts: bcm63178: Add BCMBCA peripherals
ARM64: dts: bcm4908: Add BCMBCA peripherals
ARM64: dts: bcm6856: Add BCMBCA peripherals
ARM64: dts: bcm6858: Add BCMBCA peripherals
ARM64: dts: bcm63158: Add BCMBCA peripherals
.../devicetree/bindings/rng/brcm,iproc-rng200.yaml | 6 +
arch/arm/boot/dts/broadcom/bcm63138.dtsi | 79 ++++++++++-
arch/arm/boot/dts/broadcom/bcm63148.dtsi | 64 +++++++++
arch/arm/boot/dts/broadcom/bcm63178.dtsi | 112 +++++++++++++++
arch/arm/boot/dts/broadcom/bcm6846.dtsi | 1 +
arch/arm/boot/dts/broadcom/bcm6855.dtsi | 127 +++++++++++++++++
arch/arm/boot/dts/broadcom/bcm6878.dtsi | 120 ++++++++++++++++-
arch/arm64/boot/dts/broadcom/bcmbca/bcm4908.dtsi | 122 ++++++++++++++++-
arch/arm64/boot/dts/broadcom/bcmbca/bcm63158.dtsi | 150 ++++++++++++++++++++-
arch/arm64/boot/dts/broadcom/bcmbca/bcm6856.dtsi | 138 ++++++++++++++++++-
arch/arm64/boot/dts/broadcom/bcmbca/bcm6858.dtsi | 120 ++++++++++++++++-
11 files changed, 1030 insertions(+), 9 deletions(-)
---
base-commit: 8359b1e7edc722d4b1be26aa515041a79e4224a3
change-id: 20250327-bcmbca-peripherals-arm-dfb312052363
Best regards,
--
Linus Walleij <linus.walleij@linaro.org>
next reply other threads:[~2025-03-28 7:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 7:43 Linus Walleij [this message]
2025-03-28 7:43 ` [PATCH 01/12] ARM: dts: bcm6878: Correct UART0 IRQ number Linus Walleij
2025-03-28 7:43 ` [PATCH 02/12] dt-bindings: rng: r200: Add interrupt property Linus Walleij
2025-03-31 8:00 ` Krzysztof Kozlowski
2025-03-28 7:43 ` [PATCH 03/12] ARM: dts: bcm6846: Add interrupt to RNG Linus Walleij
2025-03-28 7:43 ` [PATCH 04/12] ARM: dts: bcm6855: Add BCMBCA peripherals Linus Walleij
2025-03-28 7:43 ` [PATCH 05/12] ARM: dts: bcm6878: " Linus Walleij
2025-03-28 7:43 ` [PATCH 06/12] ARM: dts: bcm63138: " Linus Walleij
2025-03-28 7:43 ` [PATCH 07/12] ARM: dts: bcm63148: " Linus Walleij
2025-03-28 7:43 ` [PATCH 08/12] ARM: dts: bcm63178: " Linus Walleij
2025-03-28 7:43 ` [PATCH 09/12] ARM64: dts: bcm4908: " Linus Walleij
2025-03-28 7:44 ` [PATCH 10/12] ARM64: dts: bcm6856: " Linus Walleij
2025-03-28 7:44 ` [PATCH 11/12] ARM64: dts: bcm6858: " Linus Walleij
2025-03-28 7:44 ` [PATCH 12/12] ARM64: dts: bcm63158: " Linus Walleij
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=20250328-bcmbca-peripherals-arm-v1-0-e4e515dc9b8c@linaro.org \
--to=linus.walleij@linaro.org \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=olivia@selenic.com \
--cc=rafal@milecki.pl \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--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