[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221206104827.corkkthxmypegja7@skbuf>
Date: Tue, 6 Dec 2022 12:48:27 +0200
From: Vladimir Oltean <olteanv@...il.com>
To: Christian Eggers <ceggers@...i.de>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
Arun Ramadoss <arun.ramadoss@...rochip.com>,
woojung.huh@...rochip.com, UNGLinuxDriver@...rochip.com,
andrew@...n.ch, vivien.didelot@...il.com, f.fainelli@...il.com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, linux@...linux.org.uk,
Tristram.Ha@...rochip.com, richardcochran@...il.com
Subject: Re: [Patch net-next v2 01/13] net: dsa: microchip: ptp: add the
posix clock support
On Tue, Dec 06, 2022 at 11:37:26AM +0100, Christian Eggers wrote:
> > v1 -> v2
> > - Deleted setting 8021_1as bit and added P2P bit in ksz_ptp_clock_register()
>
> did I miss the discussion about this change? I thought that the first goal is
> to use KSZ switches as a boundary clock which implies using the 802.1AS feature.
>
> Using the KSZ in P2P transparent clock mode IMHO requires writing the peer delays
> into switch registers (which needs to be implemented in a companion
> application/script for ptp4p).
>
> As far as I remember, there is also no support using ptp4l with 1-step transparent
> clock switches.
If it was in response to something I said, I just asked to add a comment
as to what the 802.1AS bit does, not to delete it...
Powered by blists - more mailing lists