Searched refs:ready (Results 151 – 175 of 186) sorted by relevance
12345678
| /Zephyr-latest/tests/subsys/fs/zms/src/ |
| D | main.c | 87 if (fixture->fs.ready) { in after()
|
| /Zephyr-latest/doc/services/zbus/ |
| D | index.rst | 103 also listens to the ``Trigger`` channel. When the sensor data is ready, the sensor thread publishes
227 get ready to execute right after receiving the notification. However, they go to a pending
230 - The VDED pushes the notification message to the queue of S1. Notice the thread gets ready to
|
| /Zephyr-latest/subsys/bluetooth/common/ |
| D | Kconfig | 241 ready to receive commands.
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-tools.rst | 131 Once the hardware is connected and ready to use, you can then proceed to
|
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 223 it will be ready to be removed in 4.2 at the earliest.
|
| /Zephyr-latest/boards/st/sensortile_box_pro/doc/ |
| D | index.rst | 7 and is a ready-to-use box kit for wireless IoT and wearable sensor platforms to help using
|
| /Zephyr-latest/tests/subsys/fs/nvs/src/ |
| D | main.c | 90 if (fixture->fs.ready) { in after()
|
| /Zephyr-latest/doc/services/smf/ |
| D | index.rst | 478 printk("Error: button device %s is not ready\n",
|
| /Zephyr-latest/doc/services/logging/ |
| D | cs_stm.rst | 57 before infrastructure is ready a dedicated RAM buffer is used to which data is written. When
|
| /Zephyr-latest/doc/kernel/services/ |
| D | interrupts.rst | 139 thread A is swapped out and the next ready thread B starts to
153 ready, the IRQ lock will inhibit any preemption that would otherwise
|
| /Zephyr-latest/samples/subsys/mgmt/updatehub/ |
| D | README.rst | 389 in step 9. With that, the update is published, and the server is ready to
|
| /Zephyr-latest/boards/snps/hsdk4xd/doc/ |
| D | index.rst | 497 When you are ready to deploy the program so that it boots up automatically on
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 274 them ready for the next certification if necessary.
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.6.rst | 245 * ``ZEP-989`` - Cache next ready thread instead of finding out the long way
|
| D | release-notes-3.2.rst | 540 * stm32: Check if clock device is ready before accessing clock control
582 * stm32: Check if clock device is ready before accessing.
747 * Enhanced the BQ274XX driver to support the data ready interrupt trigger.
921 /* device is ready for use */
959 /* device is ready for use */
1798 - :github:`50777` - LE Audio: Receiver start ready command shall only be sent by the receiver
|
| D | release-notes-3.6.rst | 840 ready.
1077 if it has data ready to be read, and always invokes ``TRANSMIT_IDLE`` when the pipe is
|
| D | release-notes-3.3.rst | 734 waits for the flash to become ready before continuing. In cases where a
2650 - :github:`50777` - LE Audio: Receiver start ready command shall only be sent by the receiver
2725 - :github:`53552` - LE Audio: Device executes receiver start ready before the CIS is connected
2739 …aspberry Pi Pico - ssd1306 display attempts to initialize before i2c bus is ready for communication
3304 * :github:`51873` - sensor: bmp388: missing if check around i2c device ready function
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | chromebooks_adsp.rst | 339 Finally, with your new kernel booted, you are ready to run Zephyr
|
| /Zephyr-latest/doc/hardware/pinctrl/ |
| D | index.rst | 433 to it, it is ready to use the API. The most common way to apply a state is by
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu.rst | 260 When the BLOB transfer finishes, the firmware image is ready for distribution. The Initiator may
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 883 As before, inspect and test your changes. When ready, continue the
928 attention needed and it will be ready for merge sooner than later:
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 15 features that are not ready yet.
|
| /Zephyr-latest/boards/native/doc/ |
| D | arch_soc.rst | 134 /* We expect the peripheral done and ready to do something else */
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | test_handlers.py | 645 assert handler.ready == expected_ready
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 104 make the storage ready.
|
12345678
