From: Richard Genoud <richard.genoud@gmail.com>
To: linux-kernel@vger.kernel.org, Richard Genoud <richard.genoud@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Antoine Tenart <antoine.tenart@bootlin.com>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Yelena Krivosheev <yelena@marvell.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
netdev@vger.kernel.org
Subject: Re: CRC errors between mvneta and macb
Date: Mon, 22 Oct 2018 08:51:55 +0200 [thread overview]
Message-ID: <c24489f6-3b9a-f26b-bc7f-b564d5567294@sorico.fr> (raw)
In-Reply-To: <20181019154439.GC24045@1wt.eu>
Le 19/10/2018 à 17:44, Willy Tarreau a écrit :
> On Fri, Oct 19, 2018 at 05:15:03PM +0200, Richard Genoud wrote:
>> When there's a CRC error, the TXCLK has its polarity inverted...
>> That's a clue !
>>
>> But this TXCLK (25MHz) is not used on the g35-ek.
>> Only the REFCLK/XT2 (50MHz) is used to synchronise the PHY and the macb.
>> So I guess that the TXCLK has a role to play to generate TX+/TX-
>
> Well, just a stupid idea, maybe when this signal is inverted, the TX+/TX-
> are desynchronized by half a clock and are not always properly interpreted
> on the other side ?
>
> Willy
>
I must admit that I'm not familiar with the PHY internals, I'll have to
dig into that.
Richard.
next prev parent reply other threads:[~2018-10-22 6:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 15:15 CRC errors between mvneta and macb Richard Genoud
2018-10-19 15:44 ` Willy Tarreau
2018-10-22 6:51 ` Richard Genoud [this message]
2018-10-22 15:15 ` Richard Genoud
2018-10-22 16:34 ` Willy Tarreau
2018-10-23 6:56 ` Richard Genoud
2018-10-22 18:19 ` Andrew Lunn
2018-10-23 6:58 ` Richard Genoud
2018-10-23 12:37 ` Richard Genoud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c24489f6-3b9a-f26b-bc7f-b564d5567294@sorico.fr \
--to=richard.genoud@gmail.com \
--cc=antoine.tenart@bootlin.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yelena@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).