On Sat, Mar 09, 2024 at 02:25:38AM +0100, Niklas Söderlund wrote:
> The bindings for Renesas Ethernet AVB are from 2015 and contain some
> oddities that are impossible to get right without breaking existing
> bindings. One such thing is that the MDIO bus properties that should be
> its own node are mixed with the node for the IP for Ethernet AVB.
>
> Instead of a separate node for the MDIO bus,
>
> avb: ethernet@e6800000 {
> compatible = "renesas,etheravb-r8a7795",
> "renesas,etheravb-rcar-gen3";
> reg = <0xe6800000 0x800>, <0xe6a00000 0x10000>;
>
> ...
>
> phy-handle = <&phy0>;
>
> mdio {
> #address-cells = <1>;
> #size-cells = <0>;
>
> phy0: ethernet-phy@0 {
> ...
> };
> };
> };
>
> The Ethernet AVB mix it in one,
>
> avb: ethernet@e6800000 {
> compatible = "renesas,etheravb-r8a7795",
> "renesas,etheravb-rcar-gen3";
> reg = <0xe6800000 0x800>, <0xe6a00000 0x10000>;
>
> ...
>
> phy-handle = <&phy0>;
>
> #address-cells = <1>;
> #size-cells = <0>;
>
> phy0: ethernet-phy@0 {
> ...
> };
> };
This was at one time O.K, and since we don't remove things because
that would break backwards compatibility, its still technically
O.K. It does however lead to problems, so newer drivers have used a
dedicated MDIO node. The yaml i think only documents the use of an
MDIO node. If you want older DT blobs to pass validation, you might
want to add the extra properties to the renesas,etheravb-r8a7795
binding.
You also see some older drivers which have migrated to first look for
an MDIO node and use it if found, and then fallback to the old
scheme. So that is what i would suggest here. You could then convert
all in tree dts files to having an MDIO node, which will make the yaml
validator happy.
Andrew
