[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ab74593d-a3be-4283-ad83-3525cb6d7dd1@amd.com>
Date: Tue, 18 Mar 2025 22:18:46 +0530
From: Rajaganesh Rathinasabapathi <rrathina@....com>
To: Andrew Lunn <andrew@...n.ch>,
Rajaganesh Rathinasabapathi <Rajaganesh.Rathinasabapathi@....com>
Cc: devicetree@...r.kernel.org, openbmc@...ts.ozlabs.org, joel@....id.au,
andrew@...econstruct.com.au, robh+dt@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
Supreeth Venkatesh <supreeth.venkatesh@....com>, jothayot@....com
Subject: Re: [PATCH v3 2/2] ARM:dts:aspeed: Initial device tree for AMD Onyx
Platform
On 3/18/25 19:38, Andrew Lunn wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
>> +&mac3 {
>> + status = "okay";
>> + phy-mode = "rgmii";
>
> Does the PCB have extra long clock lines to insert the 2ns RGMII
> delay? Or are you another victim of aspeeds broken MAC/SCU driver?
>
> Andrew
We're following Aspeed SDK and referred other dts based on ast2600.
I assume Aspeed has moved clock delays to u-boot.
Link: https://lore.kernel.org/lkml/SG2PR06MB23150B3673E58737ABB08D51E6139@SG2PR06MB2315.apcprd06.prod.outlook.com/
Powered by blists - more mailing lists