Skip to contentSkip to conversation

Add support for Zyxel EX3510-B

PATCH Superseded Sam Edwards 4 participants 10 messages Oct 3, 2024 – Oct 5, 2024

Subsystems (2)

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

cover Add support for Zyxel EX3510-B

Hello BCMBCA maintainers,

This pair of patches adds an initial DT for the Zyxel EX3510-B "series" based on BCM4906, encompassing the EX3510-B0 and EX3510-B1. As I am not aware of any software-affecting difference between these two, I am calling the "series" one model.

I found the BCM4906/8 support in Linux to be in need of a lot of TLC, and have just sent a few patches necessary to get Linux to boot without crashing on this platform. At a minimum, you will want to apply [1] to resolve a panic related to xHCI not initializing. If you are booting through CFE and want to use the secondary CPU, you will have to apply [2] as well.

There are more patches to come. An issue with the switch driver is preventing the WAN port from operating, for example. I have worked around this locally so I can confirm that the DT I am submitting here is correct, but I will need to clean up my remaining local fixes before they can be sent.

As always, thank you very much for your continued efforts and for your time reviewing these patches.

Best regards,
Sam

[1]: https://lore.kernel.org/lkml/[email protected]/T/
[2]: https://lore.kernel.org/lkml/[email protected]/T/

Sam Edwards (2):
dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906
arm64: dts: broadcom: bcmbca: bcm4908: Add DT for Zyxel EX3510-B

 .../bindings/arm/bcm/brcm,bcmbca.yaml         |   1 +
 arch/arm64/boot/dts/broadcom/bcmbca/Makefile  |   1 +
 .../broadcom/bcmbca/bcm4906-zyxel-ex3510b.dts | 197 ++++++++++++++++++
 3 files changed, 199 insertions(+)
 create mode 100644 arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dts
Signature · 1 line
2.44.2
#1 lore raw

PATCH 1/2 dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906

This is a series (EX3510-B0 and EX3510-B1) of residential gateways based on BCM4906, a stripped-down version of the BCM4908 SoC. Although Zyxel's marketing materials call this a "series," the EX3510-B1 appears to be a very minor revision of the EX3510-B0, with only changes that are transparent to software. As far as Linux is concerned, this "series" effectively represents a single model.

---
 Documentation/devicetree/bindings/arm/bcm/brcm,bcmbca.yaml | 1 +
 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/arm/bcm/brcm,bcmbca.yaml +1 -0
index 07892cbdd23c..4999568225f1 100644
@@ -34,6 +34,7 @@ properties:
           - enum:
               - netgear,r8000p
               - tplink,archer-c2300-v1
+              - zyxel,ex3510b
           - const: brcm,bcm4906
           - const: brcm,bcm4908
           - const: brcm,bcmbca
Signature · 1 line
2.44.2
Acked-by on v1 1/2
#2 lore raw

Re: [PATCH 1/2] dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906

Quoted 8 lines · Sam Edwards

This is a series (EX3510-B0 and EX3510-B1) of residential gateways based on BCM4906, a stripped-down version of the BCM4908 SoC. Although Zyxel's marketing materials call this a "series," the EX3510-B1 appears to be a very minor revision of the EX3510-B0, with only changes that are transparent to software. As far as Linux is concerned, this "series" effectively represents a single model.

Can you use the same email as for SoB?

Best regards,
Krzysztof

#3 lore raw

Re: [PATCH 1/2] dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906

Quoted 11 lines · Krzysztof Kozlowski
Quoted 8 lines · Sam Edwards

This is a series (EX3510-B0 and EX3510-B1) of residential gateways based on BCM4906, a stripped-down version of the BCM4908 SoC. Although Zyxel's marketing materials call this a "series," the EX3510-B1 appears to be a very minor revision of the EX3510-B0, with only changes that are transparent to software. As far as Linux is concerned, this "series" effectively represents a single model.

Can you use the same email as for SoB?

I meant, same for patch author and SoB. How is even possible to generate different data? You had to change it manually, which should make you wondering if this is correct.

Quoted 6 lines

