[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-netdev
Subject:    Ethernet binding: broken validation parsing of #nvmem-cell-cells ?
From:       Rafał Miłecki <zajec5 () gmail ! com>
Date:       2024-01-09 10:03:26
Message-ID: bdf7751b-0421-485d-8382-26c084f09d7d () gmail ! com
[Download RAW message or body]

Hi,

I'm playing with "dtbs_check" and I stuck on following errors:

arch/arm/boot/dts/broadcom/bcm47094-luxul-xwr-3150-v1.dtb: ethernet@24000: \
                nvmem-cells: [[9], [0]] is too long
         from schema $id: http://devicetree.org/schemas/net/ethernet-controller.yaml#
arch/arm/boot/dts/broadcom/bcm47094-luxul-xwr-3150-v1.dtb: ethernet-switch@18007000: \
                ports:port@4:nvmem-cells: [[9], [5]] is too long
         from schema $id: http://devicetree.org/schemas/net/dsa/brcm,b53.yaml#


Context:

nvram@1eff0000 {
	compatible = "brcm,nvram";
	reg = <0x1eff0000 0x10000>;

	et0macaddr: et0macaddr {
		#nvmem-cell-cells = <1>;
	};
};

&gmac0 {
	nvmem-cells = <&et0macaddr 0>;
	nvmem-cell-names = "mac-address";
};


The validation error comes from ethernet-controller.yaml which contains:

nvmem-cells:
   maxItems: 1
   description:
     Reference to an nvmem node for the MAC address


If I'm not mistaken <&et0macaddr 0> gets treated as two items.

Can someone tell me what's going on here and help me with solving it,
please? I would expect it to be sth trivial but I can't see any obvious
mistake.

-- 
Rafał Miłecki


[prev in list] [next in list] [prev in thread] [next in thread]