From: Florian Fainelli <florian.fainelli@broadcom.com>
To: soc@kernel.org
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"William Zhang" <william.zhang@broadcom.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
khilman@kernel.org, bcm-kernel-feedback-list@broadcom.com
Subject: [GIT PULL 2/5] Broadcom devicetree changes for 6.17
Date: Mon, 30 Jun 2025 12:02:13 -0700 [thread overview]
Message-ID: <20250630190216.1518354-2-florian.fainelli@broadcom.com> (raw)
In-Reply-To: <20250630190216.1518354-1-florian.fainelli@broadcom.com>
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.17/devicetree
for you to fetch changes up to 8df00d6bdb0ab976637ba15829be5771dad2073f:
ARM: dts: bcm958625-meraki-mx6x: Use #pwm-cells = <3> (2025-06-09 10:10:41 -0700)
----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs Device Tree updates
for 6.17, please pull the following:
- Linus makes a number of updates to the BCMBCA SoCs Device Tree files
to correct UART interrupt numbers, add interrupts to the RNG block,
and leverage the fact that all SoCs have the same peripherals at the
same aperture
- Uwe corrects the Merakia MX6X DTS file to have #pwm-cells = 3 as per
the binding
----------------------------------------------------------------
Linus Walleij (8):
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
Uwe Kleine-König (1):
ARM: dts: bcm958625-meraki-mx6x: Use #pwm-cells = <3>
.../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 ++++++++++++++++++-
.../dts/broadcom/bcm958625-meraki-mx6x-common.dtsi | 7 +-
8 files changed, 510 insertions(+), 6 deletions(-)
next prev parent reply other threads:[~2025-06-30 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 19:02 [GIT PULL 1/5] Broadcom defconfig-arm64 changes for 6.17 Florian Fainelli
2025-06-30 19:02 ` Florian Fainelli [this message]
2025-06-30 19:02 ` [GIT PULL 3/5] Broadcom devicetree-arm64 " Florian Fainelli
2025-06-30 19:02 ` [GIT PULL 4/5] Broadcom drivers " Florian Fainelli
2025-07-01 5:11 ` Greg Kroah-Hartman
2025-07-01 10:11 ` Andrea della Porta
2025-06-30 19:02 ` [GIT PULL 5/5] Broadcom maintainers " 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=20250630190216.1518354-2-florian.fainelli@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=khilman@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@kernel.org \
--cc=u.kleine-koenig@baylibre.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