From: Florian Fainelli <florian.fainelli@broadcom.com>
To: "Linus Walleij" <linus.walleij@linaro.org>,
"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>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v2 00/12] ARM: bcm: Add some BCMBCA peripherals
Date: Sat, 26 Apr 2025 10:49:00 +0200 [thread overview]
Message-ID: <dc47e9ba-e23d-45d2-bae1-cac8bac2310b@broadcom.com> (raw)
In-Reply-To: <20250406-bcmbca-peripherals-arm-v2-0-22130836c2ed@linaro.org>
On 4/6/2025 5:32 PM, Linus Walleij wrote:
> 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 can you resubmit a v3 addressing William's feedback? I will drop
your series for now. Thanks!
--
Florian
next prev parent reply other threads:[~2025-04-26 8:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-06 15:32 [PATCH v2 00/12] ARM: bcm: Add some BCMBCA peripherals Linus Walleij
2025-04-06 15:32 ` [PATCH v2 01/12] ARM: dts: bcm6878: Correct UART0 IRQ number Linus Walleij
2025-04-11 23:42 ` Florian Fainelli
2025-04-26 0:57 ` William Zhang
2025-04-06 15:32 ` [PATCH v2 02/12] dt-bindings: rng: r200: Add interrupt property Linus Walleij
2025-04-11 23:42 ` Florian Fainelli
2025-04-06 15:32 ` [PATCH v2 03/12] ARM: dts: bcm6846: Add interrupt to RNG Linus Walleij
2025-04-11 23:42 ` Florian Fainelli
2025-04-26 1:00 ` William Zhang
2025-04-06 15:32 ` [PATCH v2 04/12] ARM: dts: bcm6855: Add BCMBCA peripherals Linus Walleij
2025-04-11 23:42 ` Florian Fainelli
2025-04-06 15:32 ` [PATCH v2 05/12] ARM: dts: bcm6878: " Linus Walleij
2025-04-11 23:42 ` Florian Fainelli
2025-04-26 1:04 ` William Zhang
2025-04-06 15:32 ` [PATCH v2 06/12] ARM: dts: bcm63138: " Linus Walleij
2025-04-11 23:43 ` Florian Fainelli
2025-04-06 15:32 ` [PATCH v2 07/12] ARM: dts: bcm63148: " Linus Walleij
2025-04-11 23:43 ` Florian Fainelli
2025-04-06 15:32 ` [PATCH v2 08/12] ARM: dts: bcm63178: " Linus Walleij
2025-04-11 23:43 ` Florian Fainelli
2025-04-06 15:32 ` [PATCH v2 09/12] ARM64: dts: bcm4908: " Linus Walleij
2025-04-11 23:43 ` Florian Fainelli
2025-04-26 1:12 ` William Zhang
2025-04-06 15:32 ` [PATCH v2 10/12] ARM64: dts: bcm6856: " Linus Walleij
2025-04-11 23:43 ` Florian Fainelli
2025-04-26 1:13 ` William Zhang
2025-04-06 15:32 ` [PATCH v2 11/12] ARM64: dts: bcm6858: " Linus Walleij
2025-04-11 23:43 ` Florian Fainelli
2025-04-26 1:16 ` William Zhang
2025-04-06 15:32 ` [PATCH v2 12/12] ARM64: dts: bcm63158: " Linus Walleij
2025-04-11 23:43 ` Florian Fainelli
2025-04-26 1:22 ` William Zhang
2025-04-07 12:47 ` [PATCH v2 00/12] ARM: bcm: Add some " Rob Herring (Arm)
2025-04-26 8:49 ` Florian Fainelli [this message]
2025-05-10 1:11 ` William Zhang
2025-05-12 12:06 ` 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=dc47e9ba-e23d-45d2-bae1-cac8bac2310b@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kursad.oney@broadcom.com \
--cc=linus.walleij@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).