Searched full:precise (Results 1 – 25 of 53) sorted by relevance
123
/Zephyr-latest/dts/bindings/rtc/ |
D | nordic,nrf-rtc.yaml | 23 # through PPI channel which ensures precise timing. If disabled then
|
/Zephyr-latest/dts/bindings/i2c/ |
D | st,stm32-i2c-v2.yaml | 29 Precise timings values for a given Hardware can be pre-computed
|
/Zephyr-latest/include/zephyr/arch/common/ |
D | exc_handle.h | 23 * To ensure precise control of the state of registers and the stack pointer,
|
/Zephyr-latest/dts/bindings/battery/ |
D | battery.yaml | 16 the precise "lithium-ion-X" options.
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | gnss.rst | 14 additionally provide a precise time synchronization mechanism,
|
/Zephyr-latest/subsys/net/l2/ieee802154/ |
D | ieee802154_radio_csma_ca.c | 48 * radio API should expose a precise radio clock instead (which may in unslotted_csma_ca_channel_access()
|
/Zephyr-latest/soc/atmel/sam/common/ |
D | Kconfig | 17 Says n if you do not need accurate and precise timers. The slow clock
|
D | soc_gpio.h | 192 * or may not be taken into account, depending on the precise timing of its
|
/Zephyr-latest/dts/bindings/led_strip/ |
D | worldsemi,ws2812-gpio.yaml | 17 type of LEDs used, consult the data-sheet for the precise timings.
|
/Zephyr-latest/include/zephyr/net/ |
D | ptp_time.h | 83 * between clocks based on sufficiently precise conversion algorithms. 151 * A precise definition of PTP timestamps and their uses in Zephyr is given in
|
D | net_time.h | 56 * specific hardware counter, will never be "precise" but only can be "good
|
/Zephyr-latest/tests/kernel/timer/timer_behavior/ |
D | README | 8 Timers are meant to be precise and accurate. This test validates an implementation is both.
|
/Zephyr-latest/include/zephyr/sys/ |
D | timeutil.h | 89 * 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/ |
D | safety_requirements.rst | 96 * Clear (concise, succinct, simple, precise)
|
/Zephyr-latest/subsys/net/lib/ptp/ |
D | msg.h | 150 /** 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/ |
D | Kconfig | 163 The LCVCO is a highly precise clock controller used for
|
/Zephyr-latest/boards/st/nucleo_f429zi/ |
D | nucleo_f429zi.dts | 84 clock-frequency = <DT_FREQ_M(168)>; /* highest value to get a precise USB clock */
|
/Zephyr-latest/boards/st/nucleo_f446ze/ |
D | nucleo_f446ze.dts | 81 clock-frequency = <DT_FREQ_M(168)>; /* highest value to get a precise USB clock */
|
/Zephyr-latest/drivers/gnss/gnss_u_blox_protocol/ |
D | gnss_u_blox_protocol.h | 18 /* TODO: check what is the precise waiting time for each message. */
|
/Zephyr-latest/samples/arch/mpu/mpu_test/ |
D | README.rst | 53 <err> os: Precise data bus error
|
/Zephyr-latest/subsys/bluetooth/host/shell/ |
D | cs.c | 472 "- 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/ |
D | clocks.rst | 80 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/ |
D | dht.c | 125 * not very precise, compute the threshold for deciding between a in dht_sample_fetch()
|
/Zephyr-latest/doc/kernel/memory_management/ |
D | virtual_memory.rst | 62 more precise access control.
|
/Zephyr-latest/samples/subsys/logging/logger/src/ |
D | main.c | 283 * as precise timing API is accessible only from the kernel. in log_demo_thread()
|
123