Lines Matching full:rtio
9 #include <zephyr/rtio/rtio.h>
10 #include <zephyr/drivers/i2c/rtio.h>
35 * The user defines an RTIO context to which actions like writes and reads will be
45 * The user defines an RTIO IODEV which wraps the device which will perform the
46 * actions submitted to the RTIO context. In this sample, we are using an I2C
47 * controller device, so we use the I2C specific helper to define the RTIO IODEV.
52 * For async write read operation we will be waiting for a callback from RTIO.
58 * We register a simple I2C target which we will be targeting using RTIO. We
191 /* This is functionally identical to sample_standard_write_read() but uses RTIO */
250 * Since the RTIO SQEs are executed in the background, we need to in sample_rtio_write_read()
266 static void rtio_write_read_done_callback(struct rtio *r, const struct rtio_sqe *sqe, void *arg0) in rtio_write_read_done_callback()
286 * Aside from the blocking wait for the sample_write_read_sem, async RTIO
342 * We wait for the callback which signals RTIO transfer has completed. in sample_rtio_write_read_async()
345 * is entirely safe given RTIO is designed to work from ISR context. in sample_rtio_write_read_async()