/freebsd/contrib/ntp/html/drivers/ |
H A D | driver22.html | 6 <title>PPS Clock Discipline</title> 11 <h3>PPS Clock Discipline</h3> 19 Reference ID: <tt>PPS</tt><br> 20 Driver ID: <tt>PPS</tt><br> 21 Serial or Parallel Port: <tt>/dev/pps<i>u</i></tt><br> 22 Requires: PPSAPI signal interface for PPS signal processing.</p> 23 …ires the Pulse per Second API (PPSAPI)<sup>1</sup>. Note also that the <tt>pps</tt> configuration … 25 <p>This driver furnishes an interface for the pulse-per-second (PPS) signal produced by a cesium cl… 26 <p>While this driver can discipline the time and frequency relative to the PPS source, it cannot nu… 27 …ary versions of Tru64 (Alpha) and SunOS. See the <a href="../pps.html">Pulse-per-second (PPS) Sign… [all …]
|
H A D | driver46.html | 39 applications. <i>GPSD</i> can also auto-detect and handle PPS 46 using a GPS device with PPS support.</b> 76 The driver needs the VERSION, TPV, PPS, WATCH and TOFF objects 115 the <tt>timedata</tt> channel. (PPS is handled 122 mode PPS on devices that are hot-plugged or activated on demand. 147 <li>The receiver does not provide a PPS signal. 148 <li>The receiver <i>does</i> provide a PPS signal and 149 the secondary PPS unit is used. 159 <td>Strict operation. This mode needs a valid PPS and a 161 the time stamp from the PPS record. Does not feed clock [all …]
|
H A D | driver4.html | 27 Features: Optional PPS signal processing, <tt>tty_clk</tt><br> 28 Requires: Optional PPS signal processing requires the PPSAPI signal interface.</p> 50 <h4>PPS Signal Processing</h4> 51 …PPS signal processing is enabled, and when the system clock has been set by this or another driver… 57 …<dd>Specifies the PPS time offset calibration factor, in seconds and fraction, with default 0.0.</… 65 <dd>Disable PPS signal processing if 0 (default); enable PPS signal processing if 1.</dd> 67 …<dd>If PPS signal processing is enabled, capture the pulse on the rising edge if 0 (default); capt… 69 …<dd>If PPS signal processing is enabled, use the <tt>ntpd</tt> clock discipline if 0 (default); us…
|
H A D | driver30.html | 23 …PPS Port: <tt>/dev/oncore.pps.</tt><i>u</i>; <tt>PPS_CAPTUREASSERT</tt> required, <tt>… 27 …terfaces to a PC straightaway, using the serial (DCD) or parallel port for PPS input and packs the… 51 …PPS</tt> interface for the pulse-per-second output from the receiver. The serial data stream alone… 78 …ion of the GPS receiver, an offset of the PPS signal from zero, and the cable delay. The offset sh… 79 …PI. The edge of the PPS signal that is `on-time' can be set with the keywords [ASSERT/CLEAR] and t… 81 …PPS pulse is referenced to UTC(GPS) with better than 50 nsec (1 sigma) accuracy. The limiting…
|
H A D | driver8.html | 22 …PPS device: /dev/refclockpps-<em>u</em>; alternate PPS device (if not available via the serial por… 27 …f a PPS signal is also provided as a configuration option. The PPS configuration option uses the… 28 …PPS configuration option is different from the hardware PPS signal, which is also supported (see … 29 <p>The use of the PPS option requires receivers with an accuracy of better than 1ms.</p> 44 <p>If PPS information is present, additional variables are available:</p> 47 <dd>The difference between the RS-232-derived timestamp and the PPS timestamp.</dd> 49 <dd>The PPS timestamp.</dd> 222 …<p>PPS support is only available when the receiver is completely synchronized. The receiver is be… 224 …PPS loopfilter control, a true PPS hardware signal can be utilized via the PPSAPI interface. PPS … 225 <h4>Hardware PPS support<br> [all …]
|
H A D | driver31.html | 25 …PPS</tt> interface for the pulse-per-second output from the receiver. The serial data stream alone… 43 <dd>Specifies the <tt>PPS</tt> signal on-time edge: 0 for assert (default), 1 for clear. 51 …The edge of the <tt>PPS</tt> signal that is `on-time' can be set with <tt>flag2</tt>. There is cur…
|
/freebsd/contrib/ntp/html/ |
H A D | pps.html | 6 <title>Pulse-Per-Second (PPS) Signal Interfacing</title> 10 <h3>Pulse-Per-Second (PPS) Signal Interfacing</h3> 12 <p>Alice is trying to find the PPS signal connector.</p> 24 <li class="inline"><a href="#use">Using the Pulse-per-Second (PPS) Signal</a></li> 28 …PPS) signal which can be used to improve the accuracy to a few microseconds. This page describes t… 29 …PPS signal can be connected in either of two ways. On FreeBSD systems (with the PPS_SYNC and pps k… 36 …and is for use with a timecode receiver or precision oscillator with a TTL PPS output. The other c… 38 …ion Time Signals</a> page is the only interface currently supported. Older PPS interfaces based on… 39 <h4>PPS Driver</h4> 40 …PPS support requires is built into some drivers, in particular the WWVB and NMEA drivers, and may … [all …]
|
H A D | kernpps.html | 22 …PPS) signal generated by some radio clocks and cesium oscillators. The PPSAPI provides a generic c… 23 <p>The PPSAPI interface defined in RFC-2783 is the only PPS interface supported in NTP Version 4. T… 25 …PPS Clock Discipline</a> driver (type 22) uses the PPSAPI in conjunction with a local radio clock … 30 <dd>Creates a PPS interface instance and returns a handle to it.</dd> 32 <dd>Destroys a PPS interface and returns the resources used.</dd> 34 …<dd>Sets the parameters associated with a PPS interface instance, including offsets to be automati… 36 <dd>Returns the parameters associated with a PPS interface instance. 40 …<dd>Returns the current timestamps associated with a PPS interface instance in either nanoseconds … 42 …<dd>If kernel PPS processing is supported, this binds the support to the associated PPS interface … 44 …PPS interface functionality is currently provided by inline code in the <tt>timepps.h</tt> header …
|
H A D | prefer.html | 46 …PPS) signals and PPS signals are being received, it is designated the <i>PPS driver.</i> Note that… 51 …idered and so forth. This order of priority is also applicable to multiple PPS drivers, multiple m… 70 <li>PPS driver, if present.</li> 76 …PPS driver and the system clock offset at this point is less than 0.4 s, and if there is a prefer … 80 …es as described in previous sections. The <tt>flag</tt> option enables the PPS signal for the sele… 81 <p>A common scenario is a GPS driver with a serial timecode and PPS signal. The 82 PPS signal is disabled until the system clock has been set by some means, not 83 necessarily the GPS driver. If the serial timecode is within 0.4 s of the PPS 84 signal, the GPS driver is designated the PPS driver and the PPS signal disciplines 85 the system clock. If the serial timecode becomes unreliable, or if the PPS signal is [all …]
|
/freebsd/contrib/ntp/ntpd/ |
H A D | ntp_ppsdev.c | 2 * ntp_ppsdev.c - PPS-device support 7 * Helper code to work around (or with) a Linux 'specialty': PPS devices 8 * are created via attaching the PPS line discipline to a TTY. This 9 * creates new pps devices, and the PPS API is *not* available through 12 * Findig the PPS device associated with a TTY is possible but needs 17 * the device or symlink to the PPS device with the given name exists, 208 * given the dir-fd of a pps instance dir in the linux sysfs tree, get 209 * the device IDs for the PPS device and the associated TTY. 232 /* 'dev' holds the device ID of the PPS device as 'major:minor' in getPpsTuple() 234 * the PPS device itself, as in 'path' above??? But nooooo.... in getPpsTuple() [all …]
|
H A D | refclock_atom.c | 2 * refclock_atom - clock driver for 1-pps signals 25 * This driver furnishes an interface for pulse-per-second (PPS) signals 34 * itself. There are two ways to connect the PPS signal, normally at TTL 38 * to connect the PPS signal directly to pin 10 (ACK) of a PC paralell 45 * the API with multiple PPS drivers and multiple handles per driver. If 58 * important difference. If this driver becomes the PPS driver according 63 * infrequent, but a reliable PPS signal, such as from an Ultra Stable 68 * The PPS timestamp is captured on the rising (assert) edge if flag2 is 70 * (default), the kernel PPS support is disabled; if lit it is enabled. 79 #define DEVICE "/dev/pps [all...] |
H A D | refclock_gpsdjson.c | 18 * - To work properly, this driver needs PPS and TPV/TOFF sentences 20 * PPS signal. 31 * This driver works slightly different from most others, as the PPS 33 * connection. This makes using both the PPS data and the serial data 35 * raw PPS stream to the core of NTPD. 41 * secondary unit is feed with the PPS samples only and can act as a PPS 71 * ?WATCH={"device":"/dev/gps0","enable":true,"json":true,"pps":true};<CRLF> 175 * + STRICT means only feed clock samples when a valid STI/PPS pair is 177 * from PPS. Masks the serial data jitter as long PPS is available, 178 * but can rapidly deteriorate once PPS drops out. [all …]
|
H A D | ntp_refclock.c | 527 * Important for PPS users: Normally, the pp->lastrec is set to the 530 * nanoseconds). When a PPS offset is available, pp->nsec is forced to 531 * zero and the fraction for pp->lastrec is set to the PPS offset. 1077 * necessary for the kernel pps mods to work. in refclock_setup() 1155 * necessary for the kernel pps mods to work. in refclock_setup() 1462 * Solaris serial ports provide PPS pulse capture only on the in refclock_params() 1478 * If flag3 is lit, select the kernel PPS if we can. in refclock_params() 1505 * This routine is called once per second. It snatches the PPS 1524 * most recent PPS timestamp. in refclock_pps() 1549 /* [Bug 2689] Discard the first sample we read -- if the PPS in refclock_pps() [all...] |
/freebsd/sys/dev/ppbus/ |
H A D | pps.c | 12 * This driver implements a draft-mogul-pps-api-02.txt PPS source. 36 #define PPS_NAME "pps" /* our official name */ 42 struct pps_state pps[9]; member 130 sx_init(&sc->lock, "pps"); in ppsattach() 138 sc->pps[0].ppscap = PPS_CAPTUREASSERT | PPS_ECHOASSERT; in ppsattach() 139 sc->pps[0].driver_abi = PPS_ABI_VERSION; in ppsattach() 140 sc->pps[0].driver_mtx = ppb_get_lock(ppbus); in ppsattach() 143 pps_init_abi(&sc->pps[0]); in ppsattach() 192 sc->pps[ in ppsattach() [all...] |
/freebsd/sys/kern/ |
H A D | kern_tc.c | 1409 * PPS events, so instead we poll them. There is a finite risk that in tc_windup() 1577 * RFC 2783 PPS-API implementation. 1585 abi_aware(struct pps_state *pps, int vers) in abi_aware() argument 1588 return ((pps->kcmode & KCMODE_ABIFLAG) && pps->driver_abi >= vers); in abi_aware() 1592 pps_fetch(struct pps_fetch_args *fapi, struct pps_state *pps) in pps_fetch() argument 1616 aseq = atomic_load_int(&pps->ppsinfo.assert_sequence); in pps_fetch() 1617 cseq = atomic_load_int(&pps->ppsinfo.clear_sequence); in pps_fetch() 1618 while (aseq == atomic_load_int(&pps->ppsinfo.assert_sequence) && in pps_fetch() 1619 cseq == atomic_load_int(&pps->ppsinfo.clear_sequence)) { in pps_fetch() 1620 if (abi_aware(pps, 1) && pps->driver_mtx != NULL) { in pps_fetch() [all …]
|
H A D | kern_ntptime.c | 53 FEATURE(pps_sync, "Support usage of external PPS signal by kernel PLL"); 178 * The following variables are used when a pulse-per-second (PPS) signal 181 * controlled by the PPS signal. 187 #define PPS_VALID 120 /* PPS signal watchdog max (s) */ 188 #define PPS_MAXWANDER 100000 /* max PPS wander (ns/s) */ 203 * PPS signal quality monitors 233 * PPS signal lost when either time or frequency synchronization in ntp_is_time_error() 240 * PPS jitter exceeded when time synchronization requested in ntp_is_time_error() 245 * PPS wander exceeded or calibration error when frequency in ntp_is_time_error() 587 * whether the PPS signal is operating. Note that the in ntp_update_second() [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/pps/ |
H A D | pps-gpio.txt | 1 Device-Tree Bindings for a PPS Signal on GPIO 3 These properties describe a PPS (pulse-per-second) signal connected to 7 - compatible: should be "pps-gpio" 8 - gpios: one PPS GPIO in the format described by ../gpio/gpio.txt 10 Additional required properties for the PPS ECHO functionality: 11 - echo-gpios: one PPS ECHO GPIO in the format described by ../gpio/gpio.txt 19 pps { 29 compatible = "pps-gpio";
|
/freebsd/contrib/ntp/kernel/sys/ |
H A D | timex.h | 25 * defines for PPS phase-lock loop. 28 * Revised status codes and structures for external clock and PPS 146 * PPS discipline code is configured (PPS_SYNC), the oscillator time and 151 * MAXTIME is the maximum jitter tolerance of the PPS signal if the 152 * kernel PPS discipline code is configured (PPS_SYNC). 160 #define MAXTIME (200L << PPS_AVG) /* max PPS error (jitter) (200 us) */ 169 * The following defines are used only if a pulse-per-second (PPS) 173 * lock loop used to discipline the CPU clock oscillator to the PPS 182 * PPS_VALID is the maximum interval before the PPS signal is considered 188 #define PPS_AVG 2 /* pps averaging constant (shift) */ [all …]
|
/freebsd/contrib/wpa/hs20/client/ |
H A D | oma_dm_client.c | 501 xml_node_t *add, xml_node_t *pps, in oma_dm_run_add() argument 538 wpa_printf(MSG_INFO, "Add command for PPS node %s", pos); in oma_dm_run_add() 540 pps_node = get_node(ctx->xml, pps, pos); in oma_dm_run_add() 542 wpa_printf(MSG_INFO, "Specified PPS node exists already"); in oma_dm_run_add() 554 pps_node = get_node(ctx->xml, pps, uri); in oma_dm_run_add() 562 /* Add at root of PPS MO */ in oma_dm_run_add() 563 pps_node = pps; in oma_dm_run_add() 647 if (update_pps_file(ctx, pps_fname, pps) < 0) in oma_dm_run_add() 657 xml_node_t *pps, const char *pps_fname) in oma_dm_add() argument 689 ret = oma_dm_run_add(ctx, locuri, add, pps, pps_fname); in oma_dm_add() [all …]
|
H A D | osu_client.c | 227 wpa_printf(MSG_INFO, "PPS for certificate credential - fqdn=%s", fqdn); in process_est_cert() 234 write_result(ctx, "Invalid client certificate SHA256 hash value in PPS"); in process_est_cert() 254 wpa_printf(MSG_INFO, "Client certificate from EST does not match fingerprint from PPS MO"); in process_est_cert() 255 write_result(ctx, "Client certificate from EST does not match fingerprint from PPS MO"); in process_est_cert() 259 wpa_printf(MSG_INFO, "Client certificate from EST matches PPS MO"); in process_est_cert() 398 xml_node_t *pps, *node; in cmd_dl_osu_ca() local 401 pps = node_from_file(ctx->xml, pps_fname); in cmd_dl_osu_ca() 402 if (pps == NULL) { in cmd_dl_osu_ca() 407 node = get_child_node(ctx->xml, pps, in cmd_dl_osu_ca() 410 wpa_printf(MSG_INFO, "No SubscriptionUpdate/TrustRoot/CertURL found from PPS"); in cmd_dl_osu_ca() [all …]
|
H A D | spp_client.c | 147 static int process_update_node(struct hs20_osu_client *ctx, xml_node_t *pps, in process_update_node() argument 261 wpa_printf(MSG_INFO, "Update command for PPS node %s", pos); in process_update_node() 263 node = get_node(ctx->xml, pps, pos); in process_update_node() 272 parent = pps; in process_update_node() 275 parent = get_node(ctx->xml, pps, pos); in process_update_node() 294 const char *pps_fname, xml_node_t *pps) in update_pps() argument 296 wpa_printf(MSG_INFO, "Updating PPS based on updateNode element(s)"); in update_pps() 299 if (process_update_node(ctx, pps, update) < 0) in update_pps() 303 return update_pps_file(ctx, pps_fname, pps); in update_pps() 349 wpa_printf(MSG_INFO, "PPS file name no known"); in hs20_spp_upload_mo() [all …]
|
H A D | osu_client.h | 70 void get_user_pw(struct hs20_osu_client *ctx, xml_node_t *pps, 73 xml_node_t *pps); 83 xml_node_t *pps); 88 xml_node_t *pps); 101 xml_node_t *pps); 106 xml_node_t *pps);
|
/freebsd/lib/libsys/ |
H A D | ntp_adjtime.2 | 69 In the following, all variables that refer PPS are only relevant if 92 * only if the PPS signal discipline is configured in the 95 long ppsfreq; /* pps frequency (scaled ppm) (ro) */ 96 long jitter; /* pps jitter (us) (ro) */ 98 long stabil; /* pps stability (scaled ppm) (ro) */ 156 Enable PPS freq discipline (read-write). 158 Enable PPS time discipline (read-write). 203 Logarithm to base 2 of the interval duration in seconds (PPS, 214 Count of calibration intervals (PPS, read-only). 219 or where the calibration interval jitter exceeded two ticks (PPS,
|
/freebsd/sys/sys/ |
H A D | timex.h | 69 #define MOD_PPSMAX 0x0040 /* set PPS maximum averaging time */ 80 #define STA_PPSFREQ 0x0002 /* enable PPS freq discipline (rw) */ 81 #define STA_PPSTIME 0x0004 /* enable PPS time discipline (rw) */ 87 #define STA_PPSSIGNAL 0x0100 /* PPS signal present (ro) */ 88 #define STA_PPSJITTER 0x0200 /* PPS signal jitter exceeded (ro) */ 89 #define STA_PPSWANDER 0x0400 /* PPS signal wander exceeded (ro) */ 90 #define STA_PPSERROR 0x0800 /* PPS signal calibration error (ro) */ 140 * only if the PPS signal discipline is configured in the 144 long ppsfreq; /* PPS frequency (scaled PPM) (ro) */ 145 long jitter; /* PPS jitter (ns/us) (ro) */ [all …]
|
/freebsd/share/man/man4/ |
H A D | ucom.4 | 81 Enables and configure PPS capture mode as described below. 83 .Sh Pulse Per Second (PPS) Timing Interface 86 driver can capture PPS timing information as defined in RFC 2783. 90 To use the PPS capture feature with 97 sysctl configures the PPS capture mode.
|