WORKAROUND: drm/msm/dp: Dump only active pixel stream blocks in snapshot

[YongxingMou]

Each DP stream has its own pixel clock, but the snapshot code unconditionally dumps all pixel stream register blocks.

In SST mode only stream 0 is active, while the remaining pixel stream blocks may be present in the address space but left unclocked. Accessing those registers during snapshot collection can result in unclocked NoC accesses.

Add a helper to query per-stream pixel clock status and dump pixel stream blocks only when the corresponding stream clock is enabled.

This avoids accessing inactive pixel stream registers while still collecting snapshot data for active streams.

[qlijarvis]

🔨 Build Failure Analysis — PR #1667

PR: #1667
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31465027483

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict (content)	Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml	No	Pre-existing conflict during automerge with topic/tech/mm/drm branch; file not touched by PR
2	Merge conflict (content)	drivers/gpu/drm/bridge/Kconfig	No	Pre-existing conflict during automerge with topic/tech/mm/drm branch; file not touched by PR
3	Merge conflict (add/add)	drivers/gpu/drm/bridge/lontium-lt9611c.c	No	Pre-existing conflict during automerge with topic/tech/mm/drm branch; file not touched by PR
4	Merge conflict (content)	sound/soc/qcom/sc8280xp.c	No	Pre-existing conflict during automerge with topic/tech/mm/drm branch; file not touched by PR

Verdict

0 of 4 errors are introduced by this PR; all 4 are pre-existing merge conflicts in the integration workflow.

The build never reached compilation. The failure occurred during the automerge step when integrating topic branches. PR #1667 only modifies drivers/gpu/drm/msm/dp/ files, none of which conflict. The PR changes themselves are syntactically valid.

📎 Detailed analysis: Full report

[qlijarvis]

🔨 Build Failure Analysis — PR #1667

PR: #1667
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31465027483

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict (content)	Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml	No	Pre-existing conflict in topic branch integration, unrelated to PR changes
2	Merge conflict (content)	drivers/gpu/drm/bridge/Kconfig	No	Pre-existing conflict in topic branch integration, unrelated to PR changes
3	Merge conflict (add/add)	drivers/gpu/drm/bridge/lontium-lt9611c.c	No	Pre-existing conflict in topic branch integration, unrelated to PR changes
4	Merge conflict (content)	sound/soc/qcom/sc8280xp.c	No	Pre-existing conflict in topic branch integration, unrelated to PR changes

Verdict

0 of 4 errors are introduced by this PR; all 4 are pre-existing merge conflicts in the topic branch.

The build failed during the automerge phase (topic branch integration) before compilation began. The PR modifies only drivers/gpu/drm/msm/dp/ files, while all conflicts occur in completely unrelated files. This is a topic branch integration issue, not a PR code quality issue.

📎 Detailed analysis: Full report

[qlijarvis]

PR #1667 — validate-patch

PR: #1667

Verdict	Issues	Detailed Report
✅	0	Full report

Final Summary

1. Lore link present: No — WORKAROUND: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only workaround, not posted upstream
4. PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1667 - WORKAROUND: drm/msm/dp: Dump only active pixel stream blocks in snapshot
Upstream commit: N/A (vendor-only workaround)
Verdict: ✅ PASS

Commit Message

Check	Status	Note
Subject matches upstream	N/A	Vendor-only workaround; no upstream source
Body preserves rationale	✅	Clear problem description and solution rationale
Fixes tag present/correct	N/A	No Fixes tag; workaround for unclocked NoC access issue
Authorship preserved	✅	Proper author and Signed-off-by chain
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
drivers/gpu/drm/msm/dp/dp_ctrl.c	✅	Adds helper msm_dp_ctrl_stream_clk_on() to query stream clock status
drivers/gpu/drm/msm/dp/dp_ctrl.h	✅	Adds function declaration
drivers/gpu/drm/msm/dp/dp_display.c	✅	Updates snapshot logic to check clock status before dumping registers

Verdict

Merge as-is. This is a well-documented vendor-only workaround that prevents unclocked NoC accesses when dumping DP pixel stream registers in SST mode. The implementation is clean and the commit message clearly explains the problem and solution.

Final Summary

1. Lore link present: No — WORKAROUND: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only workaround, not posted upstream
4. PR present in qcom-next/topics: Partial — subject or partial tree evidence found in qcom-next, but full change was not verified (per integration_presence_report.md)

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: 8d5dbc1b17adf8fe86a41adcda686785e73f5414
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] WORKAROUND: drm/msm/dp: Dump only active pixel stream blocks	partial - subject or partial tree evidence found, but full change was not verified	missing - no subject, patch-id, or full tree-content match found	partial

