On Thu, Nov 12, 2020 at 10:12:49AM +0800, pavan-lakote wrote: > If you have observed, when clock is "free_running" the clock servo state > always remains in "SERVO_UNLOCKED" this causes the port to always remain in > "UNCALIBRATED" state.
Oh, I didn't see that you had free_running=1 > So when unicast master was changed the port was in "UNCALIBRATED" state. As > the previous and new port state is same, "port_state_update()" never trigger > "unicast_client_state_changed()". Now it makes sense. > Is "free_running" clock meant to be "SERVO_UNLOCKED" always? Yes, in this mode, the program never adjusts the clock. Why don't you want to synchronize the local clock? > What is major difference between "free_running" and clock servo " nullf"? The nullf is meant for SyncE (Synchronous Ethernet). When running with Synchronous Ethernet , the correct clock frequency is provided by the link partner. In this case, only the offset needs correcting. HTH, Richard _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
