From: William Zhang <william.zhang@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>,
"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
Subject: RE: [PATCH v2 09/12] ARM64: dts: bcm4908: Add BCMBCA peripherals
Date: Fri, 25 Apr 2025 18:12:11 -0700 [thread overview]
Message-ID: <12c7d18c74a8b9e6be20e6dfadee8fce@mail.gmail.com> (raw)
In-Reply-To: <20250406-bcmbca-peripherals-arm-v2-9-22130836c2ed@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 6333 bytes --]
> -----Original Message-----
> From: Linus Walleij <linus.walleij@linaro.org>
> Sent: Sunday, April 6, 2025 8:33 AM
> 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 v2 09/12] ARM64: dts: bcm4908: Add BCMBCA peripherals
>
> All the BCMBCA SoCs share a set of peripherals at 0xff800000,
> albeit at slightly varying memory locations on the bus and
> with varying IRQ assignments. ARM64 SoCs have additional
> peripherals at 0xff858000.
>
> Add the watchdog, remaining GPIO blocks, RNG, and DMA blocks
> for the BCM4908 based on the vendor files 4908_map_part.h
> and 4908_intr.h from the "bcmopen-consumer" code drop.
>
> This SoC has up to 320 possible GPIOs due to having 10
> registers with 32 GPIOs in each available.
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> arch/arm64/boot/dts/broadcom/bcmbca/bcm4908.dtsi | 122
> ++++++++++++++++++++++-
> 1 file changed, 120 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/broadcom/bcmbca/bcm4908.dtsi
> b/arch/arm64/boot/dts/broadcom/bcmbca/bcm4908.dtsi
> index
> 613ba7ee43d6489ea0f1490d2fccaf90961b2694..a2e5277a2e77c0bdec5d933d3
> 121b4ebf2d2d07b 100644
> --- a/arch/arm64/boot/dts/broadcom/bcmbca/bcm4908.dtsi
> +++ b/arch/arm64/boot/dts/broadcom/bcmbca/bcm4908.dtsi
> @@ -323,6 +323,7 @@ pmb: power-controller@2800c0 {
> };
> };
>
> + /* PERF Peripherals */
> bus@ff800000 {
> compatible = "simple-bus";
> #address-cells = <1>;
> @@ -348,13 +349,103 @@ watchdog@28 {
> };
> };
>
> - gpio0: gpio-controller@500 {
> + /* GPIOs 0 .. 31 */
> + gpio0: gpio@500 {
> compatible = "brcm,bcm6345-gpio";
> + reg = <0x500 0x04>, <0x528 0x04>;
> reg-names = "dirout", "dat";
> - reg = <0x500 0x28>, <0x528 0x28>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + };
> +
> + /* GPIOs 32 .. 63 */
> + gpio1: gpio@504 {
> + compatible = "brcm,bcm6345-gpio";
> + reg = <0x504 0x04>, <0x52c 0x04>;
> + reg-names = "dirout", "dat";
> + gpio-controller;
> + #gpio-cells = <2>;
> + status = "disabled";
> + };
> +
> + /* GPIOs 64 .. 95 */
> + gpio2: gpio@508 {
> + compatible = "brcm,bcm6345-gpio";
> + reg = <0x508 0x04>, <0x530 0x04>;
> + reg-names = "dirout", "dat";
> + gpio-controller;
> + #gpio-cells = <2>;
> + status = "disabled";
> + };
> +
> + /* GPIOs 96 .. 127 */
> + gpio3: gpio@50c {
> + compatible = "brcm,bcm6345-gpio";
> + reg = <0x50c 0x04>, <0x534 0x04>;
> + reg-names = "dirout", "dat";
> + gpio-controller;
> + #gpio-cells = <2>;
> + status = "disabled";
> + };
>
> + /* GPIOs 128 .. 159 */
> + gpio4: gpio@510 {
> + compatible = "brcm,bcm6345-gpio";
> + reg = <0x510 0x04>, <0x538 0x04>;
> + reg-names = "dirout", "dat";
> + gpio-controller;
> #gpio-cells = <2>;
> + status = "disabled";
> + };
> +
> + /* GPIOs 160 .. 191 */
> + gpio5: gpio@514 {
> + compatible = "brcm,bcm6345-gpio";
> + reg = <0x514 0x04>, <0x53c 0x04>;
> + reg-names = "dirout", "dat";
> gpio-controller;
> + #gpio-cells = <2>;
> + status = "disabled";
> + };
> +
> + /* GPIOs 192 .. 223 */
> + gpio6: gpio@518 {
> + compatible = "brcm,bcm6345-gpio";
> + reg = <0x518 0x04>, <0x540 0x04>;
> + reg-names = "dirout", "dat";
> + gpio-controller;
> + #gpio-cells = <2>;
> + status = "disabled";
> + };
> +
> + /* GPIOs 224 .. 255 */
> + gpio7: gpio@51c {
> + compatible = "brcm,bcm6345-gpio";
> + reg = <0x51c 0x04>, <0x544 0x04>;
> + reg-names = "dirout", "dat";
> + gpio-controller;
> + #gpio-cells = <2>;
> + status = "disabled";
> + };
> +
> + /* GPIOs 256 .. 287 */
> + gpio8: gpio@520 {
> + compatible = "brcm,bcm6345-gpio";
> + reg = <0x520 0x04>, <0x548 0x04>;
> + reg-names = "dirout", "dat";
> + gpio-controller;
> + #gpio-cells = <2>;
> + status = "disabled";
> + };
> +
> + /* GPIOs 288 .. 319 */
> + gpio9: gpio@524 {
> + compatible = "brcm,bcm6345-gpio";
> + reg = <0x524 0x04>, <0x54c 0x04>;
> + reg-names = "dirout", "dat";
> + gpio-controller;
> + #gpio-cells = <2>;
> + status = "disabled";
> };
>
> pinctrl@560 {
> @@ -584,6 +675,12 @@ leds: leds@800 {
> #size-cells = <0>;
> };
>
> + rng@b80 {
> + compatible = "brcm,iproc-rng200";
> + reg = <0xb80 0x28>;
> + interrupts = <GIC_SPI 79 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> hsspi: spi@1000 {
> #address-cells = <1>;
> #size-cells = <0>;
> @@ -638,6 +735,27 @@ reset-controller@2644 {
> };
> };
>
> + /* PERF1 Peripherals */
The dma controller is under the same periph bus starting from0xff800000.
You can increase the range to 0x400000 which is actual the max range.
We are using the same periph bus for dma on other v7 platforms. We should
keep the same for v8 platfroms too IMHO. And that's what we have for
future new chips too.
> + bus@ff858000 {
> + compatible = "simple-bus";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x00 0x00 0xff858000 0x3000>;
> +
> + pl081_dma: dma-controller@1000 {
> + compatible = "arm,pl081", "arm,primecell";
> + // The magic B105F00D info is missing
> + arm,primecell-periphid = <0x00041081>;
> + reg = <0x1000 0x1000>;
> + interrupts = <GIC_SPI 84 IRQ_TYPE_LEVEL_HIGH>;
> + memcpy-burst-size = <256>;
> + memcpy-bus-width = <32>;
> + clocks = <&periph_clk>;
> + clock-names = "apb_pclk";
> + #dma-cells = <2>;
> + };
> + };
> +
> reboot {
> compatible = "syscon-reboot";
> regmap = <&twd>;
>
> --
> 2.49.0
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4199 bytes --]
next prev parent reply other threads:[~2025-04-26 1:14 UTC|newest]
Thread overview: 37+ 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-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 [this message]
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
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=12c7d18c74a8b9e6be20e6dfadee8fce@mail.gmail.com \
--to=william.zhang@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=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.