On Fri, Sep 02, 2022 at 12:26:11PM +0530, SyncMonk Technologies wrote: > Virtual PTP port is for unidirectional tranfer of phase/time interface > on a PTP clock. > When associated with an external input signal, a virtual PTP port allows > this external interface to participate in the PTP protocol. > As an input, this external port can participate in the source selection > with an associated virtual Erbest using the associated virtual PTP port. > > As per G.8275 (Annex-B) including virtual PTP ports on a PTP clock. This > virtual port will be used to support Assisted Partial Timing Support > (APTS), Inter Working Function (IWF) between different clock_domains.
Can you please describe advantages of this approach over using the existing GRANDMASTER_SETTINGS_NP management message and/or a new management message that can set all values needed for the telecom profile? For APTS, ts2phc could control ptp4l and for IWF a clientOnly ptp4l instance could control a serverOnly instance. If I understand it correctly, the virtual port will not be used for synchronization and there cannot be multiple virtual ports as their sources wouldn't know when they are in control of the clock. -- Miroslav Lichvar _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