Best regards,
Krzysztof

Best regards,
Krzysztof

#4 lore raw

Re: [PATCH 1/2] dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906

Quoted 11 lines · Krzysztof Kozlowski
Quoted 9 lines · Krzysztof Kozlowski
Quoted 8 lines · Sam Edwards

This is a series (EX3510-B0 and EX3510-B1) of residential gateways based on BCM4906, a stripped-down version of the BCM4908 SoC. Although Zyxel's marketing materials call this a "series," the EX3510-B1 appears to be a very minor revision of the EX3510-B0, with only changes that are transparent to software. As far as Linux is concerned, this "series" effectively represents a single model.

Good day Krzysztof,

Quoted 2 lines
Quoted 2 lines

Can you use the same email as for SoB?

I have sent patches to the LKML from a work email before, but I just double-checked that I am using my personal email for everything here:

$ git show ec8e6d96a05f04 | grep -E 'dt-bindings|Author|Signed'
Author: Sam Edwards <[email protected]>
    dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906
    Signed-off-by: Sam Edwards <[email protected]>
$ grep -E '^From|^Signed'
outgoing-ex3510b/0001-dt-bindings-arm64-bcmbca-Add-Zyxel-EX3510-B-based-on.patch
From ec8e6d96a05f04df00d05dec00df80172d233d8c Mon Sep 17 00:00:00 2001
From: Sam Edwards <[email protected]>
Signed-off-by: Sam Edwards <[email protected]>
$
Quoted 3 lines

I meant, same for patch author and SoB. How is even possible to generate different data? You had to change it manually, which should make you wondering if this is correct.

Hey, on a meta level: I’d appreciate it if we could try to rule out other possibilities before jumping to conclusions. Reading this made me feel accused, and I think framing things collaboratively rather than assigning blame will make it easier for all of us. How about we start with what you’re seeing and work backwards?

Wishing you well,
Sam

Quoted 11 lines
Quoted 7 lines

Best regards,
Krzysztof

Best regards,
Krzysztof

#5 lore raw

Re: [PATCH 1/2] dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906

Quoted 11 lines · Sam Edwards
Quoted 10 lines · Krzysztof Kozlowski
Quoted 8 lines · Krzysztof Kozlowski
Quoted 7 lines · Sam Edwards

This is a series (EX3510-B0 and EX3510-B1) of residential gateways based on BCM4906, a stripped-down version of the BCM4908 SoC. Although Zyxel's marketing materials call this a "series," the EX3510-B1 appears to be a very minor revision of the EX3510-B0, with only changes that are transparent to software. As far as Linux is concerned, this "series" effectively represents a single model.

Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line

Good day Krzysztof,

Quoted 2 lines
Quoted 2 lines

Can you use the same email as for SoB?

I have sent patches to the LKML from a work email before, but I just

That's not what I asked. You can send them from whatever, I asked that commit identity should match SoB in exact way.

Quoted 11 lines

double-checked that I am using my personal email for everything here:

$ git show ec8e6d96a05f04 | grep -E 'dt-bindings|Author|Signed'
Author: Sam Edwards <[email protected]>
    dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906
    Signed-off-by: Sam Edwards <[email protected]>
$ grep -E '^From|^Signed'
outgoing-ex3510b/0001-dt-bindings-arm64-bcmbca-Add-Zyxel-EX3510-B-based-on.patch
From ec8e6d96a05f04df00d05dec00df80172d233d8c Mon Sep 17 00:00:00 2001
From: Sam Edwards <[email protected]>
Signed-off-by: Sam Edwards <[email protected]>

So apply the patch from the mailing list and you will see:

Author: Sam Edwards <[email protected]>

Best regards,
Krzysztof

#6 lore raw

Re: [PATCH 1/2] dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906

Quoted 18 lines · Krzysztof Kozlowski
Quoted 16 lines · Sam Edwards
Quoted 11 lines · Krzysztof Kozlowski
Quoted 9 lines · Krzysztof Kozlowski
Quoted 8 lines · Sam Edwards

