drivers: video: stm32_dcmipp: move video/ header directory to drivers/ #92784
+1
−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
During zephyrproject-rtos#89407 a driver-specific header stm32_dcmipp.h got introduced to support new functionnalities not yet covered by video APIs. Move this header into a new <include/zephyr/drivers/video/> include direcctory like what other driver classes do. Signed-off-by: Josuah Demangeon <me@josuah.net>
github-actions
bot
requested review from
djiatsaf-st,
erwango,
etienne-lms,
FRASTM,
gautierg-st,
GeorgeCGV,
loicpoulain,
marwaiehm-st,
mathieuchopstm and
ngphibang
|
ngphibang
approved these changes
Jul 7, 2025
mathieuchopstm
approved these changes
Jul 8, 2025
avolmat-st
approved these changes
Jul 8, 2025
|
Thanks @josuah ! |
erwango
approved these changes
Jul 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Moving a header added by mistake on the wrong place... I missed it during #89407 review!
No Zephyr code relies on it currently, it is only there in the meantime that APIs get designed for hardware ISP features.
This was introduced recently so an avoid a breaking change in 4.3 if merged in 4.2. otherwise generic API for it can land in 4.3
<zephyr/drivers/video.h>.