| /Zephyr-latest/include/zephyr/net/ |
| D | ptp_time.h | 41 * any other well-defined context in which precision structured timestamps are
47 * In the context of (g)PTP, @em timestamps designate the time, relative to a
57 * timestamps are measured relative to the same local clock but with a
79 * Applications that use timestamps across different subsystems or media must
81 * and interpret timestamps accordingly. Applications must further ensure that
82 * timestamps are either all referenced to the same local clock or convert
85 * Timestamps may be measured on ingress (RX timestamps) or egress (TX
86 * timestamps) of network messages. Timestamps can also be used to schedule a
97 * * IEEE 802.15.4 timed TX and RX: Timestamps designate the point in time at
102 * depending on the context. In the context of beacon timestamps, the
[all …]
|
| D | net_time.h | 9 * @brief Representation of nanosecond resolution elapsed time and timestamps in
|
| /Zephyr-latest/samples/boards/nordic/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-latest/drivers/timer/ |
| D | altera_avalon_timer_hal.c | 53 * use a timer instance for both the system clock and timestamps in sys_clock_cycle_get_32()
63 * To properly obtain timestamps, the CPU must be configured with in sys_clock_cycle_get_32()
|
| /Zephyr-latest/tests/benchmarks/latency_measure/src/ |
| D | timing_sc.c | 100 * Both start and finish timestamps were obtained in timestamp_overhead_adjustment()
115 * Both start and finish timestamps were obtained in timestamp_overhead_adjustment()
|
| D | int_to_thread.c | 94 /* 3. Obtain the start and finish timestamps */ in start_thread_entry()
|
| /Zephyr-latest/drivers/can/ |
| D | Kconfig | 98 bool "Receiving timestamps"
102 is initialized. Not all CAN controllers support timestamps.
|
| /Zephyr-latest/soc/ |
| D | Kconfig | 68 timestamps and cycle count.
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | twister_main.py | 28 def setup_logging(outdir, log_file, log_level, timestamps): argument
42 if timestamps:
110 setup_logging(options.outdir, options.log_file, options.log_level, options.timestamps)
|
| /Zephyr-latest/subsys/logging/ |
| D | Kconfig.mode | 37 but not runtime filtering. There are no timestamps, prefixes,
|
| D | Kconfig.formatting | 206 which timestamps are printed as fixed point values with seconds on the
|
| /Zephyr-latest/tests/subsys/mgmt/mcumgr/os_mgmt_info/src/ |
| D | build_date.c | 65 /* Convert times to separate fields and then to timestamps which can be compared */ in time_string_to_seconds()
142 /* Extract time strings into timestamps */ in ZTEST()
238 /* Extract time strings into timestamps */ in ZTEST()
|
| /Zephyr-latest/dts/bindings/can/ |
| D | microchip,mcp251xfd.yaml | 56 Prescaler value for computing the timestamps of received messages.
|
| /Zephyr-latest/samples/net/ptp/ |
| D | README.rst | 29 timestamps for sent and received Ethernet frames.
|
| /Zephyr-latest/soc/nordic/nrf53/ |
| D | soc.c | 104 static uint32_t timestamps[5]; in nrf53_anomaly_160_check() local
107 uint8_t oldest = (current + 1) % ARRAY_SIZE(timestamps); in nrf53_anomaly_160_check()
112 (now - timestamps[oldest]) < (window_cycles + 1)) { in nrf53_anomaly_160_check()
133 timestamps[current] = k_cycle_get_32(); in nrf53_anomaly_160_check()
|
| /Zephyr-latest/subsys/bluetooth/ |
| D | Kconfig.iso | 112 timestamps.
|
| /Zephyr-latest/boards/ |
| D | Kconfig | 153 timestamps and cycle count.
|
| /Zephyr-latest/subsys/net/l2/ethernet/gptp/ |
| D | Kconfig | 10 and handles network packet timestamps.
|
| /Zephyr-latest/subsys/net/lib/ptp/ |
| D | Kconfig | 15 and handles network packet timestamps. The protocol's implementation
|
| /Zephyr-latest/doc/kernel/ |
| D | timeutil.rst | 61 Sub-second timestamps like ``struct timespec`` can also use this to produce
218 between their timestamps.
|
| /Zephyr-latest/doc/services/logging/ |
| D | cs_stm.rst | 149 The file will contain timestamps and the log messages in a format that is human-readable.
154 Decoding artifacts or incorrect timestamps might occur when rerunning the process.
|
| /Zephyr-latest/samples/net/gptp/ |
| D | README.rst | 32 timestamps for sent and received Ethernet frames.
|
| /Zephyr-latest/subsys/bluetooth/audio/shell/ |
| D | bap_usb.c | 214 const uint8_t ts_jitter_us = 100; /* timestamps may have jitter */ in bap_usb_add_frame_to_usb()
245 * This is done by comparing the timestamps of the frames, and in the case that they are the in bap_usb_add_frame_to_usb()
|
| /Zephyr-latest/subsys/net/lib/sntp/ |
| D | sntp.c | 105 NET_DBG("Invalid timestamps from SNTP server"); in parse_response()
|
| /Zephyr-latest/doc/hardware/peripherals/can/ |
| D | shell.rst | 32 * :kconfig:option:`CONFIG_CAN_RX_TIMESTAMP` enables printing of timestamps for received CAN frames.
|
