[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a01e7faf-4cfc-dc04-44ea-2b1e0724778b@wolfvision.net>
Date: Thu, 29 Jul 2021 11:07:50 +0200
From: Michael Riesch <michael.riesch@...fvision.net>
To: Andrew Lunn <andrew@...n.ch>, Peter Geis <pgwipeout@...il.com>
Cc: devicetree@...r.kernel.org,
arm-mail-list <linux-arm-kernel@...ts.infradead.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
Heiko Stuebner <heiko@...ech.de>,
Liang Chen <cl@...k-chips.com>, Simon Xue <xxm@...k-chips.com>
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: rk3568-evb1-v10: add ethernet
support
Hello Andrew, Peter,
On 7/28/21 10:37 PM, Andrew Lunn wrote:
>> Generally all rockchip boards use this value instead of the rgmii_id,
>> I imagine because it's more consistent to tune here than the hit or
>> miss support of the phy drivers.
>
> Most PHY drivers actually implement it correctly, since by default,
> most systems get the PHY to do the delays.
>
> But if most Rockchip boards do it this way, there is a lot to be said
> for consistence, so this is fine by me.
I have tested a dts without the delays and with phy-mode = "rgmii-id"
and it seems to work just fine.
Although consistency with other Rockchip boards is something one should
consider, I think I'll go along the "rgmii-id" path since this seems to
be a more general convention.
Thanks for your comments, I'll submit a v2.
Regards, Michael
Powered by blists - more mailing lists