Thread (19 messages) 19 messages, 5 authors, 2017-01-11

[RFC PATCH net-next v4 1/2] macb: Add 1588 support in Cadence GEM.

From: richardcochran@gmail.com (Richard Cochran)
Date: 2017-01-02 16:14:07
Also in: lkml, netdev

On Mon, Jan 02, 2017 at 03:47:07PM +0100, Nicolas Ferre wrote:
Le 02/01/2017 ? 12:31, Richard Cochran a ?crit :
quoted
This Cadence IP core is a complete disaster.
Well, it evolved and propose several options to different SoC
integrators. This is not something unusual...
I suspect as well that some other network adapters have the same
weakness concerning PTP timestamp in single register as the early
revisions of this IP.
It appears that this core can neither latch the time on read or write,
or even latch time stamps.  I have worked with many different PTP HW
implementations, even early ones like on the ixp4xx, and it is no
exaggeration to say that this one is uniquely broken.
I suspect that Rafal tend to jump too quickly to the latest IP revisions
and add more options to this series: let's not try to pour too much
things into this code right now.
Why can't you check the IP version in the driver?

And is it really true that the registers don't latch the time stamps,
as Rafal said?  If so, then we cannot accept the non-descriptor driver
version, since it cannot possibly work correctly.

Thanks,
Richard
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help