[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170102113155.GA16373@localhost.localdomain>
Date: Mon, 2 Jan 2017 12:31:55 +0100
From: Richard Cochran <richardcochran@...il.com>
To: Rafal Ozieblo <rafalo@...ence.com>
Cc: Andrei Pistirica <andrei.pistirica@...rochip.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"nicolas.ferre@...el.com" <nicolas.ferre@...el.com>,
"harinikatakamlinux@...il.com" <harinikatakamlinux@...il.com>,
"harini.katakam@...inx.com" <harini.katakam@...inx.com>,
"punnaia@...inx.com" <punnaia@...inx.com>,
"michals@...inx.com" <michals@...inx.com>,
"anirudh@...inx.com" <anirudh@...inx.com>,
"boris.brezillon@...e-electrons.com"
<boris.brezillon@...e-electrons.com>,
"alexandre.belloni@...e-electrons.com"
<alexandre.belloni@...e-electrons.com>,
"tbultel@...elsurmer.com" <tbultel@...elsurmer.com>
Subject: Re: [RFC PATCH net-next v4 1/2] macb: Add 1588 support in Cadence
GEM.
On Mon, Jan 02, 2017 at 09:36:10AM +0000, Rafal Ozieblo wrote:
> According Cadence Hardware team:
> "It is just that some customers prefer to have the time in the descriptors as that is provided per frame.
> The registers are simply overwritten when a new event frame is transmitted/received and so software could miss it."
> The question is are you sure that you read timestamp for current frame? (not for the next frame).
AFAICT, having the time stamp in the descriptor is not universally
supported. Looking at the Xilinx Zynq 7000 TRM, I can't find any
mention of this.
This Cadence IP core is a complete disaster.
Unless someone can tell us how this IP works in all of its
incarnations, this series is going nowhere.
Thanks,
Richard
Powered by blists - more mailing lists