2013-09-30 02:57:00 +08:00
|
|
|
.TH PTP4l 8 "October 2013" "linuxptp"
|
2012-11-01 18:24:24 +08:00
|
|
|
.SH NAME
|
|
|
|
ptp4l \- PTP Boundary/Ordinary Clock
|
|
|
|
|
|
|
|
.SH SYNOPSIS
|
|
|
|
.B ptp4l
|
|
|
|
[
|
2013-06-17 22:54:03 +08:00
|
|
|
.B \-AEP246HSLmqsv
|
2012-11-01 18:24:24 +08:00
|
|
|
] [
|
|
|
|
.BI \-f " config"
|
|
|
|
] [
|
|
|
|
.BI \-p " phc-device"
|
|
|
|
] [
|
|
|
|
.BI \-l " print-level"
|
|
|
|
]
|
|
|
|
[
|
|
|
|
.BI \-i " interface"
|
|
|
|
]
|
|
|
|
.I .\|.\|.
|
|
|
|
|
|
|
|
.SH DESCRIPTION
|
|
|
|
.B ptp4l
|
|
|
|
is an implementation of the Precision Time Protocol (PTP) according to IEEE
|
|
|
|
standard 1588 for Linux. It implements Boundary Clock (BC) and Ordinary Clock
|
|
|
|
(OC).
|
|
|
|
|
|
|
|
.SH OPTIONS
|
|
|
|
.TP
|
|
|
|
.B \-A
|
|
|
|
Select the delay mechanism automatically. Start with E2E and switch to P2P when
|
|
|
|
a peer delay request is received.
|
|
|
|
.TP
|
|
|
|
.B \-E
|
|
|
|
Select the delay request-response (E2E) mechanism. This is the default
|
2013-06-18 21:52:31 +08:00
|
|
|
mechanism. All clocks on single PTP communication path must use the same
|
|
|
|
mechanism. A warning will be printed when a peer delay request is received on
|
|
|
|
port using the E2E mechanism.
|
2012-11-01 18:24:24 +08:00
|
|
|
.TP
|
|
|
|
.B \-P
|
2013-06-18 21:52:31 +08:00
|
|
|
Select the peer delay (P2P) mechanism. A warning will be printed when a delay
|
|
|
|
request is received on port using the P2P mechanism.
|
2012-11-01 18:24:24 +08:00
|
|
|
.TP
|
|
|
|
.B \-2
|
|
|
|
Select the IEEE 802.3 network transport.
|
|
|
|
.TP
|
|
|
|
.B \-4
|
|
|
|
Select the UDP IPv4 network transport. This is the default transport.
|
|
|
|
.TP
|
|
|
|
.B \-6
|
|
|
|
Select the UDP IPv6 network transport.
|
|
|
|
.TP
|
|
|
|
.B \-H
|
|
|
|
Select the hardware time stamping. All ports specified by the
|
|
|
|
.B \-i
|
|
|
|
option and in the configuration file must be attached to the same PTP hardware
|
|
|
|
clock (PHC). This is the default time stamping.
|
|
|
|
.TP
|
|
|
|
.B \-S
|
|
|
|
Select the software time stamping.
|
|
|
|
.TP
|
|
|
|
.B \-L
|
|
|
|
Select the legacy hardware time stamping.
|
|
|
|
.TP
|
|
|
|
.BI \-f " config"
|
|
|
|
Read configuration from the specified file. No configuration file is read by
|
|
|
|
default.
|
|
|
|
.TP
|
2012-12-10 17:28:28 +08:00
|
|
|
.BI \-i " interface"
|
|
|
|
Specify a PTP port, it may be used multiple times. At least one port must be
|
|
|
|
specified by this option or in the configuration file.
|
|
|
|
.TP
|
2012-11-01 18:24:24 +08:00
|
|
|
.BI \-p " phc-device"
|
|
|
|
With hardware time stamping, force which PHC device (e.g. /dev/ptp0) should be
|
|
|
|
used.
|
|
|
|
.TP
|
|
|
|
.B \-s
|
|
|
|
Enable the slaveOnly mode.
|
|
|
|
.TP
|
|
|
|
.BI \-l " print-level"
|
|
|
|
Set the maximum syslog level of messages which should be printed or sent to
|
|
|
|
the system logger. The default is 6 (LOG_INFO).
|
|
|
|
.TP
|
2012-12-10 17:28:28 +08:00
|
|
|
.B \-m
|
|
|
|
Print messages to the standard output.
|
|
|
|
.TP
|
2012-11-01 18:24:24 +08:00
|
|
|
.B \-q
|
|
|
|
Don't send messages to the system logger.
|
|
|
|
.TP
|
|
|
|
.B \-v
|
2012-12-10 17:28:28 +08:00
|
|
|
Prints the software version and exits.
|
2012-11-01 18:24:24 +08:00
|
|
|
.TP
|
|
|
|
.BI \-h
|
|
|
|
Display a help message.
|
|
|
|
|
|
|
|
.SH CONFIGURATION FILE
|
|
|
|
|
|
|
|
The configuration file is divided into sections. Each section starts with a
|
|
|
|
line containing its name enclosed in brackets and it follows with settings.
|
|
|
|
Each setting is placed on a separate line, it contains the name of the
|
2012-11-07 02:00:00 +08:00
|
|
|
option and the value separated by whitespace characters. Empty lines and lines
|
|
|
|
starting with # are ignored.
|
2012-11-01 18:24:24 +08:00
|
|
|
|
|
|
|
The global section (indicated as
|
|
|
|
.BR [global] )
|
|
|
|
sets the program options, clock options and default port options. Other
|
|
|
|
sections are port specific sections and they override the default port options.
|
|
|
|
The name of the section is the name of the configured port (e.g.
|
|
|
|
.BR [eth0] ).
|
|
|
|
Ports specified in the configuration file don't need to be
|
|
|
|
specified by the
|
|
|
|
.B \-i
|
|
|
|
option. An empty port section can be used to replace the command line option.
|
|
|
|
|
|
|
|
.SH PORT OPTIONS
|
|
|
|
|
2012-12-10 21:39:08 +08:00
|
|
|
.TP
|
|
|
|
.B delayAsymmetry
|
|
|
|
The time difference in nanoseconds of the transmit and receive
|
|
|
|
paths. This value should be positive when the master-to-slave
|
|
|
|
propagation time is longer and negative when the slave-to-master time
|
|
|
|
is longer. The default is 0 nanoseconds.
|
2012-11-01 18:24:24 +08:00
|
|
|
.TP
|
|
|
|
.B logAnnounceInterval
|
|
|
|
The mean time interval between Announce messages. A shorter interval makes
|
|
|
|
ptp4l react faster to the changes in the master-slave hierarchy. The interval
|
|
|
|
should be the same in the whole domain. It's specified as a power of two in
|
|
|
|
seconds.
|
|
|
|
The default is 1 (2 seconds).
|
|
|
|
.TP
|
|
|
|
.B logSyncInterval
|
|
|
|
The mean time interval between Sync messages. A shorter interval may improve
|
|
|
|
accuracy of the local clock. It's specified as a power of two in seconds.
|
|
|
|
The default is 0 (1 second).
|
|
|
|
.TP
|
|
|
|
.B logMinDelayReqInterval
|
|
|
|
The minimum permitted mean time interval between Delay_Req messages. A shorter
|
|
|
|
interval makes ptp4l react faster to the changes in the path delay. It's
|
|
|
|
specified as a power of two in seconds.
|
|
|
|
The default is 0 (1 second).
|
|
|
|
.TP
|
|
|
|
.B logMinPdelayReqInterval
|
|
|
|
The minimum permitted mean time interval between Pdelay_Req messages. It's
|
|
|
|
specified as a power of two in seconds.
|
|
|
|
The default is 0 (1 second).
|
|
|
|
.TP
|
|
|
|
.B announceReceiptTimeout
|
|
|
|
The number of missed Announce messages before the last Announce messages
|
|
|
|
expires.
|
|
|
|
The default is 3.
|
|
|
|
.TP
|
2013-08-26 20:36:49 +08:00
|
|
|
.B syncReceiptTimeout
|
|
|
|
The number of sync/follow up messages that may go missing before
|
|
|
|
triggering a Best Master Clock election. This option is used for
|
|
|
|
running in gPTP mode according to the 802.1AS-2011 standard. Setting
|
|
|
|
this option to zero will disable the sync message timeout.
|
|
|
|
The default is 0 or disabled.
|
|
|
|
.TP
|
2012-11-01 18:24:24 +08:00
|
|
|
.B transportSpecific
|
|
|
|
The transport specific field. Must be in the range 0 to 255.
|
|
|
|
The default is 0.
|
|
|
|
.TP
|
|
|
|
.B path_trace_enabled
|
|
|
|
Enable the mechanism used to trace the route of the Announce messages.
|
|
|
|
The default is 0 (disabled).
|
|
|
|
.TP
|
|
|
|
.B follow_up_info
|
|
|
|
Include the 802.1AS data in the Follow_Up messages if enabled.
|
|
|
|
The default is 0 (disabled).
|
|
|
|
.TP
|
2013-01-30 23:28:54 +08:00
|
|
|
.B fault_reset_interval
|
|
|
|
The time in seconds between the detection of a port's fault and the fault
|
|
|
|
being reset. This value is expressed as a power of two. Setting this
|
|
|
|
value to -128 or to the special key word "ASAP" will let the fault be
|
|
|
|
reset immediately.
|
|
|
|
The default is 4 (16 seconds).
|
|
|
|
.TP
|
2013-03-19 00:08:22 +08:00
|
|
|
.B fault_badpeernet_interval
|
|
|
|
The time in seconds between the detection of a peer network misconfiguration
|
|
|
|
and the fault being reset. The port is disabled for the duration of the
|
|
|
|
interval. The value is in seconds and the special key word ASAP will let
|
|
|
|
the fault be reset immediately.
|
|
|
|
The default is 16 seconds.
|
|
|
|
.TP
|
2012-11-01 18:24:24 +08:00
|
|
|
.B delay_mechanism
|
|
|
|
Select the delay mechanism. Possible values are E2E, P2P and Auto.
|
|
|
|
The default is E2E.
|
|
|
|
.TP
|
|
|
|
.B network_transport
|
|
|
|
Select the network transport. Possible values are UDPv4, UDPv6 and L2.
|
|
|
|
The default is UDPv4.
|
2013-03-14 03:16:59 +08:00
|
|
|
.TP
|
|
|
|
.B neighborPropDelayThresh
|
|
|
|
Upper limit for peer delay in nanoseconds. If the estimated peer delay is
|
|
|
|
greater than this value the port is marked as not 802.1AS capable.
|
2013-10-29 18:58:20 +08:00
|
|
|
.TP
|
|
|
|
.B delay_filter
|
|
|
|
Select the algorithm used to filter the measured delay and peer delay. Possible
|
|
|
|
values are moving_average and moving_median.
|
|
|
|
The default is moving_median.
|
|
|
|
.TP
|
|
|
|
.B delay_filter_length
|
|
|
|
The length of the delay filter in samples.
|
|
|
|
The default is 10.
|
2012-11-01 18:24:24 +08:00
|
|
|
|
|
|
|
.SH PROGRAM AND CLOCK OPTIONS
|
|
|
|
|
|
|
|
.TP
|
|
|
|
.B twoStepFlag
|
2012-12-18 21:00:48 +08:00
|
|
|
Enable two-step mode for sync messages. One-step mode can be used only with
|
|
|
|
hardware time stamping.
|
2012-11-01 18:24:24 +08:00
|
|
|
The default is 1 (enabled).
|
|
|
|
.TP
|
|
|
|
.B slaveOnly
|
|
|
|
The local clock is a slave-only clock if enabled.
|
|
|
|
The default is 0 (disabled).
|
|
|
|
.TP
|
|
|
|
.B priority1
|
|
|
|
The priority1 attribute of the local clock. It is used in the best master
|
|
|
|
selection algorithm, lower values take precedence. Must be in the range 0 to
|
|
|
|
255.
|
|
|
|
The default is 128.
|
|
|
|
.TP
|
|
|
|
.B priority2
|
|
|
|
The priority2 attribute of the local clock. It is used in the best master
|
|
|
|
selection algorithm, lower values take precedence. Must be in the range 0 to
|
|
|
|
255.
|
|
|
|
The default is 128.
|
|
|
|
.TP
|
|
|
|
.B clockClass
|
|
|
|
The clockClass attribute of the local clock. It denotes the traceability of the
|
|
|
|
time distributed by the grandmaster clock.
|
|
|
|
The default is 248.
|
|
|
|
.TP
|
|
|
|
.B clockAccuracy
|
|
|
|
The clockAccuracy attribute of the local clock. It is used in the best master
|
|
|
|
selection algorithm.
|
|
|
|
The default is 0xFE.
|
|
|
|
.TP
|
|
|
|
.B offsetScaledLogVariance
|
|
|
|
The offsetScaledLogVariance attribute of the local clock. It characterizes the
|
|
|
|
stability of the clock.
|
|
|
|
The default is 0xFFFF.
|
|
|
|
.TP
|
|
|
|
.B domainNumber
|
|
|
|
The domain attribute of the local clock.
|
|
|
|
The default is 0.
|
|
|
|
.TP
|
|
|
|
.B free_running
|
|
|
|
Don't adjust the local clock if enabled.
|
|
|
|
The default is 0 (disabled).
|
|
|
|
.TP
|
|
|
|
.B freq_est_interval
|
|
|
|
The time interval over which is estimated the ratio of the local and
|
|
|
|
peer clock frequencies. It is specified as a power of two in seconds.
|
|
|
|
The default is 1 (2 seconds).
|
|
|
|
.TP
|
|
|
|
.B assume_two_step
|
|
|
|
Treat one-step responses as two-step if enabled. It is used to work around
|
|
|
|
buggy 802.1AS switches.
|
|
|
|
The default is 0 (disabled).
|
|
|
|
.TP
|
2013-04-05 23:52:14 +08:00
|
|
|
.B tx_timestamp_timeout
|
|
|
|
The number of milliseconds to poll waiting for the tx time stamp from the kernel
|
|
|
|
when a message has recently been sent.
|
|
|
|
The default is 1.
|
2012-11-01 18:24:24 +08:00
|
|
|
.TP
|
2013-08-29 17:01:27 +08:00
|
|
|
.B check_fup_sync
|
|
|
|
Because of packet reordering that can occur in the network, in the
|
|
|
|
hardware, or in the networking stack, a follow up message can appear
|
|
|
|
to arrive in the application before the matching sync message. As this
|
|
|
|
is a normal occurrence, and the sequenceID message field ensures
|
|
|
|
proper matching, the ptp4l program accepts out of order packets. This
|
|
|
|
option adds an additional check using the software time stamps from
|
|
|
|
the networking stack to verify that the sync message did arrive
|
|
|
|
first. This option is only useful if you do not trust the sequence IDs
|
|
|
|
generated by the master.
|
|
|
|
The default is 0 (disabled).
|
|
|
|
.TP
|
2012-11-01 18:24:24 +08:00
|
|
|
.B clock_servo
|
|
|
|
The servo which is used to synchronize the local clock. Currently only one
|
|
|
|
servo is implemented, a PI controller.
|
|
|
|
The default is pi.
|
|
|
|
.TP
|
|
|
|
.B pi_proportional_const
|
2013-06-28 23:09:14 +08:00
|
|
|
The proportional constant of the PI controller. When set to 0.0, the
|
|
|
|
proportional constant will be set by the following formula from the current
|
|
|
|
sync interval.
|
2012-11-01 18:24:24 +08:00
|
|
|
The default is 0.0.
|
2013-06-28 23:09:14 +08:00
|
|
|
|
|
|
|
kp = min(kp_scale * sync^kp_exponent, kp_norm_max / sync))
|
2012-11-01 18:24:24 +08:00
|
|
|
.TP
|
|
|
|
.B pi_integral_const
|
2013-06-28 23:09:14 +08:00
|
|
|
The integral constant of the PI controller. When set to 0.0, the
|
|
|
|
integral constant will be set by the following formula from the current
|
|
|
|
sync interval.
|
|
|
|
The default is 0.0.
|
|
|
|
|
|
|
|
ki = min(ki_scale * sync^ki_exponent, ki_norm_max / sync)
|
|
|
|
.TP
|
|
|
|
.B pi_proportional_scale
|
|
|
|
The kp_scale constant in the formula used to set the proportional constant of
|
|
|
|
the PI controller from the sync interval. When set to 0.0, the value will be
|
|
|
|
selected from 0.7 and 0.1 for the hardware and software time stamping
|
|
|
|
respectively.
|
|
|
|
The default is 0.0.
|
|
|
|
.TP
|
|
|
|
.B pi_proportional_exponent
|
|
|
|
The kp_exponent constant in the formula used to set the proportional constant of
|
|
|
|
the PI controller from the sync interval.
|
|
|
|
The default is -0.3.
|
|
|
|
.TP
|
|
|
|
.B pi_proportional_norm_max
|
|
|
|
The kp_norm_max constant in the formula used to set the proportional constant of
|
|
|
|
the PI controller from the sync interval.
|
|
|
|
The default is 0.7
|
|
|
|
.TP
|
|
|
|
.B pi_integral_scale
|
|
|
|
The ki_scale constant in the formula used to set the integral constant of
|
|
|
|
the PI controller from the sync interval. When set to 0.0, the value will be
|
2012-11-01 18:24:24 +08:00
|
|
|
selected from 0.3 and 0.001 for the hardware and software time stamping
|
|
|
|
respectively.
|
|
|
|
The default is 0.0.
|
|
|
|
.TP
|
2013-06-28 23:09:14 +08:00
|
|
|
.B pi_integral_exponent
|
|
|
|
The ki_exponent constant in the formula used to set the integral constant of
|
|
|
|
the PI controller from the sync interval.
|
|
|
|
The default is 0.4.
|
|
|
|
.TP
|
|
|
|
.B pi_integral_norm_max
|
|
|
|
The ki_norm_max constant in the formula used to set the integral constant of
|
|
|
|
the PI controller from the sync interval.
|
|
|
|
The default is 0.3.
|
|
|
|
.TP
|
2012-11-01 18:24:24 +08:00
|
|
|
.B pi_offset_const
|
|
|
|
The maximum offset the PI controller will correct by changing the clock
|
|
|
|
frequency instead of stepping the clock. When set to 0.0, the controller will
|
2013-06-25 08:46:16 +08:00
|
|
|
never step the clock except on start.
|
2012-11-01 18:24:24 +08:00
|
|
|
The default is 0.0.
|
|
|
|
.TP
|
2013-06-25 08:46:16 +08:00
|
|
|
.B pi_f_offset_const
|
|
|
|
The maximum offset the PI controller will correct by changing the clock
|
|
|
|
frequency instead of stepping the clock. This is only applied on the first
|
|
|
|
update. When set to 0.0, the controller won't step the clock on start.
|
|
|
|
The default is 0.0000001 (100 nanoseconds).
|
|
|
|
.TP
|
2013-04-11 02:07:48 +08:00
|
|
|
.B pi_max_frequency
|
|
|
|
The maximum allowed frequency adjustment of the clock in parts per billion
|
|
|
|
(ppb). This is an additional limit to the maximum allowed by the hardware. When
|
|
|
|
set to 0, the hardware limit will be used.
|
|
|
|
The default is 900000000 (90%).
|
|
|
|
.TP
|
2013-10-23 00:57:15 +08:00
|
|
|
.B sanity_freq_limit
|
|
|
|
The maximum allowed frequency offset between uncorrected clock and the system
|
|
|
|
monotonic clock in parts per billion (ppb). This is used as a sanity check of
|
|
|
|
the synchronized clock. When a larger offset is measured, a warning message
|
|
|
|
will be printed and the servo will be reset. When set to 0, the sanity check is
|
|
|
|
disabled. The default is 200000000 (20%).
|
|
|
|
.TP
|
2012-11-01 18:24:24 +08:00
|
|
|
.B ptp_dst_mac
|
|
|
|
The MAC address where should be PTP messages sent.
|
|
|
|
Relevant only with L2 transport. The default is 01:1B:19:00:00:00.
|
|
|
|
.TP
|
|
|
|
.B p2p_dst_mac
|
|
|
|
The MAC address where should be peer delay messages the PTP peer.
|
|
|
|
Relevant only with L2 transport. The default is 01:80:C2:00:00:0E.
|
|
|
|
.TP
|
2012-11-26 17:34:19 +08:00
|
|
|
.B udp6_scope
|
|
|
|
Specifies the desired scope for the IPv6 multicast messages. This
|
|
|
|
will be used as the second byte of the primary address. This option
|
|
|
|
is only relevant with IPv6 transport. See RFC 4291. The default is
|
|
|
|
0x0E for the global scope.
|
|
|
|
.TP
|
2013-09-30 02:57:00 +08:00
|
|
|
.B uds_address
|
|
|
|
Specifies the address of the UNIX domain socket for receiving local
|
|
|
|
management messages. The default is /var/run/ptp4l.
|
|
|
|
.TP
|
2012-11-01 18:24:24 +08:00
|
|
|
.B logging_level
|
|
|
|
The maximum logging level of messages which should be printed.
|
|
|
|
The default is 6 (LOG_INFO).
|
|
|
|
.TP
|
|
|
|
.B verbose
|
|
|
|
Print messages to the standard output if enabled.
|
|
|
|
The default is 0 (disabled).
|
|
|
|
.TP
|
|
|
|
.B use_syslog
|
|
|
|
Print messages to the system log if enabled.
|
|
|
|
The default is 1 (enabled).
|
|
|
|
.TP
|
2013-02-08 02:56:53 +08:00
|
|
|
.B summary_interval
|
|
|
|
The time interval in which are printed summary statistics of the clock. It is
|
|
|
|
specified as a power of two in seconds. The statistics include offset root mean
|
|
|
|
square (RMS), maximum absolute offset, frequency offset mean and standard
|
|
|
|
deviation, and path delay mean and standard deviation. The units are
|
|
|
|
nanoseconds and parts per billion (ppb). If there is only one clock update in
|
|
|
|
the interval, the sample will be printed instead of the statistics. The
|
|
|
|
messages are printed at the LOG_INFO level.
|
|
|
|
The default is 0 (1 second).
|
|
|
|
.TP
|
2012-11-01 18:24:24 +08:00
|
|
|
.B time_stamping
|
|
|
|
The time stamping method. The allowed values are hardware, software and legacy.
|
|
|
|
The default is hardware.
|
2013-02-04 06:01:52 +08:00
|
|
|
.TP
|
|
|
|
.B productDescription
|
|
|
|
The product description string. Allowed values must be of the form
|
|
|
|
manufacturerName;modelNumber;instanceIdentifier and contain at most 64
|
|
|
|
utf8 symbols. The default is ";;".
|
|
|
|
.TP
|
|
|
|
.B revisionData
|
|
|
|
The revision description string which contains the revisions for node
|
|
|
|
hardware (HW), firmware (FW), and software (SW). Allowed values are of
|
|
|
|
the form HW;FW;SW and contain at most 32 utf8 symbols. The default is
|
|
|
|
an ";;".
|
|
|
|
.TP
|
|
|
|
.B userDescription
|
|
|
|
The user description string. Allowed values are of the form
|
|
|
|
name;location and contain at most 128 utf8 symbols. The default is an
|
|
|
|
empty string.
|
|
|
|
.TP
|
|
|
|
.B manufacturerIdentity
|
|
|
|
The manufacturer id which should be an OUI owned by the manufacturer.
|
|
|
|
The default is 00:00:00.
|
2013-03-08 00:27:33 +08:00
|
|
|
.TP
|
|
|
|
.B kernel_leap
|
|
|
|
When a leap second is announced, let the kernel apply it by stepping the clock
|
|
|
|
instead of correcting the one-second offset with servo, which would correct the
|
|
|
|
one-second offset slowly by changing the clock frequency (unless the
|
|
|
|
.B pi_offset_const
|
|
|
|
option is set to correct such offset by stepping).
|
|
|
|
Relevant only with software time stamping. The default is 1 (enabled).
|
2013-07-06 03:40:06 +08:00
|
|
|
.TP
|
|
|
|
.B timeSource
|
|
|
|
The time source is a single byte code that gives an idea of the kind
|
|
|
|
of local clock in use. The value is purely informational, having no
|
|
|
|
effect on the outcome of the Best Master Clock algorithm, and is
|
|
|
|
advertised when the clock becomes grand master.
|
2012-11-01 18:24:24 +08:00
|
|
|
|
2013-05-17 16:55:48 +08:00
|
|
|
.SH TIME SCALE USAGE
|
|
|
|
|
|
|
|
.B ptp4l
|
|
|
|
as domain master either uses PTP or UTC time scale depending on time stamping
|
|
|
|
mode. In software and legacy time stamping modes it announces Arbitrary time
|
|
|
|
scale mode, which is effectively UTC here, in hardware time stamping mode it
|
|
|
|
announces use of PTP time scale.
|
|
|
|
|
|
|
|
When
|
|
|
|
.B ptp4l
|
|
|
|
is the domain master using hardware time stamping, it is up to
|
|
|
|
.B phc2sys
|
|
|
|
to maintain the correct offset between UTC and PTP times. See
|
|
|
|
.BR phc2sys (8)
|
|
|
|
manual page for more details.
|
|
|
|
|
2012-11-01 18:24:24 +08:00
|
|
|
.SH SEE ALSO
|
|
|
|
.BR pmc (8),
|
|
|
|
.BR phc2sys (8)
|