On Tue, 31 Aug 2021 10:20:18 +0000 Machnikowski, Maciej wrote: > > Hmm, IDK if this really belongs in RTNL. The OCP time card that > > Jonathan works on also wants to report signal lock, and it locks > > to GNSS. It doesn't have any networking functionality whatsoever. > > > > Can we add a genetlink family for clock info/configuration? From > > what I understood discussing this with Jonathan it sounded like most > > clocks today have a vendor-specific character device for configuration > > and reading status. > > > > I'm happy to write the plumbing if this seems like an okay idea > > but too much work for anyone to commit. > > > > I agree that this also is useful for Time card, yet it's also useful here. > PTP subsystem should implement a similar logic to this one for > DPLL-driven timers which can lock its frequency to external sources. Why would we have two APIs for doing the same thing? IIUC Richard does not want this in the PTP ioctls which is fair, but we need to cater to devices which do not have netdevs. > The reasoning behind putting it here is to enable returning the lock > to the GNSS receiver embedded on the NIC as a source for the > SyncE frequency. It helps distinguishing the embedded GNSS > from the external sources. As a result - the upper layer can report > GNSS lock based only on this message without the need to put the > embedded GNSS receiver in the config file. On the other hand - if > sync to External source is reported such SW would need to read > the source of external sync from the config file. > > And the list is expandable - if we need to define more embedded > sync source types we can always add more to it.
