-
Notifications
You must be signed in to change notification settings - Fork 7.5k
drivers: video: introduce an API for collecting statistics #85811
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
Draft
josuah
wants to merge
2
commits into
zephyrproject-rtos:main
Choose a base branch
from
tinyvision-ai-inc:pr-video-stats
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+161
−1
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
Roadmap:
|
bc382bc
to
e854911
Compare
05fe9a6
to
4483961
Compare
a61cb8f
to
a4b397a
Compare
This was referenced Mar 12, 2025
Introduce an abstraction layer handling the diversity of ways hardware have to report statistics. This allows to take advantage of the various channel average or histograms present on some hardware, that skip the need to manually compute statistics. Fixes zephyrproject-rtos#85457 Signed-off-by: Josuah Demangeon <me@josuah.net>
Add support for the new API video_set_stats() to the emulated video RX driver, and use it to implement simple API tests. The data returned is arbitrary for the sake of testing the API itself. Signed-off-by: Josuah Demangeon <me@josuah.net>
Force-push:
|
Embedded Recipes 2025 will be a good opportunity to ask libcamera folks what high-level model could be applied to the context of Zephyr. I propose holding reviews until May 17th. |
Summary from the libcamera workshop regarding this issue:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: API
Changes to public APIs
area: Samples
Samples
area: Video
Video subsystem
In progress
For PRs: is work in progress and should not be merged yet. For issues: Is being worked on
RFC
Request For Comments: want input from the community
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 an implementation for this RFC:
Downstream:
This is an implementation used on a private repo to implement a basic ISP that does auto-exposure from
main()
.Hardware -> RGB stats -> YRGB stats -> Y channel used for computing how far we are from a "goal" value -> video controls.