On Tue, Feb 01, 2022 at 07:04:29PM +, ramesh t wrote:
> Resetting of testUnit is triggering interface A to go down. This in turns is
> triggering PHC run at different frequency for small duration till interface
> is up. Though this is a driver issue on interface A, my question why is the
> b
hi Miroslav Lichvar,
You are correct, "the timestamp checked in the clockcheck code should always be
a timestamp of the clock synchronized by phc2sys"
In this case, we have connected testUnit to interface A. Interface A is
providing clock to testUnit (with ptp4l in BC mode) and time is synchro
On Thu, Jan 20, 2022 at 06:11:57PM +, ramesh t via Linuxptp-users wrote:
> In clockcheck_sample function, we should depend on CLOCK_MONOTONIC to decide
> if its getting called more frequency than a second. But we also check on
> remote time:
>
> interval = (int64_t)ts - cc->last_ts;
hi Richard,
In phc2sys code, for default config phc_interval, update_clock is called once
in a second based CLOCK_MONOTONIC timer. With sanity_check enabled,
clockcheck_sample is also called.
In clockcheck_sample function, we should depend on CLOCK_MONOTONIC to decide if
its getting called mo
