Home
last modified time | relevance | path

Searched full:precise (Results 1 – 25 of 53) sorted by relevance

123

/Zephyr-latest/dts/bindings/rtc/
Dnordic,nrf-rtc.yaml23 # through PPI channel which ensures precise timing. If disabled then
/Zephyr-latest/dts/bindings/i2c/
Dst,stm32-i2c-v2.yaml29 Precise timings values for a given Hardware can be pre-computed
/Zephyr-latest/include/zephyr/arch/common/
Dexc_handle.h23 * To ensure precise control of the state of registers and the stack pointer,
/Zephyr-latest/dts/bindings/battery/
Dbattery.yaml16 the precise "lithium-ion-X" options.
/Zephyr-latest/doc/hardware/peripherals/
Dgnss.rst14 additionally provide a precise time synchronization mechanism,
/Zephyr-latest/subsys/net/l2/ieee802154/
Dieee802154_radio_csma_ca.c48 * radio API should expose a precise radio clock instead (which may in unslotted_csma_ca_channel_access()
/Zephyr-latest/soc/atmel/sam/common/
DKconfig17 Says n if you do not need accurate and precise timers. The slow clock
Dsoc_gpio.h192 * or may not be taken into account, depending on the precise timing of its
/Zephyr-latest/dts/bindings/led_strip/
Dworldsemi,ws2812-gpio.yaml17 type of LEDs used, consult the data-sheet for the precise timings.
/Zephyr-latest/include/zephyr/net/
Dptp_time.h83 * between clocks based on sufficiently precise conversion algorithms.
151 * A precise definition of PTP timestamps and their uses in Zephyr is given in
Dnet_time.h56 * specific hardware counter, will never be "precise" but only can be "good
/Zephyr-latest/tests/kernel/timer/timer_behavior/
DREADME8 Timers are meant to be precise and accurate. This test validates an implementation is both.
/Zephyr-latest/include/zephyr/sys/
Dtimeutil.h89 * This value is assumed to be precise, but may drift depending on
293 * A "precise" time source may have error on the order of 2000 ppb.
/Zephyr-latest/doc/safety/
Dsafety_requirements.rst96 * Clear (concise, succinct, simple, precise)
/Zephyr-latest/subsys/net/lib/ptp/
Dmsg.h150 /** Precise timestamp of Sync message corresponding to that message. */
206 /** Precise timestamp of Pdelay_Resp message corresponding to that message. */
/Zephyr-latest/soc/ite/ec/it8xxx2/
DKconfig163 The LCVCO is a highly precise clock controller used for
/Zephyr-latest/boards/st/nucleo_f429zi/
Dnucleo_f429zi.dts84 clock-frequency = <DT_FREQ_M(168)>; /* highest value to get a precise USB clock */
/Zephyr-latest/boards/st/nucleo_f446ze/
Dnucleo_f446ze.dts81 clock-frequency = <DT_FREQ_M(168)>; /* highest value to get a precise USB clock */
/Zephyr-latest/drivers/gnss/gnss_u_blox_protocol/
Dgnss_u_blox_protocol.h18 /* TODO: check what is the precise waiting time for each message. */
/Zephyr-latest/samples/arch/mpu/mpu_test/
DREADME.rst53 <err> os: Precise data bus error
/Zephyr-latest/subsys/bluetooth/host/shell/
Dcs.c472 "- RTT AA only is 10ns precise: %s\n" in cmd_read_local_supported_capabilities()
475 "- RTT sounding is 10ns precise: %s\n" in cmd_read_local_supported_capabilities()
478 "- RTT random payload is 10ns precise: %s\n" in cmd_read_local_supported_capabilities()
/Zephyr-latest/doc/kernel/services/timing/
Dclocks.rst80 Apps with precise timing requirements (that are willing to do their
113 within another timer's callback will always be calculated with a precise offset
/Zephyr-latest/drivers/sensor/aosong/dht/
Ddht.c125 * not very precise, compute the threshold for deciding between a in dht_sample_fetch()
/Zephyr-latest/doc/kernel/memory_management/
Dvirtual_memory.rst62 more precise access control.
/Zephyr-latest/samples/subsys/logging/logger/src/
Dmain.c283 * as precise timing API is accessible only from the kernel. in log_demo_thread()

123