[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <db666f79-5ee3-f136-527e-aeb9cc6425b7@sigmadesigns.com>
Date: Fri, 21 Jul 2017 15:29:32 +0200
From: Marc Gonzalez <marc_gonzalez@...madesigns.com>
To: Timur Tabi <timur@...eaurora.org>,
Florian Fainelli <f.fainelli@...il.com>,
Andrew Lunn <andrew@...n.ch>, Mans Rullgard <mans@...sr.com>,
Martin Blumenstingl <martin.blumenstingl@...il.com>,
Grygorii Strashko <grygorii.strashko@...com>,
Fabio Estevam <fabio.estevam@....com>,
Zefir Kurtisi <zefir.kurtisi@...atec.com>,
Daniel Mack <zonque@...il.com>
CC: netdev <netdev@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
"David S. Miller" <davem@...emloft.net>,
Thibaud Cornic <thibaud_cornic@...madesigns.com>,
Mason <slash.tmp@...e.fr>
Subject: Re: [PATCH v2 1/4] net: phy: at803x: Document RGMII RX and TX clock
delay issues
On 21/07/2017 15:20, Timur Tabi wrote:
> On 7/21/17 6:25 AM, Marc Gonzalez wrote:
>
>> + * NB: This code assumes that RGMII RX clock delay is disabled
>> + * at reset, but actually, RX clock delay is enabled at reset.
>
> Could we change this to say, "RX clock delay is enabled at reset on some
> systems."? Otherwise, it implies that the code is wrong 100% of the
> time and should be fixed, not documented.
I don't understand what you're saying.
It is a correct observation that the code enabling
RGMII RX clock delay is a NOP, since that bit will
always be set at that point.
The spec for the 8035 (I haven't checked for 8030 and 8031,
is that what you meant by "other systems"?) states that
Sel_clk125m_dsp, which is described as:
"Control bit for rgmii interface rx clock delay"
is 1 after HW reset, 1 after SW reset.
So my statement "RX clock delay is enabled at reset"
is universally true. It's not just on some systems.
What am I missing?
Regards.
Powered by blists - more mailing lists