[GIT PULL 1/2] Broadcom devicetree changes for 7.1

[GIT PULL 1/2] Broadcom devicetree changes for 7.1

[Florian Fainelli]

The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  https://github.com/Broadcom/stblinux.git tags/arm-soc/for-7.1/devicetree

for you to fetch changes up to 220bdfcb4b4788f57faa2c28454d8b2dd3bcab6c:

  ARM: dts: BCM5301X: EA9200: specify partitions (2026-03-20 16:57:31 -0700)

----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs Device Tree updates
for 7.1, please pull the following:

- Rafal provides a complete description of the PCIe Root Complex nodes
  in order to silence a number of dtc warnings

- Rosen provides the necessary NVMEM properties to allow describing the
  WAN device MAC address from NVRAM, also adds better LEDs, USB GPIOs
  and Wi-Fi buttons for the Linksys EA9200 router

- Linus completes the BCA devices description by adding the I2C block
  and fixing interrupts for the DMA block on 63138 and 6878

----------------------------------------------------------------
Linus Walleij (7):
      ARM: dts: bcm6878: Fix PL081 DMA block IRQ
      ARM: dts: bcm63138: Fix DMA IRQ
      ARM: dts: bcm6846: Add I2C bus block
      ARM: dts: bcm6855: Add I2C bus blocks
      ARM: dts: bcm6878: Add I2C bus block
      ARM: dts: bcm63138: Add I2C block
      ARM: dts: bcm63148: Add I2C block

Miquel Raynal (1):
      ARM: dts: BCM5301X: Drop extra NAND controller compatible

Rafał Miłecki (1):
      ARM: dts: BCM5301X: Describe PCIe controllers fully

Rob Herring (Arm) (1):
      ARM: dts: broadcom: bcm2835-rpi: Move non simple-bus nodes to root level

Rosen Penev (9):
      ARM: dts: BCM5301X: add root pcie bridges
      ARM: dts: BCM5301X: EA9200: set WAN MAC from nvram
      ARM: dts: BCM5301X: panamera: set WAN MAC from nvram
      ARM: dts: BCM5301X: AC3100: set WAN MAC from nvram
      ARM: dts: BCM5301X: AC5300: set WAN MAC from nvram
      ARM: dts: BCM5301X: EA9200: add WiFi button
      ARM: dts: BCM5301X: EA9200: add USB GPIOs
      ARM: dts: BCM5301X: EA9200: add LEDs
      ARM: dts: BCM5301X: EA9200: specify partitions

 arch/arm/boot/dts/broadcom/bcm-ns.dtsi             |  58 +++++++++++-
 arch/arm/boot/dts/broadcom/bcm2835-common.dtsi     |   7 +-
 arch/arm/boot/dts/broadcom/bcm2835-rpi.dtsi        |  16 ++--
 .../boot/dts/broadcom/bcm4709-linksys-ea9200.dts   | 100 +++++++++++++++++++++
 .../boot/dts/broadcom/bcm4709-netgear-r8000.dts    |  73 +++++++--------
 .../boot/dts/broadcom/bcm47094-asus-rt-ac3100.dtsi |   7 ++
 .../boot/dts/broadcom/bcm47094-asus-rt-ac5300.dts  |   3 +
 .../dts/broadcom/bcm47094-linksys-panamera.dts     |   7 ++
 .../boot/dts/broadcom/bcm47094-luxul-xap-1610.dts  |  36 ++------
 .../dts/broadcom/bcm47094-luxul-xwr-3150-v1.dts    |  36 ++------
 arch/arm/boot/dts/broadcom/bcm63138.dtsi           |  11 ++-
 arch/arm/boot/dts/broadcom/bcm63148.dtsi           |  11 ++-
 arch/arm/boot/dts/broadcom/bcm6846.dtsi            |   9 ++
 arch/arm/boot/dts/broadcom/bcm6855.dtsi            |  18 ++++
 arch/arm/boot/dts/broadcom/bcm6878.dtsi            |  11 ++-
 15 files changed, 289 insertions(+), 114 deletions(-)

[GIT PULL 2/2] Broadcom devicetree-arm64 changes for 7.1

[Florian Fainelli]

The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  https://github.com/Broadcom/stblinux.git tags/arm-soc/for-7.1/devicetree-arm64

for you to fetch changes up to 0acb1de2b4df426a62dba33bcd80f3939636f97b:

  arm64: dts: broadcom: bcm2712: Move non simple-bus nodes to root level (2026-03-20 10:17:30 -0700)

