On Wed, Mar 16, 2022 at 02:02:08PM +0000, Modrzejewski, Pawel via Linuxptp-devel wrote: > > The servo state is an internal variable has no relevance to outside > > observers. > > Apparently, me and Dale Smith are not the only ones interested in PTP servo > > state. See > > https://docs.baslerweb.com/precision-time-protocol#additional-parameters > > (Basler GigE cameras). > > PtpServoStatus: Indicates the state of the clock servo, i.e., the state of > > the PTP clock synchronization. If the state is Locked, the clock of the > > current device is successfully synchronized with the master clock. In all > > other cases, the state is Unknown. > > Hi, > > I'm also using custom non-portable management option to query the servo(s) > state in my setup. What is more, I've added not only 'get but also 'set' > option and my phc2sys sends its servo state to ptp4l and you can check both > servos status with just one query. > You may also check this thread: > https://sourceforge.net/p/linuxptp/mailman/message/37414815/ (servo: allows > servo state transition back from S3 to S2) where we discussed possibility to > change servo state back to S2 (can potentially cause some issues).
And this is why reporting s3 doesn't mean much at all. Thanks, Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
