Searched full:subsequent (Results 1 – 25 of 146) sorted by relevance
123456
| /Zephyr-Core-3.5.0/boards/arm/cc3220sf_launchxl/ |
| D | dbghdr.c | 11 * Also, on subsequent reboots, the bootloader skips the integrity
|
| /Zephyr-Core-3.5.0/boards/arm/cc3235sf_launchxl/ |
| D | dbghdr.c | 11 * Also, on subsequent reboots, the bootloader skips the integrity
|
| /Zephyr-Core-3.5.0/tests/bsim/bluetooth/mesh/tests_scripts/friendship/ |
| D | lpn_disable.sh | 12 # by a subsequent lpn enable call, since the enable call is associated with
|
| /Zephyr-Core-3.5.0/doc/develop/sca/ |
| D | sparse.rst | 10 spaces in C code with subsequent verification that pointers to different
|
| /Zephyr-Core-3.5.0/samples/bluetooth/direct_adv/ |
| D | README.rst | 10 to the peripheral, casual advertising will be performed. Once bonded, on every subsequent
|
| /Zephyr-Core-3.5.0/tests/drivers/sdhc/ |
| D | README.txt | 10 the reset left the SDHC in a bad state subsequent tests may fail.
|
| /Zephyr-Core-3.5.0/subsys/net/lib/tls_credentials/ |
| D | Kconfig | 50 to use during subsequent TLS/SSL negotiations.
|
| /Zephyr-Core-3.5.0/subsys/net/lib/lwm2m/ |
| D | README_lwm2m | 29 …itting the unpatched changes, then committing the desired patches in a subsequent commit, then cre…
|
| /Zephyr-Core-3.5.0/samples/boards/nrf/system_off/src/ |
| D | retained.h | 51 * subsequent boots can verify the retained state.
|
| /Zephyr-Core-3.5.0/samples/bluetooth/peripheral_accept_list/ |
| D | README.rst | 11 Once a device is bonded, on subsequent boots, connection requests will only be
|
| /Zephyr-Core-3.5.0/samples/bluetooth/ |
| D | bluetooth.rst | 28 old after many test iterations. If this happens, subsequent host-device
|
| /Zephyr-Core-3.5.0/dts/bindings/dac/ |
| D | espressif,esp32-dac.yaml | 21 dts, or in subsequent overlay file.
|
| /Zephyr-Core-3.5.0/arch/x86/core/ |
| D | common.S | 21 * subsequent code must, of course, be sure to preserve it meanwhile.
|
| /Zephyr-Core-3.5.0/drivers/adc/ |
| D | adc_ads7052.c | 196 * after the first SCLK falling edge. Subsequent output bits are launched on the subsequent rising
198 * subsequent SCLK rising edges. The device enters the ACQ state after 18 clocks and a minimum time
|
| /Zephyr-Core-3.5.0/tests/arch/arc/arc_dsp_sharing/src/ |
| D | dsp_regs_arc.h | 23 * It is expected that a subsequent call to _store_all_dsp_registers()
|
| /Zephyr-Core-3.5.0/include/zephyr/sys/ |
| D | barrier.h | 67 * This routine is used to guarantee that any subsequent instructions are
|
| /Zephyr-Core-3.5.0/tests/posix/eventfd/src/ |
| D | nonblocking.c | 28 zassert_true(ret == -1, "read subsequent ret %d val %d", ret, val); in ZTEST_F()
|
| D | _main.c | 58 /* eventfd shall block on subsequent reads */ in eventfd_poll_unset_common()
|
| /Zephyr-Core-3.5.0/subsys/net/ip/ |
| D | Kconfig.debug | 41 reset the pkt cursor when it's freed, so any subsequent r/w operations
|
| /Zephyr-Core-3.5.0/include/zephyr/xen/public/ |
| D | event_channel.h | 104 * The usual pattern of use, in the guest's upcall (or subsequent
105 * handler) is as follows: (Re-enable the event channel for subsequent
|
| /Zephyr-Core-3.5.0/tests/kernel/fpu_sharing/generic/src/ |
| D | float_regs_arm_gcc.h | 52 * It is expected that a subsequent call to _store_all_float_registers()
|
| D | float_regs_arc_gcc.h | 27 * It is expected that a subsequent call to _store_all_float_registers()
|
| /Zephyr-Core-3.5.0/include/zephyr/net/ |
| D | ieee802154_mgmt.h | 108 /** Sets AckTx for all subsequent MLME-DATA (aka TX) requests. */
113 /** Unsets AckTx for all subsequent MLME-DATA requests. */
|
| /Zephyr-Core-3.5.0/tests/kernel/mem_heap/k_heap_api/src/ |
| D | test_kheap_api.c | 204 * Allocate first to make sure subsequent allocations in ZTEST()
241 * Allocate first to make sure subsequent allocations in ZTEST()
|
| /Zephyr-Core-3.5.0/tests/subsys/settings/file/src/ |
| D | settings_test_compress_file.c | 81 /* check subsequent compression */ in ZTEST()
|
123456
