Message ID | 20241213145037.3784931-4-ninad@linux.ibm.com (mailing list archive) |
---|---|
State | New |
Headers | show |
Series | DTS updates for system1 BMC | expand |
> +&mac0 { > + status = "okay"; > + > + phy-mode = "rgmii-rxid"; Why is everybody getting RGMII wrong this week? Do you have an extra long clock line on the PCB for the TX clock? > + phy-handle = <ðphy0>; > + > + pinctrl-names = "default"; > + pinctrl-0 = <&pinctrl_rgmii1_default>; > +}; > + > &mac2 { > status = "okay"; > + > + phy-mode = "rgmii"; Do you have extra long clock lines on the PCB for both Rx and Tx clock? I suspect you don't and the RGMII delays are messed up somehow. Andrew
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts index db4b9fb674fe..775a95470f5c 100644 --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dts @@ -425,14 +425,42 @@ &lpc_ctrl { memory-region = <&flash_memory>; }; +&mdio0 { + status = "okay"; + + ethphy0: ethernet-phy@0 { + compatible = "ethernet-phy-ieee802.3-c22"; + reg = <0>; + }; +}; + +&mdio2 { + status = "okay"; + + ethphy2: ethernet-phy@0 { + compatible = "ethernet-phy-ieee802.3-c22"; + reg = <0>; + }; +}; + +&mac0 { + status = "okay"; + + phy-mode = "rgmii-rxid"; + phy-handle = <ðphy0>; + + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_rgmii1_default>; +}; + &mac2 { status = "okay"; + + phy-mode = "rgmii"; + phy-handle = <ðphy2>; + pinctrl-names = "default"; - pinctrl-0 = <&pinctrl_rmii3_default>; - clocks = <&syscon ASPEED_CLK_GATE_MAC3CLK>, - <&syscon ASPEED_CLK_MAC3RCLK>; - clock-names = "MACCLK", "RCLK"; - use-ncsi; + pinctrl-0 = <&pinctrl_rgmii3_default>; }; &mac3 {