Home
last modified time | relevance | path

Searched full:timestamps (Results 1 – 25 of 28) sorted by relevance

12

/Zephyr-Core-3.5.0/include/zephyr/net/
Dptp_time.h39 * any other well-defined context in which precision structured timestamps are
45 * In the context of (g)PTP, @em timestamps designate the time, relative to a
55 * timestamps are measured relative to the same local clock but with a
77 * Applications that use timestamps across different subsystems or media must
79 * and interpret timestamps accordingly. Applications must further ensure that
80 * timestamps are either all referenced to the same local clock or convert
83 * Timestamps may be measured on ingress (RX timestamps) or egress (TX
84 * timestamps) of network messages. Timestamps can also be used to schedule a
95 * * IEEE 802.15.4 timed TX and RX: Timestamps designate the point in time at
100 * depending on the context. In the context of beacon timestamps, the
[all …]
Dnet_time.h9 * @brief Representation of nanosecond resolution elapsed time and timestamps in
/Zephyr-Core-3.5.0/samples/boards/nrf/nrf53_sync_rtc/
DREADME.rst18 that before synchronization procedure is completed, timestamps differ significantly
19 and once procedure is completed timestamps are synchronized. Network core timestamp
73 Observe that initially logging timestamps for the corresponding events on both cores
74 do not match. Same with local and remote timestamps reported on network core. After
/Zephyr-Core-3.5.0/drivers/can/
DKconfig64 bool "Receiving timestamps"
68 is initialized. Not all CAN controllers support timestamps.
/Zephyr-Core-3.5.0/drivers/timer/
Daltera_avalon_timer_hal.c53 * 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-Core-3.5.0/scripts/pylib/twister/twisterlib/
Dtwister_main.py27 def setup_logging(outdir, log_file, verbose, timestamps): argument
45 if timestamps:
106 setup_logging(options.outdir, options.log_file, VERBOSE, options.timestamps)
Denvironment.py615 parser.add_argument("--timestamps",
/Zephyr-Core-3.5.0/soc/
DKconfig63 timestamps and cycle count.
/Zephyr-Core-3.5.0/subsys/logging/
DKconfig.mode36 but not runtime filtering. There are no timestamps, prefixes,
DKconfig.formatting174 which timestamps are printed as fixed point values with seconds on the
/Zephyr-Core-3.5.0/tests/subsys/mgmt/mcumgr/os_mgmt_info/src/
Dbuild_date.c65 /* 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-Core-3.5.0/dts/bindings/can/
Dmicrochip,mcp251xfd.yaml60 Prescaler value for computing the timestamps of received messages.
/Zephyr-Core-3.5.0/soc/arm/nordic_nrf/nrf53/
Dsoc.c103 static uint32_t timestamps[5]; in nrf53_anomaly_160_check() local
106 uint8_t oldest = (current + 1) % ARRAY_SIZE(timestamps); in nrf53_anomaly_160_check()
111 (now - timestamps[oldest]) < (window_cycles + 1)) { in nrf53_anomaly_160_check()
132 timestamps[current] = k_cycle_get_32(); in nrf53_anomaly_160_check()
/Zephyr-Core-3.5.0/boards/
DKconfig122 timestamps and cycle count.
/Zephyr-Core-3.5.0/subsys/bluetooth/
DKconfig.iso105 HCI ISO Data packet with a size of 255, without utilizing timestamps.
/Zephyr-Core-3.5.0/subsys/net/l2/ethernet/gptp/
DKconfig10 and handles network packet timestamps.
Dgptp_md.c284 /* Get peer corrected timestamps. */ in gptp_md_compute_prop_time()
/Zephyr-Core-3.5.0/doc/kernel/
Dtimeutil.rst61 Sub-second timestamps like ``struct timespec`` can also use this to produce
218 between their timestamps.
/Zephyr-Core-3.5.0/samples/net/gptp/
DREADME.rst32 timestamps for sent and received Ethernet frames.
/Zephyr-Core-3.5.0/subsys/net/ip/
Dicmpv4.c216 * this option to the end of timestamps plus one (i.e., it in icmpv4_update_time_stamp()
/Zephyr-Core-3.5.0/modules/openthread/platform/
Dradio.c238 * @brief Convert 32-bit (potentially wrapped) OpenThread microsecond timestamps
239 * to 64-bit Zephyr network subsystem nanosecond timestamps.
/Zephyr-Core-3.5.0/doc/services/logging/
Dindex.rst619 Logging does not provide any mechanism for synchronizing timestamps across multiple
625 recalculates timestamps, there are 2 options:
/Zephyr-Core-3.5.0/drivers/dai/intel/dmic/
Ddmic.c457 /* Clear NTK to enable successive timestamps */ in dai_timestamp_dmic_get()
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-3.5.rst857 * Time and timestamps in the network subsystem, PTP and IEEE 802.15.4
859 Fields for timed TX and TX/RX timestamps have been consolidated. See
/Zephyr-Core-3.5.0/drivers/ethernet/
Deth_xlnx_gem.c10 * - Hardware timestamps not considered.

12