On Mon, Sep 05, 2022 at 05:53:08PM +0530, Devasish Dey wrote: > 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.
That information could be send also as a management message, which I think would be the more obvious solution, so I'm trying to understand the advantage here. > In future, > we may extend this to send sync messages to ptp4l to send the timing > information. To enable synchronization between two different PHCs? How would that work without hardware timestamping? > 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. Multiple translations working at the same time? On the same clock? It's not clear to me how would you prevent two things from controlling the same clock at once. With a management message you could be monitoring the state (as phc2sys does for instance), but with an announce and/or sync message you won't know what is happening at the other side. -- Miroslav Lichvar _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