Final Status

overall_status: PARTIAL
present_commits: 0/1
partial_commits: 1/1
missing_commits: 0/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

[qlijarvis]

PR #1667 — checker-log-analyzer

PR: #1667
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31465027592

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	Automerge conflict - cannot run
dt-binding-check	❌	Automerge conflict - cannot run
dtb-check	❌	Automerge conflict - cannot run
sparse-check	❌	Automerge conflict - cannot run
check-uapi-headers	❌	Automerge conflict - cannot run
check-patch-compliance	❌	Automerge conflict - cannot run
tag-check	✅	PASS - WORKAROUND: prefix present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1667 - WORKAROUND: drm/msm/dp: Dump only active pixel stream blocks in snapshot
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/31465027592
Target branch: tech/mm/drm

Checker	Result	Summary
checkpatch	❌	Automerge conflict - cannot run
dt-binding-check	❌	Automerge conflict - cannot run
dtb-check	❌	Automerge conflict - cannot run
sparse-check	❌	Automerge conflict - cannot run
check-uapi-headers	❌	Automerge conflict - cannot run
check-patch-compliance	❌	Automerge conflict - cannot run
tag-check	✅	PASS - WORKAROUND: prefix present

---

❌ All Checkers — Automerge Failure

Root cause: The PR cannot be merged cleanly into the tech/mm/drm baseline due to merge conflicts in 4 files unrelated to this PR's changes.

Failure details:

CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml
CONFLICT (content): Merge conflict in drivers/gpu/drm/bridge/Kconfig
CONFLICT (add/add): Merge conflict in drivers/gpu/drm/bridge/lontium-lt9611c.c
CONFLICT (content): Merge conflict in sound/soc/qcom/sc8280xp.c

Analysis:

This PR modifies only 3 files:

• drivers/gpu/drm/msm/dp/dp_ctrl.c
• drivers/gpu/drm/msm/dp/dp_ctrl.h
• drivers/gpu/drm/msm/dp/dp_display.c

However, the automerge step (which merges all topic branches in tech/mm/drm together) encountered conflicts in completely different files:

• Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml (DT binding)
• drivers/gpu/drm/bridge/Kconfig (bridge driver config)
• drivers/gpu/drm/bridge/lontium-lt9611c.c (lt9611c bridge driver)
• sound/soc/qcom/sc8280xp.c (audio driver)

These conflicts are not caused by this PR. They are pre-existing integration conflicts between other topic branches in the tech/mm/drm tree.

Fix:

This PR cannot proceed through CI until the baseline integration conflicts are resolved. Two options:

1. Rebase the tech/mm/drm branch to resolve the conflicts in:

   • lontium,lt9611.yaml
   • drivers/gpu/drm/bridge/Kconfig
   • drivers/gpu/drm/bridge/lontium-lt9611c.c
   • sound/soc/qcom/sc8280xp.c

2. Merge this PR into a different baseline that does not have these conflicts (e.g., qcom-next or a clean topic branch).

Reproduce locally:

git clone https://github.com/qualcomm-linux/kernel-topics.git
cd kernel-topics
git fetch origin tech/mm/drm
git checkout tech/mm/drm
git fetch origin pull/1667/head:pr-1667
git merge pr-1667 --no-commit
# Conflicts will appear in the 4 files listed above

---

✅ tag-check — PASS

Analysis:

The commit subject is:

WORKAROUND: drm/msm/dp: Dump only active pixel stream blocks in snapshot

The WORKAROUND: prefix is present and valid. This prefix is appropriate for temporary fixes not suitable for upstream submission.

Since the target branch is tech/mm/drm (not qcom-next or qcom-next-staging), the subject-prefix check is mandatory, and this commit passes the requirement.

---

Verdict

Cannot merge — The PR itself is correctly formatted with a valid WORKAROUND: prefix, but CI cannot complete due to pre-existing integration conflicts in the tech/mm/drm baseline that are unrelated to this PR's changes.

Action required: Resolve the 4 merge conflicts in the tech/mm/drm branch baseline (lontium DT binding, bridge Kconfig, lt9611c driver, and sc8280xp audio driver) before this PR can be validated by CI.

Note: The PR changes themselves (dp_ctrl.c, dp_ctrl.h, dp_display.c) do not conflict and appear to be clean. Once the baseline conflicts are resolved, this PR should pass all checkers.