Hi Guys, I'm pretty sure I'm not catching all dependencies here, so if you say it might break something, I'll take that :-) On the other hand, servo state transitions S2->S3 (and also S3->S0 for example) is done based on clock offset value, so for me (in my setup I'm tracking it either via logs or simple custom pmc command) staying on S3 when clock offset is bigger than threshold is just misleading ...
Anyway, many thanks for your feedback. Pawel > -----Original Message----- > From: Richard Cochran <richardcoch...@gmail.com> > Sent: Friday, February 18, 2022 12:35 AM > To: Luigi 'Comio' Mantellini <luigi.mantell...@gmail.com> > Cc: Modrzejewski, Pawel <pawel.modrzejew...@harman.com>; linuxptp- > de...@lists.sourceforge.net > Subject: [EXTERNAL] Re: [Linuxptp-devel] [PATCH] servo: allows servo state > transition back from S3 to S2 > > [EXTERNAL EMAIL] > > On Thu, Feb 17, 2022 at 11:24:00AM +0100, Luigi 'Comio' Mantellini wrote: > > 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. > > Good point. The S2 to S3 is one way on purpose, and you can't change > it without breaking things. > > Thanks, > Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
