Hi Aya,
- @adjphase: Adjusts the phase offset of the hardware clock.
parameter delta: Desired change in nanoseconds.
- @adjtime: Shifts the time of the hardware clock.
parameter delta: Desired change in nanoseconds.@@ -128,6 +131,7 @@ struct ptp_clock_info { struct ptp_pin_desc *pin_config; int (*adjfine)(struct ptp_clock_info *ptp, long scaled_ppm); int (*adjfreq)(struct ptp_clock_info *ptp, s32 delta);
- int (*adjphase)(struct ptp_clock_info *ptp, s32 phase);
Hi,
Please explain the difference in the output between adjphase and adjtime. I'd expect both to add delta to current time. Am I missing something?
Yes, both add delta to the current time and the 1 PPS should arrive at the same location.
adjtime modifies HW counter with a value to move the 1 PPS abruptly to new location. adjphase modifies the frequency to quickly nudge the 1 PPS to new location and also includes a HW filter to smooth out the adjustments and fine tune frequency.
Continuous small offset adjustments using adjtime, likley see sudden shifts of the 1 PPS. The 1 PPS probably disappears and re-appears. Continuous small offset adjustments using adjphase, should see continuous 1 PPS.
adjtime is good for large offset corrections adjphase is good for small offset corrections to allow HW filter to control the frequency instead of relying on SW filter.
On interruption of timestamps, adjphase HW can hold the frequency steady better since it has history of corrections.
ptp4l will switch to adjphase only if servo_offset_threshold and servo_num_offset_values conditions are met, ie. when offsets are stabalized below servo_offset_threshold.
adjphase is most useful for scnearios with minimal PDV.
Hope that helps.
Thanks, Vincent
Thanks, Aya
int (*adjtime)(struct ptp_clock_info *ptp, s64 delta); int (*gettime64)(struct ptp_clock_info *ptp, struct timespec64 *ts); int (*gettimex64)(struct ptp_clock_info *ptp, struct timespec64 *ts,