Home
last modified time | relevance | path

Searched refs:delays (Results 1 – 22 of 22) sorted by relevance

/Zephyr-Core-3.4.0/drivers/i2c/
Di2c_bitbang.c52 context->delays[T_LOW] = NS_TO_SYS_CLOCK_HW_CYCLES(4700); in i2c_bitbang_configure()
53 context->delays[T_HIGH] = NS_TO_SYS_CLOCK_HW_CYCLES(4000); in i2c_bitbang_configure()
56 context->delays[T_LOW] = NS_TO_SYS_CLOCK_HW_CYCLES(1300); in i2c_bitbang_configure()
57 context->delays[T_HIGH] = NS_TO_SYS_CLOCK_HW_CYCLES(600); in i2c_bitbang_configure()
98 i2c_delay(context->delays[T_LOW]); in i2c_start()
100 i2c_delay(context->delays[T_SU_STA]); in i2c_start()
103 i2c_delay(context->delays[T_HD_STA]); in i2c_start()
106 i2c_delay(context->delays[T_LOW]); in i2c_start()
113 i2c_delay(context->delays[T_HIGH]); in i2c_repeated_start()
115 i2c_delay(context->delays[T_SU_STA]); in i2c_repeated_start()
[all …]
Di2c_bitbang.h31 uint32_t delays[2]; member
/Zephyr-Core-3.4.0/soc/nios2/nios2f-zephyr/cpu/
Dghrd_timing.sdc7 # JTAG Signal Constraints constrain the TCK port, assuming a 10MHz JTAG clock and 3ns delays
/Zephyr-Core-3.4.0/samples/kernel/metairq_dispatch/
DREADME.rst36 latencies and lower processing delays, as expected.
43 priority will experience some load-dependent delays, as the CPU
88 (intended) for non-cooperative threads like T2 and T3 which is attributed to delays
/Zephyr-Core-3.4.0/samples/boards/nrf/system_off/
DREADME.rst23 that use unbounded delays to wait for startup.
/Zephyr-Core-3.4.0/drivers/flash/
DKconfig.nor76 enter and exit delays is acceptable.
/Zephyr-Core-3.4.0/doc/connectivity/networking/api/
Dnet_timeout.rst26 allow for delays that are represented as unsigned 32-bit values counting
/Zephyr-Core-3.4.0/doc/kernel/services/threads/
Dnothread.rst34 * Non-sleeping delays e.g. :c:func:`k_busy_wait`.
Dworkqueue.rst45 which could introduce delays.
/Zephyr-Core-3.4.0/scripts/coccinelle/
Dint_ms_to_timeout.cocci227 // ** Convert timeout-valued delays in K_THREAD_DEFINE with durations
/Zephyr-Core-3.4.0/doc/connectivity/bluetooth/api/mesh/
Dcore.rst28 deferred may cause unintended delays during processing of log messages. This in
/Zephyr-Core-3.4.0/drivers/modem/
DKconfig.hl7800317 This mode delays the validity of modem info.
/Zephyr-Core-3.4.0/doc/services/pm/
Ddevice_runtime.rst95 unnecessary delays since the application will not get the operation result until
/Zephyr-Core-3.4.0/doc/build/dts/
Dbindings-upstream.rst159 - delays that would be different only under unusual conditions
/Zephyr-Core-3.4.0/doc/kernel/services/timing/
Dtimers.rst56 **minimum** delays that will elapse. Because of internal system timer
Dclocks.rst95 * Kernel :c:struct:`k_timer` objects must specify delays for
/Zephyr-Core-3.4.0/doc/hardware/peripherals/canbus/
Dcontroller.rst59 * Prop_Seg: The signal propagation delay of the bus and other delays of the transceiver and node.
/Zephyr-Core-3.4.0/doc/kernel/services/scheduling/
Dindex.rst240 that delays its processing for a specified time period
/Zephyr-Core-3.4.0/doc/project/
Drelease_process.rst14 maintain the quality of the overall release without delays because of one or two
/Zephyr-Core-3.4.0/kernel/
DKconfig336 This option delays bootup for the specified amount of
/Zephyr-Core-3.4.0/doc/releases/
Drelease-notes-2.3.rst1323 * :github:`19075` - k_delayed_work_submit() does not handle long delays correctly
Drelease-notes-2.4.rst565 * Added optional delays to MCUX DSPI and LPSPI drivers.