1f4538df28
This commit applies several patches to the linuxptp srpm in order to address an issue syncing multiple interfaces on a ptp node. The srpm used is linuxptp-2.0-2.el7.src.rpm. Patch descriptions: base/linuxptp/centos/meta_patches: 0001 updates the srpm spec file to apply the patches during build 0002 updates the package versioning to comply with the STX format base/linuxptp/centos/patches: Patches 0001-0005 combine to correct a fault present when a ptp node is configured with multiple clocks in jbod mode which results in the client port getting stuck in the UNCALIBRATED state and unable to lock to the Grandmaster clock. The root of the issue lies in the sanity check where checking timestamps recieved on multiple ports will result in the sanity_freq_limit threshold constantly being reached and the servo for that port is repeatedly reset, preventing it from ever syncing. The changes in patches 0001-0005 have been written by Miroslav Lichvar on the linuxptp-devel mailing list. They are currently under review and testing by the upstream linuxptp maintainers prior to merging. I was able to apply them as-is to linuxptp v2.0. I have chosen to keep them as individual patches, as that is how they will appear upstream. Patch 0006 is my work and serves to address an issue in phc2sys where the local ptp clocks are not synced together properly if the local time is far behind the reference time. This issue ocurrs when phc2sys starts and there is no client port currently synced to a grandmaster. In the original behaviour, phc2sys selects the first configured port and proceeds to sync all of the other clocks to it by performing the first_step operation. Then ptp4l will evenually lock to the Grandmaster clock, and that single port will have its time updated to the correct value, but phc2sys has already performed the first_step operation and will not step the other clocks again. My solution is to provide an option to disable the selection of a default port by phc2sys. When no default port is selected, phc2sys waits for ptp4l to sync to the Grandmaster before bringing the other clocks into sync with the first_step operation. This option is configured via the default_sync parameter or the -D flag. The default_sync parameter is set to on by default to in order to keep the behaviour the same as upstream linuxptp but can be configured by users via system service-parameter-add ptp global default_sync=0 Closes-Bug: 1930607 Signed-off-by: Cole Walker <cole.walker@windriver.com> Change-Id: I2f660787c6753dcd4fc4c51da7b08ab9e6f197f4
19 lines
544 B
Plaintext
19 lines
544 B
Plaintext
Metadata-Version: 1.1
|
|
Name: linuxptp
|
|
Version: 2.0-2
|
|
Summary: linuxptp
|
|
Home-page: http://linuxptp.sourceforge.net/
|
|
Author:
|
|
Author-email:
|
|
License: GPLv2
|
|
|
|
Description:
|
|
This software is an implementation of the Precision Time Protocol (PTP)
|
|
according to IEEE standard 1588 for Linux. The dual design goals are to
|
|
provide a robust implementation of the standard and to use the most
|
|
relevant and modern Application Programming Interfaces (API) offered by
|
|
the Linux kernel. Supporting legacy APIs and other platforms is not a
|
|
goal.
|
|
|
|
Platform: UNKNOWN
|