On some HW it seems it's possible to get an occasional bad reading of the PHC (with normal delay), or in a worse case the clock can step due to a HW/driver bug, which triggers reset of the HW clock instance. To avoid having a bad estimate of the frequency when the next (good) sample is accumulated, drop also the last sample which triggered the reset. |
||
---|---|---|
.. | ||
compilation | ||
kernel | ||
simulation | ||
unit |