Hi linuxptp users,
I have a query regarding clock_gettime implementation in the driver.
I am running my device as a master. Is it mandatory to implement driver
call backs for gettime and settime for master?
I think the ptp4l program doesn't call clock_gettime() and clock_settime
but I'm not
Hello all,
I want to use linuxptp to synchronize multiple embedded real-time systems.
So far, I managed to synchronize the CLOCK_REALTIME on two systems with high
accuracy using ptp4l and phc2sys.
For some applications running on those systems this is very useful. But we also
have a scheduler
Hi Miroslav,
*Below is the output for master*:
*sudo ./phc_ctl /dev/ptp2phc_ctl[14216.300]: capabilities: 9
maximum frequency adjustment (ppb) 0 programable alarms 0 external time
stamp channels 0 programmable periodic signals doesn't have pulse per
second support*
*And this
On Tue, Jan 17, 2023 at 03:46:29PM +0530, Aditya Venu via Linuxptp-users wrote:
> Corrected step_threshold to 0 and observed that slave's servo state going
> to locked state.
>
> But the offset is continuously increasing..
It might be a driver issue. What does phc_ctl /dev/ptp0 (or the
Hi Richard,
Corrected step_threshold to 0 and observed that slave's servo state going
to locked state.
But the offset is continuously increasing..
ptp4l[12074.007]: master offset -31076 s2 freq -1 path delay
4145
ptp4l[12075.008]: master offset -46783 s2 freq -1 path delay
On Fri, Jan 13, 2023 at 12:32:21PM +0530, Aditya Venu via Linuxptp-users wrote:
> d) I'm using default config files for both master and slave(attaching them
> for reference)
You are NOT using the default configuration.
You changed step_threshold from the default of zero.
This is the reason for
