Home
last modified time | relevance | path

Searched full:finishing (Results 1 – 7 of 7) sorted by relevance

/Zephyr-Core-3.5.0/dts/bindings/bluetooth/
Dzephyr,bt-hci-spi.yaml33 transaction after finishing the header transaction. Without this delay the host
/Zephyr-Core-3.5.0/dts/bindings/gpio/
Darduino-header-r3.yaml20 towards the top, skipping two pins, then finishing with D14 and
/Zephyr-Core-3.5.0/tests/kernel/stack/stack/src/
Dtest_stack_fail.c67 /* Delay for finishing some actions of the new thread */ in ZTEST()
/Zephyr-Core-3.5.0/include/zephyr/zbus/
Dzbus.h468 * reading, notifying or claiming again. Finishing is the only available action.
509 * has no changes. Note this function could be useful after claiming/finishing actions.
/Zephyr-Core-3.5.0/doc/services/zbus/
Dindex.rst59 channels. Publishing, reading, claiming, and finishing are available in all RTOS thread contexts.
696 safely. When a channel is claimed, no actions are available to that channel. After finishing the
/Zephyr-Core-3.5.0/tests/bsim/bluetooth/mesh/src/
Dtest_advertiser.c531 * finishing advertising the message. in test_tx_proxy_mixin()
/Zephyr-Core-3.5.0/drivers/i3c/
Di3c_mcux.c1540 /* Finishing the IBI transaction */ in mcux_i3c_ibi_work()