samples: subsys: usb: uvc: allow a virtual video source to be used #87869
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduce a new USB Video Class (UVC) implementation from scratch. It exposes a native Zephyr Video driver interface, allowing to call the video_enqueue()/video_dequeue() interface. It will query the attached video device to learn about the pipeline capabilities, and use this to configure the USB descriptors. At runtime, this UVC implementation will send this device all the control requests, which it can then dispatch to the rest of the pipeline. The application can poll the format currently selected by the host, but will not be alerted when the host configures a new format, as there is no video.h API for it yet. Signed-off-by: Josuah Demangeon <[email protected]>
The Arduino Nicla Vision board supports the new device_next USB stack and can be used for testing USB Device features such as UVC. Signed-off-by: Josuah Demangeon <[email protected]>
Following the addition of USB Video Class, this adds a sample that makes use of the &zephyr,camera chosen node of any board to stream the video source to the host. A fallback video-emul.overlay is provided for test and debugging purpose for devices without a camera. Signed-off-by: Josuah Demangeon <[email protected]>
Following the addition of USB Video Class, this adds a sample that makes use of the &zephyr,camera chosen node of any board to stream the video source to the host. A fallback video-emul.overlay is provided for test and debugging purpose for devices without a camera. Signed-off-by: Josuah Demangeon <[email protected]>
This introduces a method for testing hardware that lacks a camera with the UVC sample. Software is used to fill video buffers, as if it was a real camera providing the frames. Signed-off-by: Josuah Demangeon <[email protected]>
github-actions
bot
added
area: Devicetree
area: Samples
github-actions
bot
requested review from
decsny,
facchinm,
galak,
jfischer-no,
kartben,
nashif,
pillo79 and
rruuaanng
Contributor
Author
|
Now part of #76798 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a split-off from this PR, which is a dependency:
This does two contradictory things:
VIDEO_SW_GENERATORto be used as virtual video source.zephyr,video-emul-*to be used as virtual video source.They can still work both at the same time:
zephyr,video-emul-*selected aszephyr,camera, thenVIDEO_SW_GENERATORdisables itself.zephyr,camera, thenVIDEO_SW_GENERATORdisables itself.VIDEO_SW_GENERATORremains enabled.This PR will be modified as discussion goes so that a single virtual video source can be used. The challenge:
zephyr,video-emul-*is very basic, for CI purpose mostly.VIDEO_SW_GENERATORlacks a devicetree node, it is a Kconfig only device.Another possibility is introduced by #82158 (comment) which permits all cameras of a system to be listed and used by samples.