Lines Matching full:rtio
3 Real Time I/O (RTIO)
14 RTIO provides a framework for doing asynchronous operation chains with event
15 driven I/O. This section covers the RTIO API, queues, executor, iodev,
18 RTIO takes a lot of inspiration from Linux's io_uring in its operations and API
80 The above sequence of operations is embodied in RTIO as chain of
85 and device on the bus it is embodied in what RTIO calls an iodev.
105 The RTIO executor is a low overhead concurrent I/O task scheduler. It ensures
141 the RTIO context that the read was associated with. To create such an RTIO
143 an RTIO context with a dedicated pool of "memory blocks" which can be consumed by
144 the iodev. Below is a snippet setting up the RTIO context with a memory pool.
150 #include <zephyr/rtio/rtio.h>
205 RTIO is useful in cases where concurrent or batch like I/O flows are useful.
211 There is a small cost to each RTIO context and iodev. This cost could be weighed
213 threads per peripheral. RTIO is much lower cost than that.
218 To check if your bus supports RTIO natively, you can check the driver API implementation, if the
219 driver implements the ``iodev_submit`` function of the bus API, then RTIO is supported. If the
220 driver doesn't support the RTIO APIs, it will set the submit function to
223 I2C buses have a default implementation which allows apps to leverage the RTIO work queue while
232 .. doxygengroup:: rtio