Get it! Thanks Richard. I have a quick implementation of TAB/PRI today based on BC clock type, instead of TC in my previous patch Please help to review my RFC V2 patch. Hope for your suggestions.
Thanks. Best regards, Yangbo Lu > -----Original Message----- > From: Richard Cochran <richardcoch...@gmail.com> > Sent: Sunday, October 13, 2019 9:53 AM > To: Y.b. Lu <yangbo...@nxp.com> > Cc: Rodney Cummings <rodney.cummi...@ni.com>; > linuxptp-devel@lists.sourceforge.net; rodney.greenstr...@gmail.com; > Андрей Иванов <ia...@yandex.com>; Erik Hons <erik.h...@ni.com> > Subject: Re: Re: [Linuxptp-devel] [Linuxptp-users] How do I implement Sync > message receive timeout according to Automotive and 802.1 AS profiles? > > On Fri, Oct 11, 2019 at 07:23:38AM +0000, Y.b. Lu wrote: > > I'm just not familiar how applications use 802.1AS synchronized time. > > I don't know of any open source applications using 802.1AS either! > > > For physical clock adjustment, I know we have /dev/ptpx device to access for > time. > > For free running clock, I can see master_local_rr is used for > > master/local rate ratio which makes sense for TC to synchronize frequency, > but for OC/BC/end instance, where to find the synchronized time. Is the > TIME_STATUS_NP info enough for applications? > > Given master_offset at ingress_time and cumulativeScaledRateOffset, you can > calculate the remote time. > > Thanks, > Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
