On Thu, Aug 06, 2020 at 04:16:10PM +0200, Miroslav Lichvar wrote: > Instead of unconditionally creating a servo for each clock in their > initialization, add the servo later on the first update of the clock, > when it is known the clock needs to be synchronized. > > This fixes an issue with phc2sys disrupting the system clock when > it is synchronized by another process and should be used by phc2sys only > as a source. Creating a servo for the system clock caused a reset of its > frequency and status. > > Reported-by: Russell King <li...@armlinux.org.uk> > Signed-off-by: Miroslav Lichvar <mlich...@redhat.com>
Sorry about the delay on this one. I applied Vladimir changes first, and that caused more-or-less trivial conflicts with this patch. I went ahead and fixed the conflicts and applied this, first checking that it passes the test suite. Thanks, Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
