Skip to content

Buses: expose I2C client probe failures in diagnostics - #622

Draft
Srikanth Muppandam (smuppand) wants to merge 2 commits into
qualcomm-linux:mainfrom
smuppand:buses-client-diagnostics
Draft

Srikanth Muppandam (smuppand) wants to merge 2 commits into
qualcomm-linux:mainfrom
smuppand:buses-client-diagnostics

Conversation

@smuppand

Copy link
Copy Markdown
Contributor

Buses can report unbound I2C clients while its controller-only kernel scan omits the client probe errors needed for triage.

  • Collect client-specific kernel messages from the existing snapshot using runtime-discovered client addresses, names, drivers, and module candidates.
  • Retain the complete client log and print a bounded excerpt when runtime validation fails.
  • Clarify controller-only health reporting and document DT/overlay configuration for disconnected optional peripherals.

Preserves existing PASS/FAIL/SKIP behavior and does not add kernel captures or hardware operations.

Match runtime client addresses, names, drivers and module candidates against the existing kernel snapshot. Retain matching lines without additional kernel reads or hardware operations. Keep this shared helper independent of result classification.

Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
Use the shared I2C diagnostic helper to retain client messages and replay a bounded excerpt when runtime validation fails. Clarify controller-only health output and document optional peripheral DT configuration without weakening binding checks. This integration depends on the preceding shared-helper commit, revert it before or together with that helper.

Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant