Add eDP display overlays for hamoa and purwa IoT EVKs

[anan-tiwa]

Both Hamoa and Purwa IoT EVKs are available in headed and headless
variants. The headed variants use an eDP display panel connected via
the DP3 controller, while the headless variants do not include a
display.

The existing DT is causing the eDP-panel driver to probe an unavailable
panel, resulting in AUX probe timeouts and missing display modes.
Userspace then attempts display commits through the eDP connector,
causing repeated DPU vblank, frame-done, and IRQ timeout errors.

Move the eDP-specific nodes out of the base DTS files into separate
DTBO overlays for each board. This allows the base DTBs to be used
as-is for headless variants, while the composite DTBs enable eDP
support on headed variants.

CRs-Fixed: 4543794, 4543797

[qswat-orbit-external]

Merge Check Failed: No Change Task Found

No associated change tasks found for CR 4543794 on any of the following entities:

Entities:

• kernel.qli.2.0

CR: 4543794

Please ensure the CR has a change task associated with at least one of the entities for this branch.

[qswat-orbit-external]

Merge Check Failed: CR Not Eligible for Merge

CR 4543794 is not eligible for merge.

The parent software image for kernel.qli.2.0 is not development complete.

Entity: kernel.qli.2.0
CR: 4543794
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

[qlijarvis]

PR #977 — validate-patch

PR: #977

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

1. Lore link present: Yes — both commits have valid lore.kernel.org links in Link: trailers
2. Lore link matches PR commits: Yes — diff content is faithful to lore; context differences are legitimate adaptations due to target tree differences; commit message has minor wording variations
3. Upstream patch status: ⏳ Decision Pending — posted 2026-08-18 (v2), no maintainer response yet, still under review
4. PR present in qcom-next/topics: Fail - 2/2 commit(s) are missing from both qcom-next and topics

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #977 - Add eDP display overlays for hamoa and purwa IoT EVKs
Upstream commits:

• Commit 1/2: https://lore.kernel.org/all/20260818-edp_overlay_for-next-v2-1-bd811d378fb7@oss.qualcomm.com/
• Commit 2/2: https://lore.kernel.org/all/20260818-edp_overlay_for-next-v2-2-bd811d378fb7@oss.qualcomm.com/
  Verdict: ⚠️ PARTIAL

Commit Message

Commit 1/2: hamoa-iot-evk

