Repository navigation
camera: strengthen libcamera and CAMX runtime validation - #609
Draft
Srikanth Muppandam (smuppand) wants to merge 2 commits into
Draft
Srikanth Muppandam (smuppand) wants to merge 2 commits into
Srikanth Muppandam (smuppand) wants to merge 2 commits into
Conversation
Srikanth Muppandam (smuppand)
force-pushed
the
libcamera-camx-validation
branch
from
October 6, 2026 17:37
4701402 to
1979788
Compare
Srikanth Muppandam (smuppand)
force-pushed
the
libcamera-camx-validation
branch
8 times, most recently
from
October 22, 2026 15:45
aafbe5e to
7bf089f
Compare
Add runtime CAMX discovery, NHX checksum fallbacks, read-only RPM checks and bounded camera-service restoration. Provide package mappings, explicit CentOS CLO repository setup and dynamic efivarfs preparation. Support native-HAL executable discovery, bounded capability and capture helpers, exact-test results and fresh image collection while preserving wrapper interfaces. Distinguish EFI read failures from payload mismatches and retain separate before, write and readback diagnostics. Track pending selection by boot ID to prevent repeated writes and verify enabled CamX DT nodes after reboot. Camera runner integration follows separately. Revert its consumers before removing this shared foundation. Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
Use shared helpers for runtime checks and read-only NHX setup with separate YAML and results. Keep base runs image-provided and explicit overlay setup responsible for missing CAMX packages and EFI selection. Reuse complete package sets without repository refresh or installation. Continue on an existing EFI selection, track a pending reboot without repeated writes and report read or post-reboot failures with retained diagnostics. Preserve NHX wrappers and JSON configurations while adding explicit native-HAL testcase, executable, frame, camera and dump-directory selections. Skip native capture without a known testcase and reject mixed native and JSON requests. Require successful execution, matching test results, fresh valid dumps and owned-service restoration. Document native validation limits, unchanged Kodiak streams and repeat-setup behavior. Depends on the preceding shared-helper commit. Revert this consumer integration before its shared foundation. Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
Srikanth Muppandam (smuppand)
force-pushed
the
libcamera-camx-validation
branch
from
October 22, 2026 16:05
7bf089f to
3179015
Compare
This branch has not been deployed
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
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.
Summary
Strengthen libcamera and CAMX validation across supported images while keeping runtime decisions evidence-based and portable.
Changes
Validation
Target status
CentOS currently reports SKIP when the image lacks the required CAMX packages. The available CAMX RPMs are unsigned in the existing repository path, so package provisioning must be corrected in the image/repository flow before target validation can resume.