This is the reason synce4l (based on an ITU-T physical layer protocol, G.8264) should be separate from linuxptp project and be it's own standalone project; so that it does NOT get confused with L1_SYNC TLV from IEEE 1588-2019 (if/when it gets added to linuxptp). The HA profile's use of the physical layer clock is not the same as ITU-T definition of SyncE.
This is not to say there is no interaction between synce4l and ptp4l to support the ITU-T profiles that have physical layer assistance, but the two protocols themselves are mutually exclusive. Also, similar to the PHC to abstract the hardware for user space programs, I would suspect a similar SyncE Hardware Clock infrastructure will be needed in Linux to allow for abstraction of hardware used by synce4l (i.e. as this project matures to meet the full recommendations in G.8264 and, as required, G.781). Greg Greg Armstrong Principal System Architect, Timing Products Division Renesas Electronics Canada Limited Mobile: 1-613-218-9373 -----Original Message----- From: Miroslav Lichvar <mlich...@redhat.com> Sent: May 31, 2022 10:07 AM To: Richard Cochran <richardcoch...@gmail.com> Cc: piotr.kwapulin...@intel.com; anatolii.gerasyme...@intel.com; andrzej.saw...@intel.com; linuxptp-devel@lists.sourceforge.net Subject: Re: [Linuxptp-devel] [PATCH 00/11] synce4l: add software for Synchronous Ethernet On Thu, May 26, 2022 at 10:51:01AM -0700, Richard Cochran wrote: > On Mon, May 02, 2022 at 11:05:54AM +0200, Arkadiusz Kubalewski wrote: > > synce4l is a software implementation of Synchronous Ethernet > > (Sync-E) according to ITU-T Recommendation G.8264. The design goal > > is to provide logic to supported hardware by processing Ethernet > > Synchronization Messaging Channel (ESMC) and control Digital Phase > > Locked Loop (DPLL) clock on Network Card Interface (NIC). > > The bulk of this is a new, stand alone program. One comment that I > received off list questioned whether this program should be part of > linuxptp, or does it deserve its own project? synce4l as submitted doesn't share much with the rest of linuxptp, but that could change with support for the L1_SYNC TLV from 1588-2019. I think it would need to be handled by ptp4l itself, or at least by something communicating with ptp4l over UDS. -- Miroslav Lichvar _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Flinuxptp-devel&data=05%7C01%7Cgreg.armstrong.uw%40renesas.com%7Cece84de7784b43f32e4908da430f2242%7C53d82571da1947e49cb4625a166a4a2a%7C0%7C0%7C637896029522150943%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9fqPCkzVsPbjxXg%2Bn2%2FwKztjJiWq5RXsRUEXmHTC4JA%3D&reserved=0 _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