Check	Status	Note
Subject matches upstream	⚠️	PR: "Hamoa IoT EVKs are..." vs lore: "Hamoa IoT EVK variants are..." — minor wording difference
Body preserves rationale	⚠️	PR: "Move the eDP-specific nodes" vs lore: "Move the DP3 and eDP panel specific nodes" — PR omits "DP3" mention
Fixes tag present/correct	✅	N/A — no Fixes tag in either version
Authorship preserved	✅	From: Anand Tiwari <anand.tiwari@oss.qualcomm.com> matches lore author (FROMLIST: submitter may differ, original author's Signed-off-by present)
Backport note (if applicable)	N/A	FROMLIST: prefix — not a backport

Commit 2/2: purwa-iot-evk

Check	Status	Note
Subject matches upstream	⚠️	PR: "Purwa IoT EVKs are..." vs lore: "Purwa IoT EVK variants are..." — minor wording difference
Body preserves rationale	⚠️	PR: "Move the eDP-specific nodes" vs lore: "Move the DP3 and eDP panel specific nodes" — PR omits "DP3" mention
Fixes tag present/correct	✅	N/A — no Fixes tag in either version
Authorship preserved	✅	From: Anand Tiwari <anand.tiwari@oss.qualcomm.com> matches lore author
Backport note (if applicable)	N/A	FROMLIST: prefix — not a backport

Diff

Commit 1/2: hamoa-iot-evk

File	Status	Notes
arch/arm64/boot/dts/qcom/Makefile	✅	Identical changes — adds hamoa-iot-evk-edp overlay build rule
arch/arm64/boot/dts/qcom/hamoa-iot-evk-edp.dtso	✅	New file — content matches lore patch
arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts	⚠️	Context-only delta — deletions identical, but PR context shows wcd938x: audio-codec while lore shows clocks { node; target tree differs from lore base

Commit 2/2: purwa-iot-evk

File	Status	Notes
arch/arm64/boot/dts/qcom/Makefile	✅	Identical changes — adds purwa-iot-evk-edp overlay build rule
arch/arm64/boot/dts/qcom/purwa-iot-evk-edp.dtso	✅	New file — content matches lore patch
arch/arm64/boot/dts/qcom/purwa-iot-evk.dts	⚠️	Context-only delta — deletions identical, target tree context differs from lore base

Upstream Patch Status

Commit	Community Verdict
[PATCH v2 1/2] arm64: dts: qcom: hamoa-iot-evk: Add eDP display overlay	⏳ Decision Pending — posted 2026-08-18, no maintainer response yet (3 days old)
[PATCH v2 2/2] arm64: dts: qcom: purwa-iot-evk: Add eDP display overlay	⏳ Decision Pending — posted 2026-08-18, no maintainer response yet (3 days old)

Analysis: Both patches were posted to linux-arm-msm@vger.kernel.org on August 18, 2026 as v2 of the series. The lore thread contains no replies from maintainers (no Reviewed-by:, Acked-by:, applied, queued, or NAK signals). The patches are very recent (3 days old as of 2026-08-21) and are still under community review.

Issues

1. Commit message wording differences (both commits):

   • PR commit message body differs slightly from lore:
     • PR: "Hamoa IoT EVKs are available..." vs lore: "Hamoa IoT EVK variants are available..."
     • PR: "Move the eDP-specific nodes" vs lore: "Move the DP3 and eDP panel specific nodes"
   • The PR version is slightly less precise — it omits the mention of "DP3" which is explicitly moved in the patch.
   • Impact: Minor — the technical content is preserved, but the lore version is more accurate.

2. Context differences in .dts file deletions (both commits):

   • The PR patch applies to a tree where the context around the deleted backlight node differs from the lore base tree.
   • Lore context: backlight node is followed by clocks { node
   • PR context: backlight node is followed by wcd938x: audio-codec { node
   • Impact: Legitimate adaptation — the actual deletions are identical; only the surrounding context differs due to the target tree having different content (likely the clocks node was removed or moved in the PR target tree).

3. Integration presence:

   • Per integration_presence_report.md, both commits are missing from qcom-next and all topic branches.
   • Impact: These patches have not yet landed in the Qualcomm integration tree, which is expected given they were posted only 3 days ago and have no maintainer acceptance signal yet.

Verdict

Merge with awareness of upstream status. The PR faithfully represents the lore patches with only minor commit message wording differences and legitimate context adaptations. However, the upstream patches are still pending community review (no maintainer response after 3 days). The PR should be merged only if:

1. The team accepts FROMLIST: patches before upstream acceptance (common practice for vendor trees), OR
2. The maintainer provides an acceptance signal on lore (Reviewed-by/Acked-by/applied).

The commit message wording differences are minor and do not affect correctness, but ideally the PR should match the lore version exactly (including "DP3 and eDP panel specific nodes" instead of just "eDP-specific nodes").

Final Summary

1. Lore link present: Yes — both commits have valid lore.kernel.org links in Link: trailers
2. Lore link matches PR commits: Yes — diff content is faithful to lore; context differences are legitimate adaptations due to target tree differences; commit message has minor wording variations
3. Upstream patch status: ⏳ Decision Pending — posted 2026-08-18 (v2), no maintainer response yet, still under review
4. PR present in qcom-next/topics: No — both commits missing from qcom-next and topics (per integration_presence_report.md); expected given recent posting and pending upstream status

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: 3c1e80ceb9fb6978aa94bc0624e7c0003f3b4f6e
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/2	[PATCH 1/2] FROMLIST: arm64: dts: qcom: hamoa-iot-evk: Add eDP	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing
2/2	[PATCH 2/2] FROMLIST: arm64: dts: qcom: purwa-iot-evk: Add eDP	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing

Final Status

overall_status: FAIL
present_commits: 0/2
partial_commits: 0/2
missing_commits: 2/2
topics_checked_for_commits: 2/2
final_summary: PR present in qcom-next/topics: Fail - 2/2 commit(s) are missing from both qcom-next and topics

[qlijarvis]

PR #977 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	Passed
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	Failed (pre-existing tree issues only)
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no C/H changes)
check-patch-compliance	❌	Failed (missing FROMLIST: prefix in git commits)
tag-check	❌	Failed (subject prefix missing)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #977 - Add eDP display overlay for hamoa-iot-evk and purwa-iot-evk
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/32167604473

Checker	Result	Summary
checkpatch	✅	Passed
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	Failed (pre-existing tree issues only)
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no C/H changes)
check-patch-compliance	❌	Failed (missing FROMLIST: prefix in git commits)
tag-check	❌	Failed (subject prefix missing)

---

❌ check-patch-compliance

Root cause: Both commits in the PR are missing the required FROMLIST: prefix in their git commit subject lines.

Failure details:

Checking commit: arm64: dts: qcom: hamoa-iot-evk: Add eDP display overlay
Commit summary does not start with a required prefix

Checking commit: arm64: dts: qcom: purwa-iot-evk: Add eDP display overlay
Commit summary does not start with a required prefix

Analysis: The patch files show FROMLIST: in the subject, but the actual git commits in the PR branch do not have this prefix. The checker validates the git commit history, not the patch file format.

Fix: Amend both commits to add the FROMLIST: prefix:

# For the first commit
git rebase -i HEAD~2
# Mark both commits as 'edit'

# For each commit:
git commit --amend -m "FROMLIST: arm64: dts: qcom: hamoa-iot-evk: Add eDP display overlay"
# (keep the rest of the commit message body unchanged)

git commit --amend -m "FROMLIST: arm64: dts: qcom: purwa-iot-evk: Add eDP display overlay"
# (keep the rest of the commit message body unchanged)

git rebase --continue
git push --force-with-lease

Reproduce locally:

cd kernel
git log --oneline HEAD~2..HEAD
# Verify subjects start with FROMLIST:

---

❌ tag-check

Root cause: Same as check-patch-compliance — both commits lack the required subject prefix.

Failure details:
Both commits are missing a valid prefix tag (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, or WORKAROUND:).

Fix: Same as above — add FROMLIST: prefix to both commit subjects.

---

❌ dtb-check

Root cause: Pre-existing tree issues in hamoa/purwa base DTSIs — NOT introduced by this PR.

Failure details:
The dtb-check log shows errors for nodes that are not touched by this PR:

• etm@* nodes: 'anyOf' conditional failed
• video-codec@aa00000: missing 'iommus' property, unexpected 'iommu-map'
• ctcu@10001000: failed to match any schema with compatible: ['qcom,hamoa-ctcu', 'qcom,sa8775p-ctcu']
• funnel@*, tmc@*, replicator@*: compatible does not contain items matching schema
• phy@1bd4000 (purwa only): missing 'qcom,4ln-config-sel' property

Analysis: This PR adds only eDP display overlay files (hamoa-iot-evk-edp.dtso and purwa-iot-evk-edp.dtso) that reference display-related nodes (&mdss, &mdss_dp3, &mdss_dp3_out, &pmc8380_3_gpios, &pmk8550_pwm, &tlmm). The PR does not modify or reference any of the failing nodes (etm, video-codec, ctcu, funnel, tmc, replicator, phy).

These errors are pre-existing issues in the base hamoa.dtsi and purwa.dtsi files that get exposed when the new DTB variants are built. The dtb-check baseline subtraction should have filtered these out, but they appear in the log because the new DTB files (hamoa-iot-evk-edp.dtb, purwa-iot-evk-edp.dtb) inherit all nodes from the base DTSIs.

Verdict: These dtb-check failures are false positives for this PR. The PR itself is correct and does not introduce any new schema violations.

Fix: None required for this PR. The underlying tree issues should be fixed separately:

• Add missing bindings for qcom,hamoa-ctcu
• Fix CoreSight node compatible strings to match schema requirements
• Add missing iommus property to video-codec nodes
• Add missing qcom,4ln-config-sel to purwa phy node

Reproduce locally:

make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/hamoa-iot-evk-edp.dtb
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/purwa-iot-evk-edp.dtb
# Compare with base DTBs to confirm errors are pre-existing

---

Verdict

2 blockers to fix before merge:

1. check-patch-compliance / tag-check: Add FROMLIST: prefix to both commit subjects in the git history (not just in the patch file format).

2. dtb-check: No action required — all failures are pre-existing tree issues not introduced by this PR.

After fixing the commit subjects, the PR will be ready to merge. The dtb-check failures should be tracked separately as tree-wide cleanup items.

[qlijarvis]

PR #977 — validate-patch

PR: #977

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

1. Lore link present: Not provided in agent output
2. Lore link matches PR commits: Not provided in agent output
3. Upstream patch status: Not provided in agent output
4. PR present in qcom-next/topics: Fail - 2/2 commit(s) are missing from both qcom-next and topics

Verdict: ⚠️ — click to expand

Perfect! I have completed the validate-patch skill workflow following all the mandatory steps. Here's a summary of what was done:

Validation Summary

I validated PR #977 against the upstream lore.kernel.org patches following the complete validate-patch skill workflow:

✅ Steps Completed:

1. ✅ Parsed PR and found lore links for both commits
2. ✅ Fetched upstream lore patches (pre-fetched by Jarvis in lore_evidence/)
3. ✅ Checked upstream patch status (Decision Pending - no maintainer response yet)
4. ✅ Obtained PR diff from pr.patch
5. ✅ Compared commit messages (found minor wording simplifications)
6. ✅ Compared diff content (code changes match exactly; Makefile context differs legitimately)
7. ✅ Verified file paths and symbols (all correct)
8. ✅ Checked qcom-next/topics presence (both commits missing - expected for new FROMLIST)
9. ✅ Produced structured validation report

Key Findings:

• Diff content: ✅ Faithful to upstream (new files, deletions, and Makefile changes match exactly)
• Commit messages: ⚠️ Minor wording simplifications that diverge from upstream text
• Upstream status: ⏳ Under review (posted Aug 18, 2026, no maintainer response yet)
• Integration presence: ❌ Not in qcom-next/topics (expected for new submission)

Verdict: ⚠️ PARTIAL - Code is correct, but commit message wording should ideally match upstream verbatim for FROMLIST commits.

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: 3c1e80ceb9fb6978aa94bc0624e7c0003f3b4f6e
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/2	[PATCH 1/2] FROMLIST: arm64: dts: qcom: hamoa-iot-evk: Add eDP	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing
2/2	[PATCH 2/2] FROMLIST: arm64: dts: qcom: purwa-iot-evk: Add eDP	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing

Final Status

overall_status: FAIL
present_commits: 0/2
partial_commits: 0/2
missing_commits: 2/2
topics_checked_for_commits: 2/2
final_summary: PR present in qcom-next/topics: Fail - 2/2 commit(s) are missing from both qcom-next and topics

[qlijarvis]

PR #977 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	All commits pass style checks
dt-binding-check	⏭️	Skipped - no binding changes
dtb-check	❌	Pre-existing tree issues exposed by new DTB targets
sparse-check	⏭️	Skipped - no C/H file changes
check-uapi-headers	⏭️	Skipped - no UAPI changes
check-patch-compliance	✅	Both commits have valid FROMLIST: prefix and Link tags
tag-check	✅	Both commits have required FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #977 - Add eDP display overlay for hamoa-iot-evk and purwa-iot-evk
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/32212695428
Target branch: qcom-6.18.y

Checker	Result	Summary
checkpatch	✅	All commits pass style checks
dt-binding-check	⏭️	Skipped - no binding changes
dtb-check	❌	Pre-existing tree issues exposed by new DTB targets
sparse-check	⏭️	Skipped - no C/H file changes
check-uapi-headers	⏭️	Skipped - no UAPI changes
check-patch-compliance	✅	Both commits have valid FROMLIST: prefix and Link tags
tag-check	✅	Both commits have required FROMLIST: prefix

---

❌ dtb-check

Root cause: Pre-existing schema validation errors in base SoC DTSI files (hamoa.dtsi, purwa.dtsi) exposed when building new DTB targets hamoa-iot-evk-edp.dtb and purwa-iot-evk-edp.dtb.

Failure details:

The PR adds two new device tree overlay files (hamoa-iot-evk-edp.dtso and purwa-iot-evk-edp.dtso) that enable eDP display support. When these overlays are compiled into DTB files, they expose pre-existing validation errors in the base SoC device tree files that are not introduced by this PR.

Errors observed:

1. ctcu@10001000 binding mismatch (both boards):

   ctcu@10001000 (qcom,hamoa-ctcu): compatible: 'oneOf' conditional failed
   failed to match any schema with compatible: ['qcom,hamoa-ctcu', 'qcom,sa8775p-ctcu']
   

   → The qcom,hamoa-ctcu compatible string has no binding schema.

2. CoreSight components missing binding (both boards):

   funnel@13401000 (arm,coresight-cpu-funnel): compatible: ['arm,coresight-cpu-funnel'] 
     does not contain items matching the given schema
   tmc@13409000 (arm,coresight-cpu-tmc): compatible: ['arm,coresight-cpu-tmc'] 
     does not contain items matching the given schema
   

   → The arm,coresight-cpu-funnel and arm,coresight-cpu-tmc compatible strings are not documented in DT bindings.

3. Video codec IOMMU property issues (both boards):

   video-codec@aa00000: 'iommus' is a required property
   video-codec@aa00000: Unevaluated properties are not allowed ('iommu-map' was unexpected)
   video-codec@aa00000: iommu-map:2: [0, 1] is too short
   

   → The video codec node uses iommu-map instead of the required iommus property, and the iommu-map array has insufficient cells.

Analysis:

These errors are pre-existing tree issues in the base SoC DTSI files (hamoa.dtsi, purwa.dtsi), not introduced by the eDP overlay patches in this PR. The PR only adds display-related nodes (eDP bridge, panel, backlight, regulators) in overlay files. The failing nodes (ctcu, funnel, tmc, video-codec) are defined in the base SoC DTSI and have existed before this PR.

The dtb-check CI compares errors at head_sha (after PR merge) against base_sha (before PR merge). These errors appear in the output because:

• The PR adds new DTB build targets (hamoa-iot-evk-edp.dtb, purwa-iot-evk-edp.dtb)
• These new targets were not built at base_sha, so their errors don't appear in the baseline
• When built at head_sha, they expose pre-existing issues in the included base DTSI files

Fix:

These issues should be fixed in separate patches that address the base SoC DTSI files, not in this PR:

1. For ctcu binding:

   • Add Documentation/devicetree/bindings/soc/qcom/qcom,hamoa-ctcu.yaml covering qcom,hamoa-ctcu and qcom,sa8775p-ctcu

2. For CoreSight components:

   • Add bindings for arm,coresight-cpu-funnel and arm,coresight-cpu-tmc to Documentation/devicetree/bindings/arm/arm,coresight-cpu-debug.yaml or create new binding files

3. For video codec IOMMU:

   • In hamoa.dtsi and purwa.dtsi, replace iommu-map with iommus property in the video-codec@aa00000 node
   • Or update the qcom,iris binding to accept iommu-map and document the required cell count

Reproduce locally:

make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/hamoa-iot-evk-edp.dtb
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/purwa-iot-evk-edp.dtb

---

✅ tag-check

Status: PASS

Both commits in this PR have the required FROMLIST: subject prefix:

• FROMLIST: arm64: dts: qcom: hamoa-iot-evk: Add eDP display overlay
• FROMLIST: arm64: dts: qcom: purwa-iot-evk: Add eDP display overlay

Since the target branch is qcom-6.18.y (not qcom-next or qcom-next-staging), the subject prefix check is mandatory and both commits comply.

---

Verdict

The PR is ready to merge from a patch compliance perspective.

The dtb-check failures are pre-existing tree issues in the base SoC DTSI files, not introduced by this PR. The PR itself:

• ✅ Passes checkpatch (coding style)
• ✅ Passes check-patch-compliance (has FROMLIST: prefix and Link: tags)
• ✅ Passes tag-check (required prefix present)
• ✅ Only adds display overlay files with no C/H/binding changes

Recommendation: Merge this PR as-is. The dtb-check errors should be addressed in separate follow-up patches that fix the base SoC DTSI files (hamoa.dtsi, purwa.dtsi) and add missing bindings for ctcu, CoreSight components, and video codec IOMMU properties.