On Mon, Sep 05, 2022 at 02:37:13PM +0200, Miroslav Lichvar wrote: > 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.
Presently, ts2phc is "open loop" with no knowledge of the port states. As a result, it can only work with the ptp4l "free_running" option enabled. phc2sys in "automatic" mode monitors the port states in order to determine how to use CLOCK_REALTIME. So both of these are setups are a bit clunky, because the interaction with the PTP network is only implicitly defined. I can imagine that allowing an Announce messages on the UDS port and letting the UDS port participate in BMCA might make the whole system easier to understand/configure. For this we would need: - proper BMCA logic in phc2sys and ts2phc - configuration of relevant management attributes in phc2sys and ts2phc Thanks, Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