This is a series (EX3510-B0 and EX3510-B1) of residential gateways based on BCM4906, a stripped-down version of the BCM4908 SoC. Although Zyxel's marketing materials call this a "series," the EX3510-B1 appears to be a very minor revision of the EX3510-B0, with only changes that are transparent to software. As far as Linux is concerned, this "series" effectively represents a single model.

Good day Krzysztof,

Quoted 1 line
Quoted 1 line
Quoted 19 lines
Quoted 3 lines
Quoted 1 line
Quoted 1 line

Can you use the same email as for SoB?

I have sent patches to the LKML from a work email before, but I just

That's not what I asked. You can send them from whatever, I asked that commit identity should match SoB in exact way.

Quoted 11 lines

double-checked that I am using my personal email for everything here:

$ git show ec8e6d96a05f04 | grep -E 'dt-bindings|Author|Signed'
Author: Sam Edwards <[email protected]>
    dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906
    Signed-off-by: Sam Edwards <[email protected]>
$ grep -E '^From|^Signed'
outgoing-ex3510b/0001-dt-bindings-arm64-bcmbca-Add-Zyxel-EX3510-B-based-on.patch
From ec8e6d96a05f04df00d05dec00df80172d233d8c Mon Sep 17 00:00:00 2001
From: Sam Edwards <[email protected]>
Signed-off-by: Sam Edwards <[email protected]>

Greetings Krzysztof,

Quoted 4 lines

So apply the patch from the mailing list and you will see:

Author: Sam Edwards <[email protected]>

Looks fine to me, those are both set to my personal (non-work) account. The only difference I'm seeing is that the capitalization in my email address is being discarded in the author field, but in light of the case-insensitive nature of email addresses: these are an exact match.

Still, I was interested to see what was affecting the capitalization in one field but not the other, so I did some digging. To answer your previous question: they can differ because they are transported in different ways. Evidently git-am considers a few headers in the email envelope significant (e.g. Subject/From/Date) by default. The envelope's "From:" is what specifies the patch author, while the Signed-off-by tag is just part of the message body. The envelope is unfortunately fair game for modification by various MTAs, which would explain why my patches aren't arriving with my 'From:' email address capitalization intact. When I have time, I'd like to look into what specific hop in the mail path is doing that. Hopefully it's something I can reconfigure, but it might also be out of my hands.

Is there some other difference you're noticing that's too subtle for me to spot? Or is it indeed the capitalization that's the key issue here? If the latter, I want to understand why it's important so I can see if there’s a way to work around it, or if we need to consider other options for getting patches delivered in the preferred format in the future.

COMMITTER: In light of the above, could you kindly add this flag to git-am to fix the capitalization issue: --author="Sam Edwards <[email protected]>"

Quoted 3 lines

Best regards,
Krzysztof

Have a relaxing weekend,
Sam

#7 lore raw

PATCH 2/2 arm64: dts: broadcom: bcmbca: bcm4908: Add DT for Zyxel EX3510-B

In reply to Sam Edwards

Zyxel EX3510-B is a WiFi 6 capable home gateway (family) based on the BCM4906 SoC, with 512MiB of RAM and 512MiB of NAND flash. WiFi support consists of a BCM6710 and a BCM6715 attached to separate PCIe buses.

Add an initial devicetree for this system, with support for:
- Onboard UART (per base dtsi)
- USB (2.0 only; superspeed devices are treated as high-speed due to an unknown cause)
- Both buttons (rear reset, front WPS)
- Almost all LEDs:
- Power (red/green)
- Internet (red/green)
- WAN (green)
- LAN (green; anode is connected to GPIO 13 so currently nonfunctioning)
- USB (green)
- WPS button (red/green)
- Absent in DT: There are 2.4GHz/5.0GHz WiFi status LEDs connected to the WiFi chips instead of the SoC.
- NAND flash
- Embedded Ethernet switch
- Factory-programmed Ethernet MAC address

WiFi cannot be enabled at this time due to Linux lacking drivers for both the PCIe controllers and the PCIe WiFi peripherals.

