Repository navigation
Buses: fail driver errors and report optional camera skips - #622
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
buses-client-diagnostics
branch
from
October 17, 2026 17:18
905fcbe to
2e578ff
Compare
Srikanth Muppandam (smuppand)
changed the title
Srikanth Muppandam (smuppand)
force-pushed
the
buses-client-diagnostics
branch
from
October 17, 2026 17:33
2e578ff to
5dff7f4
Compare
Srikanth Muppandam (smuppand)
changed the title
Preserve the default inventory API and add opt-in controller, adapter, client and mux correlation for GENI, QUP and CCI. Classify optional camera readiness separately while retaining explicit runtime driver errors from the existing kernel snapshot. Fail EEPROM I/O errors and short reads. Add bounded read-only shell discovery, probe, consistency-matrix and natural runtime-idle checks without package installation or hardware policy changes. Metadata-only discovery does not depend on transfer tools. Keep destructive integrity validation in the existing Python helper. Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
Use the shared I2C topology and EEPROM helpers with image-provided tools. Preserve safe automatic defaults and expose explicit matrix and runtime-idle modes through the existing EEPROM options. Initialize results before argument validation and keep final kernel checks after adapter-selection skips. Fail captured controller and client errors independently of optional camera readiness or strict-mode settings. Retain actionable stdout and file diagnostics. Depends on the preceding shared-helper commit. Revert this integration before or together with that helper. Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
Srikanth Muppandam (smuppand)
force-pushed
the
buses-client-diagnostics
branch
from
October 18, 2026 10:35
5dff7f4 to
7a1a98b
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
1 participant
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.
Buses could pass despite firmware-load and camera probe errors in the captured kernel log. Unbound optional cameras also need separate readiness reporting from required controllers and clients.
I2C_DMESG_STRICT=0, optional-camera SKIP, or later successful binding. Normal initialization and dummy-regulator notices alone do not fail.