On Tue, Aug 10, 2021 at 05:47:44PM +0200, JP wrote: > I guess I will only be able to make use of one domain "the standard way" > (i.e. use phc2sys to synchronize CLOCK_REALTIME, and then use standard Linux > clock system calls with CLOCK_REALTIME).
right. > Is there a best practice when it comes to using a second domain? It depends on what you are trying to accomplish. The stack is flexible enough to cover many use cases. > Can one use > a PHC clock id with any system call that uses clock ids (e.g. the timerfd > family)? No. > Or are these only expected to work with clock_gettime & co? Yes. > And is > this different for virtual PHCs? A PHC vclock is simply a PHC that shares the MAC HW with other PHCs, but it is otherwise a PHC like any other. > Would a "free running" instance of ptp4l for the 2nd domain be more useful > in user space, rather than going the virtual PHC route? Again, it depends on the use case. HTH, Richard _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
