On Mon, May 16, 2022 at 07:30:09AM -0700, Richard Cochran wrote: > On Mon, May 16, 2022 at 11:37:58AM +0200, Miroslav Lichvar wrote: > > What interval do you suggest? 10 milliseconds? Of real time or > > perhaps consumed CPU time (CLOCK_PROCESS_CPUTIME_ID)? > > I would use monotonic clock (real time not process time). > > Duration? I don't know... how long do these errors persist?
The ice driver returns EBUSY when it fails to get a lock for the PTP clock, e.g. on concurrent reads. That's a random occurence and I'd not expect a time interval here. In the ionic driver there is EBUSY returned when the FW is upgraded. I have no idea how long that could take and if applications are supposed to work when that happens. Some other drivers seem to return EIO on firmware reset/upgrade. -- Miroslav Lichvar _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
