Searched refs:ready (Results 126 – 150 of 186) sorted by relevance
12345678
298 After ICBMsg initialization, you are ready for the endpoint binding procedure.319 * To make sure that two sides are ready to exchange messages over that endpoint.
1074 elif self.instance.run and self.instance.handler.ready:1532 if instance.handler.ready and instance.run:1616 if handler.ready:1693 if instance.handler.ready:
93 self.ready = False407 self.ready = True
33 actively polling them, but rather pending for one or more to become ready.294 * ``ZEP-1395`` - Add data ready trigger to FXOS8700 driver295 * ``ZEP-1401`` - Enhance ready queue cache and interrupt exit code to reduce interrupt latency.
49 * Bluetooth Qualification-ready BLE Controller143 * BLE controller qualification-ready, with all required tests passing
154 data instead of waiting for BT connection to be ready. This is helpful on
256 discovered and ready to use. Each characteristic may hold information
99 You're now ready to build applications targeting this board, for example:
6 The DesignWare(R) ARC(R) HS Development Kit is a ready-to-use platform for501 When you are ready to deploy the program so that it boots up automatically on
152 Your workspace is now almost ready to use; you just need to run ``west update``
1788 void radio_tmr_ready_save(uint32_t ready) in radio_tmr_ready_save() argument1790 radio_tmr_ready = ready; in radio_tmr_ready_save()
2014 bool ready = data->int_driven->tx_irq_enabled && in uarte_nrfx_irq_tx_ready_complete() local2017 if (ready) { in uarte_nrfx_irq_tx_ready_complete()2021 return ready ? data->int_driven->tx_buff_size : 0; in uarte_nrfx_irq_tx_ready_complete()
500 assert testinstance.handler.ready == expected_handler_ready
78 * ``Interrupt mode``: data ready, threshold interrupt etc.
200 * the driver can verify that its parent device (RTC) is ready.
103 A system thread that runs when there are no other threads ready to run.
188 The ``smp_svr`` app is ready to run. Just reset your board and test the app
218 * the driver can verify that its parent device (RTC) is ready.
165 the mempool. When the read is ready, instead of getting the buffers directly
129 It calls ``wait_for_promt`` method, to not start scenario until DUT is ready. The shell fixture
213 recovery mode. We'll use the :zephyr:code-sample:`smp-svr` sample since it's ready to be
145 to be **ready**, and is eligible to be selected as the current thread.246 or equal priority, becomes ready.
312 We have two ready-to-build samples demonstrating use of the Zephyr CAN API:
64 # will be ready for use in other CMake list files that run
281 When you are ready to deploy the program so that it boots up automatically
