Searched refs:timestamps (Results 1 – 18 of 18) sorted by relevance
| /Zephyr-Core-3.7.0/samples/boards/nrf/nrf53_sync_rtc/ |
| D | README.rst | 18 that before synchronization procedure is completed, timestamps differ significantly
19 and once procedure is completed timestamps are synchronized. Network core timestamp
75 Observe that initially logging timestamps for the corresponding events on both cores
76 do not match. Same with local and remote timestamps reported on network core. After
|
| /Zephyr-Core-3.7.0/soc/nordic/nrf53/ |
| D | soc.c | 72 static uint32_t timestamps[5]; in nrf53_anomaly_160_check() local
75 uint8_t oldest = (current + 1) % ARRAY_SIZE(timestamps); in nrf53_anomaly_160_check()
80 (now - timestamps[oldest]) < (window_cycles + 1)) { in nrf53_anomaly_160_check()
101 timestamps[current] = k_cycle_get_32(); in nrf53_anomaly_160_check()
|
| /Zephyr-Core-3.7.0/scripts/pylib/twister/twisterlib/ |
| D | twister_main.py | 27 def setup_logging(outdir, log_file, verbose, timestamps): argument
45 if timestamps:
109 setup_logging(options.outdir, options.log_file, VERBOSE, options.timestamps)
|
| /Zephyr-Core-3.7.0/drivers/can/ |
| D | Kconfig | 98 bool "Receiving timestamps"
102 is initialized. Not all CAN controllers support timestamps.
|
| /Zephyr-Core-3.7.0/soc/ |
| D | Kconfig | 66 timestamps and cycle count.
|
| /Zephyr-Core-3.7.0/samples/net/ptp/ |
| D | README.rst | 29 timestamps for sent and received Ethernet frames.
|
| /Zephyr-Core-3.7.0/subsys/logging/ |
| D | Kconfig.mode | 37 but not runtime filtering. There are no timestamps, prefixes,
|
| D | Kconfig.formatting | 182 which timestamps are printed as fixed point values with seconds on the
|
| /Zephyr-Core-3.7.0/subsys/bluetooth/ |
| D | Kconfig.iso | 112 timestamps.
|
| /Zephyr-Core-3.7.0/boards/ |
| D | Kconfig | 137 timestamps and cycle count.
|
| /Zephyr-Core-3.7.0/doc/kernel/ |
| D | timeutil.rst | 61 Sub-second timestamps like ``struct timespec`` can also use this to produce
218 between their timestamps.
|
| /Zephyr-Core-3.7.0/subsys/net/l2/ethernet/gptp/ |
| D | Kconfig | 10 and handles network packet timestamps.
|
| /Zephyr-Core-3.7.0/subsys/net/lib/ptp/ |
| D | Kconfig | 15 and handles network packet timestamps. The protocol's implementation
|
| /Zephyr-Core-3.7.0/samples/net/gptp/ |
| D | README.rst | 32 timestamps for sent and received Ethernet frames.
|
| /Zephyr-Core-3.7.0/doc/hardware/peripherals/can/ |
| D | shell.rst | 32 * :kconfig:option:`CONFIG_CAN_RX_TIMESTAMP` enables printing of timestamps for received CAN frames.
|
| /Zephyr-Core-3.7.0/doc/services/logging/ |
| D | index.rst | 630 Logging does not provide any mechanism for synchronizing timestamps across multiple
636 recalculates timestamps, there are 2 options:
|
| /Zephyr-Core-3.7.0/doc/releases/ |
| D | release-notes-3.5.rst | 860 * Time and timestamps in the network subsystem, PTP and IEEE 802.15.4
862 Fields for timed TX and TX/RX timestamps have been consolidated. See
|
| D | release-notes-1.14.rst | 2178 * :github:`9043` - New logging subsystem's timestamps wrap a little before the 3-minute mark
|
