-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Video RTIO demo #92566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Video RTIO demo #92566
Conversation
Signed-off-by: Josuah Demangeon <[email protected]>
|
For anyone investigating RTIO, the implementation of the engine is actually nimble! Other useful resources:
And the ongoing discussionso with RTIO developers (for grasping the RTIO model), and Zephyr/Linux develoeprs (for grasping the V4L2 model) through this year! |
|
|
Thank you for the this implementation. I tried to quickly implement the necessary stuffs to generalize this into the framework in #92370. It is faster to illustrate the idea, hope you don't mind. |
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
|
This is superseded by #92370 so can be closed. |




In some area, RTIO is used to increase performance at a slight extra cost in code size.
For video, it seems like a partial RTIO-like flow was already adopted by @loicpoulain in video APIs out of kernel primitives (the same week RTIO was introduced), so switching to RTIO actually reduces the amount of code in drivers and simplify the video APIs.
API functions removed as now available through RTIO APIs:
.enqueue.dequeue.flush.set_signal(the polling API)API function added:
.iodev_submitThe sample
main.cdid not go down in size. This initial PR adds a naive implementation that exposes all the RTIO internals directly, allowing discussion with the RTIO developers and Video developers and users about what wrappers to implement.Keeping the low-level exposed is also a good opportunity to allow application libraries to wrap video APIs in higher-level and efficient userspace APIs.