Dear All, I would like to advise that a transition from S3 (stable_lock) -> S2 (lock) can create issues with Transient Noise or Transfer Noise behaviours when write phase mode is also used. I tried to introduce this transition in the past, but I was unable to choose the best threshold.
In my opinion, any patch should be tested wrt ITU-T G8273.2. ciao luigi Il giorno gio 17 feb 2022 alle ore 03:08 Richard Cochran < richardcoch...@gmail.com> ha scritto: > On Mon, Jan 10, 2022 at 01:15:21PM +0000, Modrzejewski, Pawel via > Linuxptp-devel wrote: > > Currently servo state stays in S3 (SERVO_LOCKED_STABLE) even though > > clock offset increases above servo_offset_threshold value (but is still > > below step_threshold value). > > That is on purpose. By design this state variable tracks the initial > convergence, nothing more. The use case is the automotive profile > which has an idea of "fast" start. > > > It will still switch to S0 (SERVO_UNLOCKED) when clock offset is bigger > than > > step_threshold. It allows one to check only servo state and potentially > simplifies > > synchronization status monitoring. > > Simplifies? how? > > There is no monitoring of the servo state. This is a purely internal > state variable. > > Thanks, > Richard > > > _______________________________________________ > Linuxptp-devel mailing list > Linuxptp-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxptp-devel > -- *Luigi 'Comio' Mantellini* My Professional Profile <http://www.linkedin.com/in/comio> *"UNIX is very simple, it just needs a genius to understand its simplicity." [cit.]*
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
