On Wed, Aug 24, 2022 at 03:57:12PM +0530, SyncMonk Technologies wrote:
> adding alternate master support for linuxptp
>
> A PTP Master Clock, which is not the Best Master,
> may act as a master with the Alternate Master flag
> set on the messages it sends.
> Need to support Alternate Master, including using
> Slave Event Monitoring channel for the
> alternate connections (to pass along timestamps to external servo).
> See ITU-T G.8275.2 Appendix III & V.
The conditions under which a port may transmit Announce with the
alternateMasterFlag are clearly laid in 1588:
A PTP Port, PTP Port-A not in the MASTER state, shall transmit
multicast Announce messages when the number of other PTP Ports
that:
- Are currently transmitting qualified (see 9.3.2.5) Announce
messages, with flagField.alternateMasterFlag TRUE, that are being
received by PTP Port-A, and
- Would be chosen using the best master algorithm as best master in
preference to PTP Port-A,
- Is less than the value of
alternateMasterPortDS.numberOfAlternateMasters.
The code in this patch series does not conform to 1588, and so I won't
consider merging it.
Sorry,
Richard
_______________________________________________
Linuxptp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