----------------------------------------------------------------
This pull request contains Broadcom ARM64-based SoCs Device Tree updates
for 7.1, please pull the following:

- Maira adds the V3D DT node to the 2712 (Raspberry Pi 5) SoC

- Gergor adds the I2C controller, CSI (camera), ISP (image signal
  processor), fixes the pinctrl node and updates the UART10 interrupt
  for the RP1 sister chip to the 2712 (Raspberry Pi 5)

- Rob moves the firmware and GPU to the root level to fix DTC warnings

----------------------------------------------------------------
Gregor Herburger (6):
      arm64: dts: broadcom: rp1: add i2c controller
      arm64: dts: broadcom: rp1: add csi nodes
      arm64: dts: broadcom: bcm2712: add camera backend node pispbe
      arm64: dts: broadcom: bcm2712-rpi-5-b: add pinctrl properties for csi i2cs
      arm64: dts: broadcom: bcm2712-d-rpi-5-b: add fixes for pinctrl/pinctrl_aon
      arm64: dts: broadcom: bcm2712-d-rpi-5-b: update uart10 interrupt

Maíra Canal (1):
      arm64: dts: broadcom: bcm2712: Add V3D device node

Rob Herring (Arm) (1):
      arm64: dts: broadcom: bcm2712: Move non simple-bus nodes to root level

 arch/arm64/boot/dts/broadcom/bcm2712-d-rpi-5-b.dts |  14 +++
 .../boot/dts/broadcom/bcm2712-rpi-5-b-base.dtsi    |  55 +++++------
 arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts   |  24 +++++
 arch/arm64/boot/dts/broadcom/bcm2712.dtsi          |  29 +++++-
 arch/arm64/boot/dts/broadcom/rp1-common.dtsi       | 105 +++++++++++++++++++++
 5 files changed, 196 insertions(+), 31 deletions(-)

Re: [GIT PULL 2/2] Broadcom devicetree-arm64 changes for 7.1

[Krzysztof Kozlowski]

On Mon, Mar 23, 2026 at 12:02:39PM -0700, Florian Fainelli wrote:
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> 
>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/Broadcom/stblinux.git tags/arm-soc/for-7.1/devicetree-arm64
> 
> for you to fetch changes up to 0acb1de2b4df426a62dba33bcd80f3939636f97b:
> 
>   arm64: dts: broadcom: bcm2712: Move non simple-bus nodes to root level (2026-03-20 10:17:30 -0700)

Patches were good, I wanted to merge them, but then merge complained:

	Can't check signature: No public key

I refreshed now my keyring with kernel.org and the same.

I think the same issue was last time and repo is non korg, so nothing
seems to improve.

I am moving on.

Best regards,
Krzysztof

Re: [GIT PULL 2/2] Broadcom devicetree-arm64 changes for 7.1

[Krzysztof Kozlowski]

On 01/04/2026 13:18, Krzysztof Kozlowski wrote:
> On Mon, Mar 23, 2026 at 12:02:39PM -0700, Florian Fainelli wrote:
>> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
>>
>>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
>>
>> are available in the Git repository at:
>>
>>   https://github.com/Broadcom/stblinux.git tags/arm-soc/for-7.1/devicetree-arm64
>>
>> for you to fetch changes up to 0acb1de2b4df426a62dba33bcd80f3939636f97b:
>>
>>   arm64: dts: broadcom: bcm2712: Move non simple-bus nodes to root level (2026-03-20 10:17:30 -0700)
> 
> Patches were good, I wanted to merge them, but then merge complained:
> 
> 	Can't check signature: No public key
> 
> I refreshed now my keyring with kernel.org and the same.
> 
> I think the same issue was last time and repo is non korg, so nothing
> seems to improve.


Maybe last time I mentioned this only internally or on IRC, so could get
lost. Please get your key in to the kernel keyring, to solve above. Pull
is not rejected, but I leave it to Arnd who might have your key.

How to get key signed? Obviously conferences are the easiest way, but
other is to find people around you or on your travel itinerary via
ksmap. Eventually many people do video call cross signing, so even
travel is not needed. I video signed twice, but that was an exception
because I prefer to meet in person. Kernel wiki has guideline on all
this, so I am not saying anything new here.

Best regards,
Krzysztof

Re: [GIT PULL 2/2] Broadcom devicetree-arm64 changes for 7.1

[Arnd Bergmann]

