Thanks Greg for your inputs. Appreciate it. Regards, Ankur
On Tue, Oct 26, 2021 at 6:50 AM Greg Armstrong < greg.armstrong...@renesas.com> wrote: > Hi Ankur, > > > > For ptp4l, have a look at the Slave Event Monitoring channel that was > introduced in v3.0. Per IEEE1588-2019, this allows the ability to monitor > the reception and transmission of PTP events. From that, you should be able > to see the offset/delay data. > > > > [Linuxptp-devel] [PATCH 00/10] Slave event monitoring (mail-archive.com) > <https://www.mail-archive.com/linuxptp-devel@lists.sourceforge.net/msg04053.html> > > > > Regards, > > Greg > > > > *Greg Armstrong* > > Principal System Architect, Timing Products Division > > Renesas Electronics Canada Limited > > Mobile: 1-613-218-9373 > > > > *From:* Ankur Sharma <ankur.at.n...@gmail.com> > *Sent:* October 25, 2021 9:43 PM > *To:* linuxptp-users@lists.sourceforge.net > *Subject:* [Linuxptp-users] Collect Offset/Delay Values > > > > Hi, > > > > I am currently looking into collecting/monitoring the offset/delay values > reported by ptp4l and phc2sys. We know that both tools print those details > to STDOUT and/or System logs file. However, is there a command line way to > collect that offset/delay data for an instance as and when needed? > (something similar to chronyc or ntpq -p) > > > > Any suggestions or pointers would be appreciated. > > > > Regards, > > Ankur > -- ankurandy
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
