[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221209125611.m5cp3depjigs7452@skbuf>
Date: Fri, 9 Dec 2022 14:56:11 +0200
From: Vladimir Oltean <olteanv@...il.com>
To: Horatiu Vultur <horatiu.vultur@...rochip.com>
Cc: Michael Walle <michael@...le.cc>, Steen.Hegelund@...rochip.com,
UNGLinuxDriver@...rochip.com, daniel.machon@...rochip.com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
lars.povlsen@...rochip.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
pabeni@...hat.com, richardcochran@...il.com
Subject: Re: [PATCH net-next v3 4/4] net: lan966x: Add ptp trap rules
On Fri, Dec 09, 2022 at 01:58:57PM +0100, Horatiu Vultur wrote:
> > Does it also work out of the box with the following patch if
> > the interface is part of a bridge or do you still have to do
> > the tc magic from above?
>
> You will still need to enable the TCAM using the tc command to have it
> working when the interface is part of the bridge.
FWIW, with ocelot (same VCAP mechanism), PTP traps work out of the box,
no need to use tc. Same goes for ocelot-8021q, which also uses the VCAP.
I wouldn't consider forcing the user to add any tc command in order for
packet timestamping to work properly.
Powered by blists - more mailing lists