Home
last modified time | relevance | path

Searched full:either (Results 1 – 25 of 874) sorted by relevance

12345678910>>...35

/Zephyr-Core-3.7.0/tests/ztest/fail/
DREADME.rst13 - ``ztest_test_fail()`` during either the ``after`` or ``teardown`` phase of the test suite
14 - ``ztest_test_skip()`` during either the ``after`` or ``teardown`` phase of the test suite
15 - ``ztest_test_pass()`` during either the ``after`` or ``teardown`` phase of the test suite
/Zephyr-Core-3.7.0/soc/espressif/esp32s3/
DKconfig.mac21 …When using the default (Espressif-assigned) base MAC address, either setting can be used. When usi…
23 addresses in this range (either 2 or 4 per device.)ll depend on the
24 allocation of MAC addresses in this range (either 1 or 2 per device).
/Zephyr-Core-3.7.0/soc/st/stm32/common/
Dstm32_hsem.h18 * Index of the semaphore used by CPU2 to prevent the CPU1 to either write or
19 * erase data in flash. The CPU1 shall not either write or erase in flash when
20 * this semaphore is taken by the CPU2. When the CPU1 needs to either write or
31 * Index of the semaphore used by CPU1 to prevent the CPU2 to either write or
33 * semaphore to prevent the CPU2 to either write or erase in flash
/Zephyr-Core-3.7.0/soc/espressif/esp32s2/
DKconfig.mac20 When using the default (Espressif-assigned) base MAC address, either setting can be used.
22 allocation of MAC addresses in this range (either 1 or 2 per device).
/Zephyr-Core-3.7.0/soc/espressif/esp32/
DKconfig.mac20 When using the default (Espressif-assigned) base MAC address, either setting can be used.
22 allocation of MAC addresses in this range (either 2 or 4 per device.)
/Zephyr-Core-3.7.0/soc/espressif/esp32c3/
DKconfig.mac21 …When using the default (Espressif-assigned) base MAC address, either setting can be used. When usi…
23 addresses in this range (either 2 or 4 per device.)
/Zephyr-Core-3.7.0/soc/espressif/esp32c6/
DKconfig.mac21 …When using the default (Espressif-assigned) base MAC address, either setting can be used. When usi…
23 addresses in this range (either 2 or 4 per device.)
/Zephyr-Core-3.7.0/doc/kernel/services/data_passing/
Dpipes.rst30 Data is synchronously **sent** either in whole or in part to a pipe by a
32 satisfied, then the operation will either fail immediately or attempt to send
34 completed later. Accepted data is either copied to the pipe's ring buffer
39 will either fail immediately or attempt to receive as many bytes as possible
41 data is either copied from the pipe's ring buffer or directly from the
45 either on the entire pipe or on only its ring buffer. Flushing the entire pipe
/Zephyr-Core-3.7.0/include/zephyr/data/
Dnavigation.h47 * @return -EINVAL if either navigation point is invalid
60 * @return -EINVAL if either navigation point is invalid
/Zephyr-Core-3.7.0/include/zephyr/drivers/uart/
Dserial_test.h23 * concurrent write operations, either by preventing all writers from
51 * concurrent read operations, either by preventing all readers from
71 * concurrent read operations, either by preventing all readers from
/Zephyr-Core-3.7.0/doc/build/kconfig/
Dmenuconfig.rst33 #. Build your application as usual using either ``west`` or ``cmake``:
42 #. To run the terminal-based ``menuconfig`` interface, use either of these
53 To run the graphical ``guiconfig``, use either of these commands:
117 In the ``guiconfig`` interface, either click on the image next to the symbol
172 dependencies, either by pressing :kbd:`?` in ``menuconfig`` or in the
/Zephyr-Core-3.7.0/dts/arm/nordic/
Dnrf91_peripherals.dtsi151 * This i2c node can be either TWIM or TWIS, for the user to pick:
167 * This i2c node can be either TWIM or TWIS, for the user to pick:
183 * This i2c node can be either TWIM or TWIS, for the user to pick:
199 * This i2c node can be either TWIM or TWIS, for the user to pick:
215 * This spi node can be either SPIM or SPIS, for the user to pick:
231 * This spi node can be either SPIM or SPIS, for the user to pick:
247 * This spi node can be either SPIM or SPIS, for the user to pick:
263 * This spi node can be either SPIM or SPIS, for the user to pick:
/Zephyr-Core-3.7.0/drivers/sensor/isl29035/
DKconfig69 configured either for either ambient light or infrared sensing.
/Zephyr-Core-3.7.0/dts/bindings/rtc/
Dzephyr,fake-rtc.yaml5 This binding provides a fake RTC controller for use as either a stub or a mock in Zephyr
/Zephyr-Core-3.7.0/dts/bindings/can/
Dzephyr,fake-can.yaml5 This binding provides a fake CAN controller for use as either a stub or a mock in Zephyr
/Zephyr-Core-3.7.0/dts/bindings/mtd/
Dzephyr,fake-eeprom.yaml5 This binding provides a fake EEPROM for use as either a stub or a mock in Zephyr testing.
/Zephyr-Core-3.7.0/samples/sensor/bme280/
DKconfig14 # the device connected either way. These defaults can be overridden if
/Zephyr-Core-3.7.0/include/zephyr/sys/
Dring_buffer.h268 * concurrent write operations, either by preventing all writers from
296 * concurrent write operations, either by preventing all writers from
318 * concurrent write operations, either by preventing all writers from
342 * concurrent read operations, either by preventing all readers from
370 * concurrent read operations, either by preventing all readers from
392 * concurrent read operations, either by preventing all readers from
414 * concurrent read operations, either by preventing all readers from
423 * multiple times. To remove data, use either @ref ring_buf_get or
444 * concurrent write operations, either by preventing all writers from
468 * concurrent read operations, either by preventing all readers from
/Zephyr-Core-3.7.0/include/zephyr/drivers/timer/
Dnrf_grtc_timer.h108 * @retval -EPERM if either channel is unavailable or SYSCOUNTER is not running.
123 * @retval -EPERM if either channel is unavailable or SYSCOUNTER is not running.
160 * @retval -EPERM if either channel is unavailable or SYSCOUNTER is not running.
174 * @retval -EPERM if either channel is unavailable or SYSCOUNTER is not running.
/Zephyr-Core-3.7.0/soc/openisa/rv32m1/
DKconfig.soc9 option should not be used to target either Arm core.
/Zephyr-Core-3.7.0/doc/develop/west/
Dwest-not-found.rst15 The west APIs are not documented since either west was missing or the zephyr
/Zephyr-Core-3.7.0/samples/subsys/llext/modules/
DKconfig13 hello_world_ext.c, either as an llext module or as a built-in part of
/Zephyr-Core-3.7.0/tests/bsim/bluetooth/ll/edtt/
DREADME.txt22 for regression, either as part of a CI system, or in workstation during
48 To run the tests you can either run one of the provided scripts, or run by
/Zephyr-Core-3.7.0/include/zephyr/logging/
Dlog_backend_net.h21 * called either before or after the backend has been initialized. If it gets called when
35 * called either before or after the backend has been initialized. If it gets called when
/Zephyr-Core-3.7.0/doc/contribute/
Dproposals_and_rfcs.rst50 either disagreement or not enough voiced opinions in order to proceed. Make sure
51 to either label it appropriately or include it in the corresponding GitHub

12345678910>>...35