[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <327df2cb-a0ad-c272-9b03-066d16ac14b6@ti.com>
Date: Tue, 5 Jun 2018 16:18:22 -0500
From: Grygorii Strashko <grygorii.strashko@...com>
To: Andrew Lunn <andrew@...n.ch>
CC: Ilias Apalodimas <ilias.apalodimas@...aro.org>,
Ivan Vecera <ivecera@...hat.com>,
Jiri Pirko <jiri@...nulli.us>, <netdev@...r.kernel.org>,
<ivan.khoronzhuk@...aro.org>, <nsekhar@...com>,
<francois.ozog@...aro.org>, <yogeshs@...com>, <spatton@...com>
Subject: Re: [PATCH 0/4] RFC CPSW switchdev mode
On 06/02/2018 07:08 PM, Andrew Lunn wrote:
> On Sat, Jun 02, 2018 at 06:28:22PM -0500, Grygorii Strashko wrote:
>
> Hi Grygorii
>
> I'm just picking out one thing here... there is lots more good stuff here.
>
>> Additional headache is PTP: we have on PHC, but both external interfaces P1/P2
>> can timestamp packets.
>
> This should not be a problem. The Marvell switches have one PHC, but
> each port can time stamp packets using this counter. Each port has its
> own receive and transmit time stamp registers. So i don't think this
> will cause you problems.
I hope you are right - question is always in number of available options
and which one to select - and, most important, explain it to the end user :(
For example:
phc_index is returned as part of .get_ts_info() = cpsw_get_ts_info(),
so which intf should return phc_index?
Still not tested, so jut hope ...
--
regards,
-grygorii
Powered by blists - more mailing lists