---
 arch/arm64/boot/dts/broadcom/bcmbca/Makefile  |   1 +
 .../broadcom/bcmbca/bcm4906-zyxel-ex3510b.dts | 197 ++++++++++++++++++
 2 files changed, 198 insertions(+)
 create mode 100644 arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dts
arch/arm64/boot/dts/broadcom/bcmbca/Makefile +1 -0
index 27741b71ba9e..9a8461d91c8c 100644
@@ -2,6 +2,7 @@
 dtb-$(CONFIG_ARCH_BCMBCA) += \
 				bcm4906-netgear-r8000p.dtb \
 				bcm4906-tplink-archer-c2300-v1.dtb \
+				bcm4906-zyxel-ex3510b.dtb \
 				bcm4908-asus-gt-ac5300.dtb \
 				bcm4908-netgear-raxe500.dtb \
 				bcm94908.dtb \
arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dts new file +197 -0

197 lines not on this page · raw message

Signature · 1 line
2.44.2
maintainer
#8 lore raw

Re: [PATCH 2/2] arm64: dts: broadcom: bcmbca: bcm4908: Add DT for Zyxel EX3510-B

Quoted 23 lines · Sam Edwards

Zyxel EX3510-B is a WiFi 6 capable home gateway (family) based on the BCM4906 SoC, with 512MiB of RAM and 512MiB of NAND flash. WiFi support consists of a BCM6710 and a BCM6715 attached to separate PCIe buses.

Add an initial devicetree for this system, with support for:
- Onboard UART (per base dtsi)
- USB (2.0 only; superspeed devices are treated as high-speed due to an unknown cause)
- Both buttons (rear reset, front WPS)
- Almost all LEDs:
- Power (red/green)
- Internet (red/green)
- WAN (green)
- LAN (green; anode is connected to GPIO 13 so currently nonfunctioning)
- USB (green)
- WPS button (red/green)
- Absent in DT: There are 2.4GHz/5.0GHz WiFi status LEDs connected to the WiFi chips instead of the SoC.
- NAND flash
- Embedded Ethernet switch
- Factory-programmed Ethernet MAC address

Quoted 2 lines

WiFi cannot be enabled at this time due to Linux lacking drivers for both the PCIe controllers and the PCIe WiFi peripherals.

On the topic of PCIe, AFAICT Rafal had made an attempt at modifying pcie-brcmstb.c, which is really the same IP, or rather a fork of it. Let me know if you need help in figuring out the programming and we can help with that.

Signature · 1 line
Florian
#9 lore raw
In reply to Sam Edwards
Quoted 31 lines · Sam Edwards

Hello BCMBCA maintainers,

This pair of patches adds an initial DT for the Zyxel EX3510-B "series" based on BCM4906, encompassing the EX3510-B0 and EX3510-B1. As I am not aware of any software-affecting difference between these two, I am calling the "series" one model.

I found the BCM4906/8 support in Linux to be in need of a lot of TLC, and have just sent a few patches necessary to get Linux to boot without crashing on this platform. At a minimum, you will want to apply [1] to resolve a panic related to xHCI not initializing. If you are booting through CFE and want to use the secondary CPU, you will have to apply [2] as well.

There are more patches to come. An issue with the switch driver is preventing the WAN port from operating, for example. I have worked around this locally so I can confirm that the DT I am submitting here is correct, but I will need to clean up my remaining local fixes before they can be sent.

As always, thank you very much for your continued efforts and for your time reviewing these patches.

Best regards,
Sam

[1]: https://lore.kernel.org/lkml/[email protected]/T/
[2]: https://lore.kernel.org/lkml/[email protected]/T/

Sam Edwards (2):
dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906
arm64: dts: broadcom: bcmbca: bcm4908: Add DT for Zyxel EX3510-B

Quoted 11 lines
 .../bindings/arm/bcm/brcm,bcmbca.yaml         |   1 +
 arch/arm64/boot/dts/broadcom/bcmbca/Makefile  |   1 +
 .../broadcom/bcmbca/bcm4906-zyxel-ex3510b.dts | 197 ++++++++++++++++++
 3 files changed, 199 insertions(+)
 create mode 100644 arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dts

