On Wed, Aug 24, 2022 at 04:32:19PM +0530, SyncMonk Technologies wrote: > Adding virtual PTP port support > As per G.8275 (Annex-B) including virtual PTP ports on a PTP clock. This > virtual port will be used to support APTS, IWF between different > clock_domains.
Please name the patchset correctly - it does not add the APTS support at all. Only a communication channel between different tools. Can you explain the big picture of this implementation? What will be used as the underlying PTP clock for that APTS implementation? What clock properties will be communicated with this implementation? The biggest challenge of APTS implementation is to know which clock is synchronized to what. I.e. you need to know if the ts2phc receives valid PPS signals from the GNSS to make the right decision. How this can be achieved using this infrastructure? The other one is to provide enough PHCs to the device. What is ts2phc using here vs the ptp4l that will make the decision on electing the right source clock? I took a look at the linkedin links you sent, but they don't explain it. Regards Maciek _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
