| /Zephyr-latest/subsys/bluetooth/controller/ll_sw/nordic/hal/nrf5/radio/ |
| D | radio.h | 156 void radio_tmr_ready_save(uint32_t ready);
|
| /Zephyr-latest/doc/services/portability/ |
| D | cmsis_rtos_v2.rst | 71 parameter ef_id is not ready to be used) are not supported.
|
| /Zephyr-latest/samples/boards/96boards/argonkey/sensors/ |
| D | README.rst | 35 printk("%s: device not ready.\n", hum_dev->name);
|
| /Zephyr-latest/boards/particle/nrf52_blenano2/doc/ |
| D | index.rst | 102 .. _Kickstarter: https://www.kickstarter.com/projects/redbearinc/bluetooth-5-ready-ble-module-nano-…
|
| /Zephyr-latest/drivers/usb/device/ |
| D | usb_dc_nrfx.c | 246 bool ready; member
275 .ready = false,
290 return get_usbd_ctx()->ready; in dev_ready()
693 ctx->ready = true; in usbd_work_process_pwr_events()
703 ctx->ready = false; in usbd_work_process_pwr_events()
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | bap.rst | 218 Sink 0x20019110 is ready to sync without encryption
271 Sink 0x20019110 is ready to sync without encryption
282 Sink 0x20019110 is ready to sync with encryption
289 Sink 0x20019110 is ready to sync with encryption
606 to the source the stack is ready to stop receiving data.
|
| /Zephyr-latest/drivers/flash/ |
| D | nrf_qspi_nor.c | 42 volatile bool ready;
363 while (!dev_data->ready) { in qspi_wait_for_completion()
367 dev_data->ready = false; in qspi_wait_for_completion()
378 dev_data->ready = true; in qspi_complete()
|
| /Zephyr-latest/doc/project/ |
| D | code_flow.rst | 16 of new features to be introduced into the main branch when ready. Creating a new
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | features.rst | 42 * Concurrent multi-protocol support ready
|
| /Zephyr-latest/samples/drivers/lora/receive/ |
| D | README.rst | 18 the user must be ready to inspect the console output immediately after
|
| /Zephyr-latest/boards/beagle/beagleconnect_freedom/doc/ |
| D | index.rst | 13 of a board and a case which ships programmed and ready to be used.
|
| /Zephyr-latest/doc/kernel/services/ |
| D | polling.rst | 26 - a kernel FIFO contains data ready to be retrieved
27 - a kernel message queue contains data ready to be retrieved
28 - a kernel pipe contains data ready to be retrieved
|
| /Zephyr-latest/kernel/ |
| D | Kconfig | 304 ready queue implementation, offering different choices between
309 bool "Simple linked-list ready queue"
311 When selected, the scheduler ready queue will be implemented
321 bool "Red/black tree ready queue"
323 When selected, the scheduler ready queue will be implemented
334 bool "Traditional multi-queue ready queue"
337 When selected, the scheduler ready queue will be implemented
463 milliseconds. This is used to allow serial ports to get ready
466 detect the new USB serial bus, enumerate it and get ready to
|
| /Zephyr-latest/subsys/logging/frontends/ |
| D | Kconfig | 65 in the buffer and flushed to the STMESP once the pipeline is ready.
|
| /Zephyr-latest/samples/sensor/fdc2x1x/ |
| D | README.rst | 11 FDC2X1X sensor in polling mode or optionally with data ready trigger. It is able
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 239 …-dormant and carrier-up whenever (and only when) association is complete and connectivity is ready.
301 *Make API immediately ready*
304 Connectivity implementations must be ready to receive API calls immediately after :c:member:`conn_m…
308 …ready for connect commands immediately when :c:member:`conn_mgr_conn_api.init` is called, calls to…
|
| /Zephyr-latest/drivers/serial/ |
| D | uart_emul.c | 250 bool ready = false; in uart_emul_irq_rx_ready() local
258 ready = !ring_buf_is_empty(data->rx_rb); in uart_emul_irq_rx_ready()
261 return ready; in uart_emul_irq_rx_ready()
|
| /Zephyr-latest/drivers/sensor/bosch/bmi160/ |
| D | bmi160.c | 84 .ready = bmi160_bus_ready_spi,
116 .ready = bmi160_bus_ready_i2c,
1056 if (!cfg->bus_io->ready(dev)) { in bmi160_init()
|
| /Zephyr-latest/doc/develop/api/ |
| D | terminology.rst | 48 a consequence of a higher-priority thread being made ready. Whether the
51 the head of the ready queue.
|
| /Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/ |
| D | README.rst | 194 [00:00:00.181,000] <inf> app_device: Device adt7420@48 is ready
195 [00:00:00.181,000] <inf> app_device: Device leds is ready
|
| /Zephyr-latest/doc/build/dts/ |
| D | howtos.rst | 111 /* Not ready, do not use */
121 that the device is ready to be used before passing it to any API functions.
162 successfully, the last thing to check is if the device is ready, like this:
167 printk("Device not ready\n");
170 If you find that the device is not ready, it likely means that the device's
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig.cc1200 | 26 be ready first (and sometime gpio should be the very first as spi
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | coap_client.rst | 57 ``last_block`` is set to true, the response is finished and the client is ready for the next request
|
| D | net_config.rst | 36 the networking to be ready and available. If for example IPv4 address from
|
| /Zephyr-latest/doc/safety/ |
| D | safety_requirements.rst | 64 After doing this, the requirements are ready and a pull request can be created.
|
