> 12.10.2022 15:20 Jakub Raczyński <j.raczyn...@elpromaelectronics.com> > napisał(a): > > > > > > > > > > 12.10.2022 14:38 Erez <erezge...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > On Wed, 12 Oct 2022 at 13:48, Jakub Raczynski > > <j.raczyn...@elpromaelectronics.com > > <mailto:j.raczyn...@elpromaelectronics.com>> wrote: > > > Current implementation of flag "-a -rr" for phc2sys selects > > > CLOCK_REALTIME for > > > both directions of PTP synchronization. This may be impractical for > > > Network > > > > > > Not really sure what you are talking about, it can be used to "synchro‐ > > nize the system clock to a PTP hardware clock (PHC)". > > Which means it updated the PHC and only read the CLOCK_REALTIME. > > Why do you need to "protect" the CLOCK_REALTIME further? > > > > > The problem is simple: flag "-a -rr" sets CLOCK_REALTIME to be both source > and receiver, depending on the portState. I find it a bit lacking, as it > would be really useful if we could use CLOCK_REALTIME as source only and > ntpshm as receiver (depending on the portState of course). To clarify here, > you still have to use two phc2sys instances. But currently, first one with > "-a -rr" just blocks second one (PHC->ntpshm) as it will synchronize system > clock if portState is Slave. This patch just sets "semi master-only" flag for CLOCK_REALTIME.
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
