diff options
Diffstat (limited to 'Documentation/pps')
-rw-r--r-- | Documentation/pps/pps.txt | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/Documentation/pps/pps.txt b/Documentation/pps/pps.txt index d35dcdd82ff6..c03b1be5eb15 100644 --- a/Documentation/pps/pps.txt +++ b/Documentation/pps/pps.txt | |||
@@ -66,6 +66,21 @@ In LinuxPPS the PPS sources are simply char devices usually mapped | |||
66 | into files /dev/pps0, /dev/pps1, etc.. | 66 | into files /dev/pps0, /dev/pps1, etc.. |
67 | 67 | ||
68 | 68 | ||
69 | PPS with USB to serial devices | ||
70 | ------------------------------ | ||
71 | |||
72 | It is possible to grab the PPS from an USB to serial device. However, | ||
73 | you should take into account the latencies and jitter introduced by | ||
74 | the USB stack. Users has reported clock instability around +-1ms when | ||
75 | synchronized with PPS through USB. This isn't suited for time server | ||
76 | synchronization. | ||
77 | |||
78 | If your device doesn't report PPS, you can check that the feature is | ||
79 | supported by its driver. Most of the time, you only need to add a call | ||
80 | to usb_serial_handle_dcd_change after checking the DCD status (see | ||
81 | ch341 and pl2303 examples). | ||
82 | |||
83 | |||
69 | Coding example | 84 | Coding example |
70 | -------------- | 85 | -------------- |
71 | 86 | ||