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