On Wed, Apr 1, 2026, at 14:02, Krzysztof Kozlowski wrote:
> On 01/04/2026 13:18, Krzysztof Kozlowski wrote:
>> On Mon, Mar 23, 2026 at 12:02:39PM -0700, Florian Fainelli wrote:
>> 
>> I think the same issue was last time and repo is non korg, so nothing
>> seems to improve.
>
>
> Maybe last time I mentioned this only internally or on IRC, so could get
> lost. Please get your key in to the kernel keyring, to solve above. Pull
> is not rejected, but I leave it to Arnd who might have your key.
>
> How to get key signed? Obviously conferences are the easiest way, but
> other is to find people around you or on your travel itinerary via
> ksmap. Eventually many people do video call cross signing, so even
> travel is not needed. I video signed twice, but that was an exception
> because I prefer to meet in person. Kernel wiki has guideline on all
> this, so I am not saying anything new here.

I think what happened is that the key expired. I can see that
Florian is using the same key as the last 113 times, and I see
it has signatures from other developers, but the copy I have
expired in 2024, which probably caused it to disappear from
the keyservers.

this is what I see:

$ gpg --list-sigs 9BE46ADFE60625D891F72B8587D0969C44070704
pub   dsa1024/61579915B563760E 2008-09-16 [SCA] [expired: 2024-11-06]
      FE4FA16F65261D8BDA57BCBD61579915B563760E
uid                 [ expired] Florian Fainelli <f.fainelli@gmail.com>
sig          DE95E6B5B9FA86CB 2008-09-16  Florian Fainelli <florian.fainelli@openpattern.org>
sig          9B1F67D46FF7D7AB 2008-09-16  Florian Fainelli <florian.fainelli@telecomint.eu>
sig          F91A73ED49C617B5 2008-09-16  Florian Fainelli <florian@minet.net>
sig          972BE49811AD8F26 2008-09-16  Florian Fainelli <florian@openwrt.org>
sig 3        61579915B563760E 2008-09-16  Florian Fainelli <f.fainelli@gmail.com>
sig 3        61579915B563760E 2014-11-09  Florian Fainelli <f.fainelli@gmail.com>
sig          3A8F3B2F5A7C9849 2016-03-12  Michael Turquette <mturquette@baylibre.com>
sig          E6BF0DCBA6694C84 2017-04-08  Andrew Lunn <andrew@lunn.ch>
sig          987E58D467ED50B8 2017-04-09  [User ID not found]

       Arnd

Re: [GIT PULL 2/2] Broadcom devicetree-arm64 changes for 7.1

[Krzysztof Kozlowski]

On 01/04/2026 16:37, Arnd Bergmann wrote:
> On Wed, Apr 1, 2026, at 14:02, Krzysztof Kozlowski wrote:
>> On 01/04/2026 13:18, Krzysztof Kozlowski wrote:
>>> On Mon, Mar 23, 2026 at 12:02:39PM -0700, Florian Fainelli wrote:
>>>
>>> I think the same issue was last time and repo is non korg, so nothing
>>> seems to improve.
>>
>>
>> Maybe last time I mentioned this only internally or on IRC, so could get
>> lost. Please get your key in to the kernel keyring, to solve above. Pull
>> is not rejected, but I leave it to Arnd who might have your key.
>>
>> How to get key signed? Obviously conferences are the easiest way, but
>> other is to find people around you or on your travel itinerary via
>> ksmap. Eventually many people do video call cross signing, so even
>> travel is not needed. I video signed twice, but that was an exception
>> because I prefer to meet in person. Kernel wiki has guideline on all
>> this, so I am not saying anything new here.
> 
> I think what happened is that the key expired. I can see that
> Florian is using the same key as the last 113 times, and I see
> it has signatures from other developers, but the copy I have
> expired in 2024, which probably caused it to disappear from
> the keyservers.
> 
> this is what I see:
> 
> $ gpg --list-sigs 9BE46ADFE60625D891F72B8587D0969C44070704
> pub   dsa1024/61579915B563760E 2008-09-16 [SCA] [expired: 2024-11-06]

dsa1024 might be another answer... DSA1024 was deprecated by NIST in
2013, so maybe gnugp even drops it just like keys with too weak signatures?

But another problem is that I do not see it in the `git log` of keyring
at all which suggests it wasn't ever submitted.

I don't think DSA1024 can be accepted now in keyring, so this requires a
new key, cross signed by the old one.

