arm64: dts: ti: k3-am62: MDIO pinmux should belong to the MDIO node
authorAndrew Davis <afd@ti.com>
Tue, 18 Oct 2022 21:15:29 +0000 (16:15 -0500)
committerNishanth Menon <nm@ti.com>
Fri, 28 Oct 2022 13:15:12 +0000 (08:15 -0500)
Although usually integrated as a child of an Ethernet controller, MDIO
IP has an independent pinout. This pinout should be controlled by
the MDIO node (so if it was to be disabled for instance, the pinmux
state would reflect that).

Move the MDIO pins pinmux to the MIDO nodes.

Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Bryan Brattlof <bb@ti.com>
Link: https://lore.kernel.org/r/20221018211533.21335-7-afd@ti.com
arch/arm64/boot/dts/ti/k3-am625-sk.dts

index 197d329a6082761f7235b19f98af548a2f126b50..318ec805ff54d199c1622cc93d6e8ee81ea48597 100644 (file)
 
 &cpsw3g {
        pinctrl-names = "default";
-       pinctrl-0 = <&main_mdio1_pins_default
-                    &main_rgmii1_pins_default
+       pinctrl-0 = <&main_rgmii1_pins_default
                     &main_rgmii2_pins_default>;
 };
 
 };
 
 &cpsw3g_mdio {
+       pinctrl-names = "default";
+       pinctrl-0 = <&main_mdio1_pins_default>;
+
        cpsw3g_phy0: ethernet-phy@0 {
                reg = <0>;
                ti,rx-internal-delay = <DP83867_RGMIIDCTL_2_00_NS>;