aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSanjeev <ghane0@gmail.com>2016-12-24 03:27:31 -0500
committerJonathan Corbet <corbet@lwn.net>2017-01-04 16:40:52 -0500
commitf2c1a053ceedec87aa355fafe60db1af27d7d830 (patch)
tree82bbd99ae7e22efbff187a0ee12d5183d62ed51b
parentfe4c56c98c1338c0b8b69d08ccf5694bf8e1dcaf (diff)
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>
-rw-r--r--Documentation/pps/pps.txt7
1 files changed, 5 insertions, 2 deletions
diff --git a/Documentation/pps/pps.txt b/Documentation/pps/pps.txt
index a9f53bba910d..1fdbd5447216 100644
--- a/Documentation/pps/pps.txt
+++ b/Documentation/pps/pps.txt
@@ -72,8 +72,11 @@ PPS with USB to serial devices
72It is possible to grab the PPS from an USB to serial device. However, 72It is possible to grab the PPS from an USB to serial device. However,
73you should take into account the latencies and jitter introduced by 73you should take into account the latencies and jitter introduced by
74the USB stack. Users have reported clock instability around +-1ms when 74the USB stack. Users have reported clock instability around +-1ms when
75synchronized with PPS through USB. This isn't suited for time server 75synchronized with PPS through USB. With USB 2.0, jitter may decrease
76synchronization. 76down to the order of 125 microseconds.
77
78This may be suitable for time server synchronization with NTP because
79of its undersampling and algorithms.
77 80
78If your device doesn't report PPS, you can check that the feature is 81If your device doesn't report PPS, you can check that the feature is
79supported by its driver. Most of the time, you only need to add a call 82supported by its driver. Most of the time, you only need to add a call