mirror of
https://github.com/torvalds/linux.git
synced 2024-11-10 22:21:40 +00:00
Doc: clarify source of jitter in USB1.1, and USB2.0
Even though the jitter due to USB1.1 may be 1ms, NTP can reduce its effect significantly. And USB2.0 reduces this anyway. Signed-off-by: Sanjeev Gupta <ghane0@gmail.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
fe4c56c98c
commit
f2c1a053ce
@ -72,8 +72,11 @@ PPS with USB to serial devices
|
|||||||
It is possible to grab the PPS from an USB to serial device. However,
|
It is possible to grab the PPS from an USB to serial device. However,
|
||||||
you should take into account the latencies and jitter introduced by
|
you should take into account the latencies and jitter introduced by
|
||||||
the USB stack. Users have reported clock instability around +-1ms when
|
the USB stack. Users have reported clock instability around +-1ms when
|
||||||
synchronized with PPS through USB. This isn't suited for time server
|
synchronized with PPS through USB. With USB 2.0, jitter may decrease
|
||||||
synchronization.
|
down to the order of 125 microseconds.
|
||||||
|
|
||||||
|
This may be suitable for time server synchronization with NTP because
|
||||||
|
of its undersampling and algorithms.
|
||||||
|
|
||||||
If your device doesn't report PPS, you can check that the feature is
|
If your device doesn't report PPS, you can check that the feature is
|
||||||
supported by its driver. Most of the time, you only need to add a call
|
supported by its driver. Most of the time, you only need to add a call
|
||||||
|
Loading…
Reference in New Issue
Block a user