On 21/07/2017 16:06, Timur Tabi wrote:
> On 7/21/17 8:29 AM, Marc Gonzalez wrote:
>
>> 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 (
On 7/21/17 8:29 AM, Marc Gonzalez wrote:
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 b
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
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 current code supports enabling RGMII RX and TX clock delays.
The unstated assumption is that these settings are disabled by
default at reset, which is not the case.
RX clock delay is enabled at reset. And TX clock delay "survives"
across SW resets. Thus, if the bootloader enables TX clock dela
