Jordan Yates
Jordan Yates
For review purposes, please ignore the first commit which only moves the PM function. Comments should address the second commit.
> The reason this API does not exist is that if this high of a resolution/synchronization is required, which is typically the case for applications using PPS, the PPS output...
> I agree it is more accurate, but adding this complexity is just not worth it IMO, the issue with PPS and synchronization is an issue not directly related to...
> That is not what the subsystem would do... the subsystem would expose an API to get the exact time synchronized by the PPS signal, using the PPS signal as...
> Perfect, that is one way an application is expected to use PPS, in which case, why have it be tied to the GNSS API? It is just monitoring a...
> An application could have some dependency on a 1Hz GPIO routed interrupt which is synced with the real-time base, which could be the GNSS, or an RTC. Would you...
> I tend to agree. The solution proposed here (getting a timestamp of the last pulse) is one way of using a 1PPS signal, but certainly not the only way....