[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <26dec4b7-0c6d-4e8e-9df6-d644191e767f@lunn.ch>
Date: Mon, 13 Jan 2025 15:38:43 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Ninad Palsule <ninad@...ux.ibm.com>
Cc: Jacky Chou <jacky_chou@...eedtech.com>,
"andrew+netdev@...n.ch" <andrew+netdev@...n.ch>,
"andrew@...econstruct.com.au" <andrew@...econstruct.com.au>,
"conor+dt@...nel.org" <conor+dt@...nel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"eajames@...ux.ibm.com" <eajames@...ux.ibm.com>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"joel@....id.au" <joel@....id.au>,
"krzk+dt@...nel.org" <krzk+dt@...nel.org>,
"kuba@...nel.org" <kuba@...nel.org>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
"linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"minyard@....org" <minyard@....org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"openipmi-developer@...ts.sourceforge.net" <openipmi-developer@...ts.sourceforge.net>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"ratbert@...aday-tech.com" <ratbert@...aday-tech.com>,
"robh@...nel.org" <robh@...nel.org>
Subject: Re: 回覆: 回覆: 回覆: [PATCH v2 05/10] ARM: dts: aspeed:
system1: Add RGMII support
On Mon, Jan 13, 2025 at 08:26:08AM -0600, Ninad Palsule wrote:
> Hi Jacky,
>
> On 1/13/25 00:22, Jacky Chou wrote:
> > Hi Ninad,
> >
> > > Thanks. When are you planning to push this change? I might need to hold on to
> > > mac changes until then.
> > Yes. We have a plan to push the patch about RGMII delay configuration.
> > Currently, I try to align our SDK to kernel.
>
> Thanks. What will be the "phy-mode" value after you make these changes?
>
> Will it be "rgmii-id" for MAC1..4?
It should be.
> If that is the case then I can test it with current configuration which may
> add extra delays in the RX from PHY side.
I would then expect traffic will not flow correctly, and your see CRC
errors, because of double delays. It is however a useful test, because
if it does somehow work, it probably means the PHY driver is also
broken with its handling of delays. I don't know what PHY driver you
are using, but those in mainline should be correct, it is something i
try to review carefully.
Andrew
Powered by blists - more mailing lists