Home
last modified time | relevance | path

Searched refs:drift (Results 1 – 16 of 16) sorted by relevance

/Zephyr-latest/tests/kernel/timer/timer_behavior/
DKconfig31 int "Maximum drift in microseconds allowed (should be about 1 period allowance)"
35 int "Maximum drift percentage for the timer period"
57 int "Maximum drift in PPM for tests using external tool"
60 Parts Per Million of allowed drift when using an external tool
64 int "Maximum timer period drift in PPM for tests using external tool"
67 Parts Per Million of allowed period drift when using an external tool
DREADME1 # Test a timer implementations variance and long term drift
6 2. Periodic timers do not drift in either direction from expected total time.
48 to account for expected drift in the test and between the DUT and the external
70 they tend to drift. To be able to account for this drift, the external test
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/openisa/lll/
Dlll_conn.c599 e->drift.start_to_address_actual_us = in isr_done()
601 e->drift.window_widening_event_us = in isr_done()
603 e->drift.preamble_to_addr_us = preamble_to_addr_us; in isr_done()
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/nordic/lll/
Dlll_sync_iso.c520 e->drift.preamble_to_addr_us = addr_us_get(lll->phy); in isr_rx_estab()
521 e->drift.start_to_address_actual_us = in isr_rx_estab()
523 e->drift.window_widening_event_us = in isr_rx_estab()
1305 e->drift.preamble_to_addr_us = addr_us_get(lll->phy); in isr_rx_done()
1306 e->drift.start_to_address_actual_us = in isr_rx_done()
1308 e->drift.window_widening_event_us = in isr_rx_done()
Dlll_conn.c996 e->drift.start_to_address_actual_us =
998 e->drift.window_widening_event_us =
1000 e->drift.preamble_to_addr_us = preamble_to_addr_us;
Dlll_sync.c1199 e->drift.preamble_to_addr_us = addr_us_get(lll->phy); in isr_rx_done_cleanup()
1200 e->drift.start_to_address_actual_us = in isr_rx_done_cleanup()
1202 e->drift.window_widening_event_us = lll->window_widening_event_us; in isr_rx_done_cleanup()
Dlll_peripheral_iso.c1231 e->drift.start_to_address_actual_us = in isr_done()
1233 e->drift.window_widening_event_us = EVENT_US_FRAC_TO_US( in isr_done()
1235 e->drift.preamble_to_addr_us = preamble_to_addr_us; in isr_done()
/Zephyr-latest/drivers/clock_control/
DKconfig.stm3285 affected by slow clock drift such as RTC or IWDG, in collaboration with
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/
Dlll.h555 struct event_done_extra_drift drift; member
Dull.c2304 done->extra.drift.start_to_address_actual_us; in ull_drift_ticks_get()
2306 done->extra.drift.window_widening_event_us; in ull_drift_ticks_get()
2308 done->extra.drift.preamble_to_addr_us; in ull_drift_ticks_get()
Dull_llcp.c1524 done->extra.drift.start_to_address_actual_us,
1525 (-done->extra.drift.preamble_to_addr_us));
/Zephyr-latest/doc/hardware/peripherals/
Drtc.rst140 * RTC time will drift over time.
/Zephyr-latest/boards/native/native_sim/doc/
Dindex.rst259 This can be controlled with the ``--rt-ratio=<ratio>`` and ``-rt-drift=<drift>``
261 underlying mechanism, and that ``drift`` is by definition equal to
268 Similarly if ``--rt-drift=-100e-6`` is given, the simulated time will progress
/Zephyr-latest/doc/kernel/services/timing/
Dclocks.rst115 introducing systematic clock drift over time.
/Zephyr-latest/doc/build/kconfig/
Dtips.rst308 of the selecting and selected symbol will never drift out of sync, e.g. when
/Zephyr-latest/doc/releases/
Drelease-notes-3.3.rst3131 * :github:`53010` - timers: large drift if hardware timer has a low resolution