> -----Original Message-----
> From: Miroslav Lichvar <mlich...@redhat.com>
> Sent: Monday, March 15, 2021 9:57 AM
> To: linuxptp-devel@lists.sourceforge.net
> Subject: [Linuxptp-devel] SyncE support
>
> As I understand it, there is currently no explicit support for SyncE
> in the mainline kernel and linuxptp. For example, there is no access
> to the Synchronization Status Message (SSM), so ptp4l cannot know if
> SyncE is active on a port.
>
Right, this appears to be the general case today
> IIRC some people use SyncE with linuxptp by disabling the frequency
> control. I assume they set up everything manually with some 3rd party
> HW-specific tools using custom ioctls, or maybe it's just a
> client-only use case for linuxptp.
>
I think the only examples I've seen were client only...
> There seems to be a growing interest for SyncE, but it's not clear to
> me how the functionality needed for controlling and monitoring SyncE
> is supposed to be split between the firmware, driver, kernel, and
> ptp4l.
Right. I've heard a few folks here talking about it, but I don't know the plans
off hand.
Given that some parts of it are device specific, it would seem to me like we
need some extensions of the PTP interface that drivers which support SyncE
hardware could implement, and then we could extend the LinuxPTP stack to
include monitoring synce, perhaps as part of ptp4l itself or as part of a
separate application?
>
> In 1588-2019 there is an L1_SYNC TLV specified. Does anyone know what
> is actually needed for the kernel and linuxptp to support it properly,
> e.g. on a boundary clock?
>
> Any pointers?
>
> --
> Miroslav Lichvar
>
>
>
> _______________________________________________
> Linuxptp-devel mailing list
> Linuxptp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