>       FE4FA16F65261D8BDA57BCBD61579915B563760E
> uid                 [ expired] Florian Fainelli <f.fainelli@gmail.com>
> sig          DE95E6B5B9FA86CB 2008-09-16  Florian Fainelli <florian.fainelli@openpattern.org>
> sig          9B1F67D46FF7D7AB 2008-09-16  Florian Fainelli <florian.fainelli@telecomint.eu>
> sig          F91A73ED49C617B5 2008-09-16  Florian Fainelli <florian@minet.net>
> sig          972BE49811AD8F26 2008-09-16  Florian Fainelli <florian@openwrt.org>
> sig 3        61579915B563760E 2008-09-16  Florian Fainelli <f.fainelli@gmail.com>
> sig 3        61579915B563760E 2014-11-09  Florian Fainelli <f.fainelli@gmail.com>
> sig          3A8F3B2F5A7C9849 2016-03-12  Michael Turquette <mturquette@baylibre.com>
> sig          E6BF0DCBA6694C84 2017-04-08  Andrew Lunn <andrew@lunn.ch>
> sig          987E58D467ED50B8 2017-04-09  [User ID not found]
> 
>        Arnd


Best regards,
Krzysztof

Re: [GIT PULL 2/2] Broadcom devicetree-arm64 changes for 7.1

[Arnd Bergmann]

On Wed, Apr 1, 2026, at 16:47, Krzysztof Kozlowski wrote:
> On 01/04/2026 16:37, Arnd Bergmann wrote:
>> $ gpg --list-sigs 9BE46ADFE60625D891F72B8587D0969C44070704
>> pub   dsa1024/61579915B563760E 2008-09-16 [SCA] [expired: 2024-11-06]
>
> dsa1024 might be another answer... DSA1024 was deprecated by NIST in
> 2013, so maybe gnugp even drops it just like keys with too weak signatures?
>
> But another problem is that I do not see it in the `git log` of keyring
> at all which suggests it wasn't ever submitted.

Indeed, that also explains why the Broadcom tree is hosted on github
rather than git.kernel.org. While using the kernel.org hosting
is by no means a requirement, github does occasionally cause problems,
and I do get a bit annoyed when it takes ages to pull from that.

Florian, I don't know if there is a Broadcom specific policy that
requires you to use the corporate github account, but if you
are setting up a new key already, it may be a good time to
also move the hosting.

> I don't think DSA1024 can be accepted now in keyring, so this requires a
> new key, cross signed by the old one.

+1

      Arnd

Re: [GIT PULL 2/2] Broadcom devicetree-arm64 changes for 7.1

[Krzysztof Kozlowski]

On 01/04/2026 18:33, Arnd Bergmann wrote:
> On Wed, Apr 1, 2026, at 16:47, Krzysztof Kozlowski wrote:
>> On 01/04/2026 16:37, Arnd Bergmann wrote:
>>> $ gpg --list-sigs 9BE46ADFE60625D891F72B8587D0969C44070704
>>> pub   dsa1024/61579915B563760E 2008-09-16 [SCA] [expired: 2024-11-06]
>>
>> dsa1024 might be another answer... DSA1024 was deprecated by NIST in
>> 2013, so maybe gnugp even drops it just like keys with too weak signatures?
>>
>> But another problem is that I do not see it in the `git log` of keyring
>> at all which suggests it wasn't ever submitted.
> 
> Indeed, that also explains why the Broadcom tree is hosted on github
> rather than git.kernel.org. While using the kernel.org hosting
> is by no means a requirement, github does occasionally cause problems,

Kind of, but quoting Linus' policy - either kernel.org or properly
signed pulls by a key in the keyring.

Of course new SoCs/maintainers are exempted of that rule, but this does
not apply here.

> and I do get a bit annoyed when it takes ages to pull from that.
> 
> Florian, I don't know if there is a Broadcom specific policy that
> requires you to use the corporate github account, but if you
> are setting up a new key already, it may be a good time to
> also move the hosting.
> 
>> I don't think DSA1024 can be accepted now in keyring, so this requires a
>> new key, cross signed by the old one.

Just to clarify: not "cross signed", but simply signed by the old key.

> 
> +1
> 
>       Arnd


Best regards,
Krzysztof

Re: [GIT PULL 2/2] Broadcom devicetree-arm64 changes for 7.1

[Florian Fainelli]