--
2.44.2

My bot found new DTB warnings on the .dts files added or changed in this series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings are fixed by another series. Ultimately, it is up to the platform maintainer whether these warnings are acceptable or not. No need to reply unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then make sure dt-schema is up to date:

  pip3 install dtschema --upgrade

New warnings running 'make CHECK_DTBS=y broadcom/bcmbca/bcm4906-zyxel-ex3510b.dtb' for [email protected]:

arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dtb: nand-controller@1800: nand@0:partitions: 'oneOf' conditional failed, one must be fixed:

	'#address-cells', '#size-cells', 'partition@0', 'partition@100000', 'partition@6080000' do not match any of the regexes: 'pinctrl-[0-9]+'
	'#address-cells', '#size-cells', 'partition@0', 'partition@100000', 'partition@6080000' do not match any of the regexes: '^partition-[0-9a-z]+$', 'pinctrl-[0-9]+'
	'fis-index-block' is a required property
	'partitions-table-offset' is a required property
	'#address-cells', '#size-cells', 'partition@0', 'partition@100000', 'partition@6080000' do not match any of the regexes: '^partition-.*$', 'pinctrl-[0-9]+'
	False schema does not allow 1

arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dtb: nand-controller@1800: nand@0:partitions:compatible: 'oneOf' conditional failed, one must be fixed:
['brcm,bcm4908-partitions'] is too short
'fixed-partitions' was expected
'sercomm,sc-partitions' was expected
'arm,arm-firmware-suite' was expected
'brcm,bcm947xx-cfe-partitions' was expected
'linksys,ns-partitions' was expected
'qcom,smem-part' was expected
'redboot-fis' was expected
'tplink,safeloader-partitions' was expected
Unevaluated properties are not allowed ('#address-cells', '#size-cells', 'compatible', 'mac@106a0', 'ranges' were unexpected)
['nvmem-cells'] is too short
'brcm,bcm4908-firmware' was expected
'linksys,ns-firmware' was expected
Unevaluated properties are not allowed ('compatible' was unexpected)
['brcm,bcm4908-firmware'] is too short
from schema $id: http://devicetree.org/schemas/mtd/brcm,brcmnand.yaml#
arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dtb: nand-controller@1800: nand@0: Unevaluated properties are not allowed ('#address-cells', '#size-cells', 'nand-ecc-strength', 'partitions' were unexpected)
from schema $id: http://devicetree.org/schemas/mtd/brcm,brcmnand.yaml#
arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dtb: nand-controller@1800: nand@0:partitions: 'oneOf' conditional failed, one must be fixed:

	'#address-cells', '#size-cells', 'partition@0', 'partition@100000', 'partition@6080000' do not match any of the regexes: 'pinctrl-[0-9]+'
	'#address-cells', '#size-cells', 'partition@0', 'partition@100000', 'partition@6080000' do not match any of the regexes: '^partition-[0-9a-z]+$', 'pinctrl-[0-9]+'
	'fis-index-block' is a required property
	'partitions-table-offset' is a required property
	'#address-cells', '#size-cells', 'partition@0', 'partition@100000', 'partition@6080000' do not match any of the regexes: '^partition-.*$', 'pinctrl-[0-9]+'
	False schema does not allow 1

arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dtb: nand-controller@1800: nand@0:partitions:compatible: 'oneOf' conditional failed, one must be fixed:
['brcm,bcm4908-partitions'] is too short
'fixed-partitions' was expected
'sercomm,sc-partitions' was expected
'arm,arm-firmware-suite' was expected
'brcm,bcm947xx-cfe-partitions' was expected
'linksys,ns-partitions' was expected
'qcom,smem-part' was expected
'redboot-fis' was expected
'tplink,safeloader-partitions' was expected
Unevaluated properties are not allowed ('#address-cells', '#size-cells', 'compatible', 'mac@106a0', 'ranges' were unexpected) ['nvmem-cells'] is too short
'brcm,bcm4908-firmware' was expected
'linksys,ns-firmware' was expected
Unevaluated properties are not allowed ('compatible' was unexpected)
['brcm,bcm4908-firmware'] is too short
from schema $id: http://devicetree.org/schemas/mtd/brcm,brcmnand.yaml#
arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dtb: nand-controller@1800: Unevaluated properties are not allowed ('#address-cells', '#size-cells' were unexpected)
from schema $id: http://devicetree.org/schemas/mtd/brcm,brcmnand.yaml#
arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dtb: nand-controller@1800: nand@0:partitions: 'oneOf' conditional failed, one must be fixed:

	'#address-cells', '#size-cells', 'partition@0', 'partition@100000', 'partition@6080000' do not match any of the regexes: 'pinctrl-[0-9]+'
	'#address-cells', '#size-cells', 'partition@0', 'partition@100000', 'partition@6080000' do not match any of the regexes: '^partition-[0-9a-z]+$', 'pinctrl-[0-9]+'
	'fis-index-block' is a required property
	'partitions-table-offset' is a required property
	'#address-cells', '#size-cells', 'partition@0', 'partition@100000', 'partition@6080000' do not match any of the regexes: '^partition-.*$', 'pinctrl-[0-9]+'
	False schema does not allow 1

arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dtb: nand-controller@1800: nand@0:partitions:compatible: 'oneOf' conditional failed, one must be fixed:
['brcm,bcm4908-partitions'] is too short
'fixed-partitions' was expected
'sercomm,sc-partitions' was expected
'arm,arm-firmware-suite' was expected
'brcm,bcm947xx-cfe-partitions' was expected
'linksys,ns-partitions' was expected
'qcom,smem-part' was expected
'redboot-fis' was expected
'tplink,safeloader-partitions' was expected
Unevaluated properties are not allowed ('#address-cells', '#size-cells', 'compatible', 'mac@106a0', 'ranges' were unexpected) ['nvmem-cells'] is too short
'brcm,bcm4908-firmware' was expected
'linksys,ns-firmware' was expected
Unevaluated properties are not allowed ('compatible' was unexpected)
['brcm,bcm4908-firmware'] is too short
from schema $id: http://devicetree.org/schemas/mtd/nand-controller.yaml#
arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dtb: nand@0: partitions: 'oneOf' conditional failed, one must be fixed:

	'#address-cells', '#size-cells', 'partition@0', 'partition@100000', 'partition@6080000' do not match any of the regexes: 'pinctrl-[0-9]+'
	'#address-cells', '#size-cells', 'partition@0', 'partition@100000', 'partition@6080000' do not match any of the regexes: '^partition-[0-9a-z]+$', 'pinctrl-[0-9]+'
	'fis-index-block' is a required property
	'partitions-table-offset' is a required property
	'#address-cells', '#size-cells', 'partition@0', 'partition@100000', 'partition@6080000' do not match any of the regexes: '^partition-.*$', 'pinctrl-[0-9]+'
	False schema does not allow 1

arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dtb: nand@0: partitions:compatible: 'oneOf' conditional failed, one must be fixed:
['brcm,bcm4908-partitions'] is too short
'fixed-partitions' was expected
'sercomm,sc-partitions' was expected
'arm,arm-firmware-suite' was expected
'brcm,bcm947xx-cfe-partitions' was expected
'linksys,ns-partitions' was expected
'qcom,smem-part' was expected
'redboot-fis' was expected
'tplink,safeloader-partitions' was expected
Unevaluated properties are not allowed ('#address-cells', '#size-cells', 'compatible', 'mac@106a0', 'ranges' were unexpected) ['nvmem-cells'] is too short
'brcm,bcm4908-firmware' was expected
'linksys,ns-firmware' was expected
Unevaluated properties are not allowed ('compatible' was unexpected)
['brcm,bcm4908-firmware'] is too short
from schema $id: http://devicetree.org/schemas/mtd/raw-nand-chip.yaml#
arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dtb: partition@0: Unevaluated properties are not allowed ('ranges' was unexpected)
from schema $id: http://devicetree.org/schemas/mtd/partitions/nvmem-cells.yaml#