Hi Miroslav, 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? > The Announce message coming over the virtual port helps us to keep a track of the quality and availability of the external source. TS2PHC will be sending the information about the external source over the virtual port to PTP and will not need any other external intervention using PMC. In future, we may extend this to send sync messages to ptp4l to send the timing information.
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. There can be multiple virtual ports and the configuration will be the same as we have for the ports with transport type as vport. This will be used in IWF, so there can be multiple translations based on profiles if needed. Yes, for the Announce message from external ports we do not need multiple instances so we have placed it at the device level. We are working on the patch which will address Richard's concern regarding the hardcoded configuration parameters and will make clear the use of multiple virtual ports. Yes, with virtual ports we need to have "delay_mechanism" as NO_MECHANISM as these are one-way communication channels. Thanks, Devasish Dey SyncMonk Technologies. On Mon, 5 Sept 2022 at 16:21, Miroslav Lichvar <mlich...@redhat.com> wrote: > 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 >
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