On 4/1/26 09:38, Krzysztof Kozlowski wrote:
> On 01/04/2026 18:33, Arnd Bergmann wrote:
>> On Wed, Apr 1, 2026, at 16:47, Krzysztof Kozlowski wrote:
>>> On 01/04/2026 16:37, Arnd Bergmann wrote:
>>>> $ gpg --list-sigs 9BE46ADFE60625D891F72B8587D0969C44070704
>>>> pub   dsa1024/61579915B563760E 2008-09-16 [SCA] [expired: 2024-11-06]
>>>
>>> dsa1024 might be another answer... DSA1024 was deprecated by NIST in
>>> 2013, so maybe gnugp even drops it just like keys with too weak signatures?
>>>
>>> But another problem is that I do not see it in the `git log` of keyring
>>> at all which suggests it wasn't ever submitted.
>>
>> Indeed, that also explains why the Broadcom tree is hosted on github
>> rather than git.kernel.org. While using the kernel.org hosting
>> is by no means a requirement, github does occasionally cause problems,
> 
> Kind of, but quoting Linus' policy - either kernel.org or properly
> signed pulls by a key in the keyring.
> 
> Of course new SoCs/maintainers are exempted of that rule, but this does
> not apply here.
> 
>> and I do get a bit annoyed when it takes ages to pull from that.
>>
>> Florian, I don't know if there is a Broadcom specific policy that
>> requires you to use the corporate github account, but if you
>> are setting up a new key already, it may be a good time to
>> also move the hosting.

OK, I will get going with moving the hosting to kernel.org. What about 
this specific pull request, will it go through or is relocating the 
hosting mandatory for it to be accepted?
-- 
Florian

Re: [GIT PULL 2/2] Broadcom devicetree-arm64 changes for 7.1

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 387 bytes --]

On Wed, Apr 01, 2026 at 09:41:03AM -0700, Florian Fainelli wrote:

> OK, I will get going with moving the hosting to kernel.org. What about this
> specific pull request, will it go through or is relocating the hosting
> mandatory for it to be accepted?

Whenever you get round to it please remember to let me know so I can
update where -next is fetching from (this is a common gotcha!).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [GIT PULL 2/2] Broadcom devicetree-arm64 changes for 7.1

[Arnd Bergmann]

On Wed, Apr 1, 2026, at 18:41, Florian Fainelli wrote:
> On 4/1/26 09:38, Krzysztof Kozlowski wrote:
>> On 01/04/2026 18:33, Arnd Bergmann wrote:
>>> On Wed, Apr 1, 2026, at 16:47, Krzysztof Kozlowski wrote:
>>>
>>> Florian, I don't know if there is a Broadcom specific policy that
>>> requires you to use the corporate github account, but if you
>>> are setting up a new key already, it may be a good time to
>>> also move the hosting.
>
> OK, I will get going with moving the hosting to kernel.org. What about 
> this specific pull request, will it go through or is relocating the 
> hosting mandatory for it to be accepted?

I've merged both now, should push them out later tonight.

     Arnd

Re: [GIT PULL 1/2] Broadcom devicetree changes for 7.1

[Krzysztof Kozlowski]

On Mon, Mar 23, 2026 at 12:02:38PM -0700, Florian Fainelli wrote:
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> 
>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/Broadcom/stblinux.git tags/arm-soc/for-7.1/devicetree
> 
> for you to fetch changes up to 220bdfcb4b4788f57faa2c28454d8b2dd3bcab6c:
> 
>   ARM: dts: BCM5301X: EA9200: specify partitions (2026-03-20 16:57:31 -0700)

Four days after:

Days in linux-next:
----------------------------------------
 0 | ++++++++++++++++ (16)

...

Commits with 0 days in linux-next (16 of 19: 84.2%)...

Are you sure your tree is included in the next?

Best regards,
Krzysztof

Re: [GIT PULL 1/2] Broadcom devicetree changes for 7.1

[Florian Fainelli]

On 3/27/26 04:53, Krzysztof Kozlowski wrote:
> On Mon, Mar 23, 2026 at 12:02:38PM -0700, Florian Fainelli wrote:
>> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
>>
>>    Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
>>
>> are available in the Git repository at:
>>
>>    https://github.com/Broadcom/stblinux.git tags/arm-soc/for-7.1/devicetree
>>
>> for you to fetch changes up to 220bdfcb4b4788f57faa2c28454d8b2dd3bcab6c:
>>
>>    ARM: dts: BCM5301X: EA9200: specify partitions (2026-03-20 16:57:31 -0700)
> 
> Four days after:
> 
> Days in linux-next:
> ----------------------------------------
>   0 | ++++++++++++++++ (16)
> 
> ...
> 
> Commits with 0 days in linux-next (16 of 19: 84.2%)...
> 
> Are you sure your tree is included in the next?

The branch that is included in linux-next is my "next" branch which is a 
merge of all branches. In this particular case however it looks like the 
branch was not updated.
-- 
Florian