The nvmem-cells and nvmem-cell-names properties are used to supply a
MAC address to the brcmfmac wireless controller. Nodes such as
bcm4709-linksys-ea9200.dts fail dtbs_check with:

    Unevaluated properties are not allowed ('nvmem-cell-names',
    'nvmem-cells' were unexpected)

nvmem-consumer.yaml cannot be referenced from the common
network-class.yaml because it does not constrain the number of entries
or their names, and not all network devices use the same cell names.
Each binding that uses nvmem must therefore define its own
nvmem-cells/nvmem-cell-names constraints, like ethernet-controller.yaml
and qca,ath9k.yaml already do.

Add the single-cell, mac-address-only constraints to the
brcm,bcm4329-fmac binding.

Assisted-by: opencode:deepseek-v4-flash-free
Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
 v2: don't use nvmem-consumer.yaml
 .../bindings/net/wireless/brcm,bcm4329-fmac.yaml           | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml b/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml
index 81fd3e37452a..88d0099871b1 100644
--- a/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml
+++ b/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml
@@ -57,6 +57,13 @@ properties:
           - pci14e4,4434  # BCM4388
           - pci14e4,449d  # BCM43752
 
+  nvmem-cells:
+    maxItems: 1
+    description: Reference to an nvmem node for the MAC address
+
+  nvmem-cell-names:
+    const: mac-address
+
   reg:
     description: SDIO function number for the device (for most cases
       this will be 1) or PCI device identifier.
-- 
2.55.0

On 11/08/2026 21:28, Rosen Penev wrote:
> The nvmem-cells and nvmem-cell-names properties are used to supply a
> MAC address to the brcmfmac wireless controller. Nodes such as
> bcm4709-linksys-ea9200.dts fail dtbs_check with:
> 
>      Unevaluated properties are not allowed ('nvmem-cell-names',
>      'nvmem-cells' were unexpected)
> 
> nvmem-consumer.yaml cannot be referenced from the common
> network-class.yaml because it does not constrain the number of entries
> or their names, and not all network devices use the same cell names.
> Each binding that uses nvmem must therefore define its own
> nvmem-cells/nvmem-cell-names constraints, like ethernet-controller.yaml
> and qca,ath9k.yaml already do.
> 
> Add the single-cell, mac-address-only constraints to the
> brcm,bcm4329-fmac binding.
> 
> Assisted-by: opencode:deepseek-v4-flash-free

Probably for this v2 it is better to say:

Suggested-by: Rob Herring <robh@kernel.org>

> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
>   v2: don't use nvmem-consumer.yaml
>   .../bindings/net/wireless/brcm,bcm4329-fmac.yaml           | 7 +++++++
>   1 file changed, 7 insertions(+)