[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6a3d7eb4-c091-437f-98f8-2b8577e539a7@lunn.ch>
Date: Fri, 22 Aug 2025 02:11:55 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Jacky Chou <jacky_chou@...eedtech.com>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
joel@....id.au, andrew@...econstruct.com.au,
howard_chiu@...eedtech.com, arnd@...db.de, andrew+netdev@...n.ch,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [net] ARM: dts: aspeed: ast2600-evb: Correct phy-mode to rgmii-id
On Thu, Aug 21, 2025 at 01:25:55PM +0800, Jacky Chou wrote:
> According to the latest ethernet-controller.yaml.
> Since there is no RGMII delay on AST2600 EVB, the phy-mode property of all
> MACs change to "rgmii-id" mode.
> @@ -123,7 +123,7 @@ ethphy3: ethernet-phy@0 {
> &mac0 {
> status = "okay";
>
> - phy-mode = "rgmii-rxid";
> + phy-mode = "rgmii-id";
> phy-handle = <ðphy0>;
How does this change actually work?
I could imaging such a change as part of a patchset which changes the
MAC driver, and how it handles RGMII delays. But on its own, how does
this not break the board?
Andrew
Powered by blists - more mailing lists