[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YrawUa4VcRrMvNJf@lunn.ch>
Date: Sat, 25 Jun 2022 08:50:57 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Peter Geis <pgwipeout@...il.com>
Cc: Sebastian Reichel <sebastian.reichel@...labora.com>,
Giuseppe Cavallaro <peppe.cavallaro@...com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Jose Abreu <joabreu@...opsys.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
arm-mail-list <linux-arm-kernel@...ts.infradead.org>,
devicetree <devicetree@...r.kernel.org>,
David Wu <david.wu@...k-chips.com>, kernel@...labora.com
Subject: Re: [PATCH 1/3] net: ethernet: stmmac: dwmac-rk: Disable delayline
if it is invalid
> The driver already sets the delays to 0 in case of the rgmii-id modes.
> 0 is disabled, even in this patch. The only thing this patch does is
> change the behavior when the delays are not set. If the rx delays
> should be 0, they should be defined as 0 in the device tree. There is
> rgmii-rxid for a reason as well, but if they are setting the rx delay
> to 0 with rgmii that implies this hardware is fundamentally broken.
Or the delay is implemented by longer tracks on the PCB. It happens
sometimes, but not very often.
Andrew
Powered by blists - more mailing lists