[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.

[qlijarvis]

PR #977 — validate-patch

PR: #977

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

1. Lore link present: Yes — https://lore.kernel.org/all/20260818-edp_overlay_for-next-v2-2-bd811d378fb7@oss.qualcomm.com/
2. Lore link matches PR commits: Partial — diff content is identical; commit message has minor wording variations (3 phrases differ slightly but preserve technical meaning)
3. Upstream patch status: In review — posted Aug 18, 2026 as part of v2 series; no maintainer acceptance/rejection signals found in thread
4. PR present in qcom-next/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #977 - FROMLIST: arm64: dts: qcom: purwa-iot-evk: Add eDP display overlay
Upstream commit: https://lore.kernel.org/all/20260818-edp_overlay_for-next-v2-2-bd811d378fb7@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Commit Message

Check	Status	Note
Subject matches upstream	✅	Subject identical (with FROMLIST: prefix added)
Body preserves rationale	⚠️	Minor wording differences in 3 places
Fixes tag present/correct	✅	No Fixes tag in upstream or PR (not a bug fix)
Authorship preserved	✅	From: matches lore author (Anand Tiwari)
Backport note (if applicable)	N/A	FROMLIST: commit, not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/Makefile	✅	Identical changes; context line numbers differ (expected)
arch/arm64/boot/dts/qcom/purwa-iot-evk-edp.dtso	✅	New file content identical to lore patch
arch/arm64/boot/dts/qcom/purwa-iot-evk.dts	✅	Deletions identical to lore patch

Issues

Commit message wording differences:

1. First paragraph: PR says "Purwa IoT EVKs are" vs lore says "Purwa IoT EVK variants are" and "When the panel is absent" vs "When the panel is not connected"

2. Third paragraph: PR says "Move the eDP-specific nodes" vs lore says "Move the DP3 and eDP panel specific nodes" and "enables eDP for boards" vs "enables eDP panel for boards"

3. Fourth paragraph: PR says "so the /delete-property/ of #sound-dai-cells is moved into the base DTS instead of the overlay" vs lore says "so keeping the /delete-property/ of #sound-dai-cells in base DTS"

These are minor semantic variations that preserve the technical meaning but alter the phrasing. The PR commit message is slightly more concise but loses some specificity (e.g., "DP3 and eDP panel specific nodes" → "eDP-specific nodes").

Upstream Patch Status

Commit	Community Verdict
arm64: dts: qcom: purwa-iot-evk: Add eDP display overlay	⏳ Decision Pending — posted Aug 18, 2026; no maintainer decision signals (applied/queued/NAK) found in thread; patch is part of v2 series (2/2)

Dependency Check

• ⚠️ Series dependency: This is patch 2/2 of a series. Patch 1/2 (hamoa-iot-evk eDP overlay) is not included in this PR. The patches are independent (different boards), so no functional dependency exists.
• ✅ No missing header/helper changes

qcom-next Presence

Commit	Status
FROMLIST: arm64: dts: qcom: purwa-iot-evk: Add eDP display overlay	❌ Not in qcom-next — per integration_presence_report.md: "missing - no subject, patch-id, or full tree-content match found" in both qcom-next and topics

Verdict

Merge with minor note: The diff content is faithful to the lore patch. The commit message has minor wording variations that slightly reduce specificity but preserve technical accuracy. The FROMLIST: prefix is correctly applied. The patch is not yet in qcom-next or topics, which is expected for a FROMLIST: commit still under upstream review (posted Aug 18, 2026, no maintainer decision yet).

Recommendation: The wording differences are cosmetic and do not affect correctness. If strict fidelity to upstream wording is required, consider updating the commit message to match lore exactly. Otherwise, the PR is acceptable as-is.

Final Summary

1. Lore link present: Yes — https://lore.kernel.org/all/20260818-edp_overlay_for-next-v2-2-bd811d378fb7@oss.qualcomm.com/
2. Lore link matches PR commits: Partial — diff content is identical; commit message has minor wording variations (3 phrases differ slightly but preserve technical meaning)
3. Upstream patch status: In review — posted Aug 18, 2026 as part of v2 series; no maintainer acceptance/rejection signals found in thread
4. PR present in qcom-next/topics: No — commit is missing from both qcom-next and topics (expected for FROMLIST: under upstream review)

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

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] FROMLIST: arm64: dts: qcom: purwa-iot-evk: Add eDP display	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/1
partial_commits: 0/1
missing_commits: 1/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Fail - 1/1 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/36130944129

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	Pre-existing tree errors only
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	✅	Valid FROMLIST prefix + Link tag
tag-check	✅	Subject prefix present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #977 — FROMLIST: arm64: dts: qcom: purwa-iot-evk: Add eDP display overlay
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/36130944129
Target branch: qcom-6.18.y

Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	Pre-existing tree errors only
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	✅	Valid FROMLIST prefix + Link tag
tag-check	✅	Subject prefix present

---

❌ dtb-check — Pre-existing tree errors (not introduced by this PR)

Root cause: The new DTB file purwa-iot-evk-edp.dtb inherits pre-existing validation errors from the base tree nodes (etm, video-codec, ctcu, coresight components). The PR itself does not modify any of these nodes.

Failure details:

purwa-iot-evk-edp.dtb: soc@0 (simple-bus): etm@13021000: 'anyOf' conditional failed
purwa-iot-evk-edp.dtb: soc@0 (simple-bus): etm@13121000: 'anyOf' conditional failed
purwa-iot-evk-edp.dtb: soc@0 (simple-bus): etm@13221000: 'anyOf' conditional failed
purwa-iot-evk-edp.dtb: soc@0 (simple-bus): etm@13321000: 'anyOf' conditional failed
purwa-iot-evk-edp.dtb: soc@0 (simple-bus): etm@13521000: 'anyOf' conditional failed
purwa-iot-evk-edp.dtb: soc@0 (simple-bus): etm@13621000: 'anyOf' conditional failed
purwa-iot-evk-edp.dtb: soc@0 (simple-bus): etm@13721000: 'anyOf' conditional failed
purwa-iot-evk-edp.dtb: soc@0 (simple-bus): etm@13821000: 'anyOf' conditional failed
purwa-iot-evk-edp.dtb: video-codec@aa00000 (qcom,x1p42100-iris): 'iommus' is a required property
purwa-iot-evk-edp.dtb: video-codec@aa00000 (qcom,x1p42100-iris): Unevaluated properties are not allowed ('iommu-map' was unexpected)
purwa-iot-evk-edp.dtb: video-codec@aa00000 (qcom,x1p42100-iris): iommu-map:2: [0, 1] is too short
purwa-iot-evk-edp.dtb: ctcu@10001000 (qcom,hamoa-ctcu): compatible: 'oneOf' conditional failed
purwa-iot-evk-edp.dtb: /soc@0/ctcu@10001000: failed to match any schema with compatible: ['qcom,hamoa-ctcu', 'qcom,sa8775p-ctcu']
purwa-iot-evk-edp.dtb: funnel@13401000 (arm,coresight-cpu-funnel): compatible: ['arm,coresight-cpu-funnel'] does not contain items matching the given schema
purwa-iot-evk-edp.dtb: tmc@13409000 (arm,coresight-cpu-tmc): compatible: ['arm,coresight-cpu-tmc'] does not contain items matching the given schema
purwa-iot-evk-edp.dtb: replicator@13490000 (arm,coresight-cpu-replicator): compatible: ['arm,coresight-cpu-replicator'] does not contain items matching the given schema
[... and 9 more coresight replicator/funnel/tmc errors ...]

Analysis: These errors are present in the base qcom-6.18.y tree and affect all DTBs that include the purwa SoC base nodes. The PR adds only a new overlay file (purwa-iot-evk-edp.dtso) that enables eDP display — it does not touch etm, video-codec, ctcu, or coresight nodes.

Fix: None required for this PR. These are baseline tree issues that should be fixed separately in the base SoC DTSI files:

• etm@* nodes: Fix binding schema to accept the current compatible strings
• video-codec@aa00000: Add iommus property or update binding to accept iommu-map
• ctcu@10001000: Add binding for qcom,hamoa-ctcu compatible
• funnel@*/tmc@*/replicator@*: Update coresight bindings to accept -cpu- variants

Reproduce locally:

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

---

Verdict

Ready to merge. All checkers passed or skipped appropriately. The dtb-check failure is due to pre-existing tree errors not introduced by this PR. The patch itself is clean:

• ✅ Proper FROMLIST: prefix
• ✅ Valid Link: tag pointing to lore.kernel.org
• ✅ No checkpatch style issues
• ✅ No new DTB validation errors introduced

[Salendarsingh Gaud (sgaud-quic)]

anan-tiwa please rebase the PR on tip

[anan-tiwa]

anan-tiwa please rebase the PR on tip

rebased onto latest

[qlijarvis]

PR #977 — validate-patch

PR: #977

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

1. Lore link present: Yes — https://lore.kernel.org/all/20260818-edp_overlay_for-next-v2-2-bd811d378fb7@oss.qualcomm.com/

2. Lore link matches PR commits: Partial — diff content is faithful to lore but commit message body has been reworded; context differs due to different tree base; line count discrepancy (96 vs 107 deleted lines) suggests possible incomplete removal or different base tree state

3. Upstream patch status: ⏳ Decision Pending — patch posted to linux-arm-msm@vger.kernel.org on 2026-08-18 (v2 series); no merge signals (applied/queued/Reviewed-by/Acked-by) or rejection signals (NAK) found in the fetched thread; patch is recent (posted ~2.5 months ago from current date 2026-11-02) and likely still under review

4. PR present in qcom-next/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #977 - FROMLIST: arm64: dts: qcom: purwa-iot-evk: Add eDP display overlay
Upstream commit: https://lore.kernel.org/all/20260818-edp_overlay_for-next-v2-2-bd811d378fb7@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Commit Message

Check	Status	Note
Subject matches upstream	⚠️	PR: "Add eDP display overlay" vs Lore: "Add eDP display overlay" — subject matches but wording differs slightly in body
Body preserves rationale	⚠️	PR body is reworded: "Purwa IoT EVKs are available" vs lore "Purwa IoT EVK variants are available"; "Move the eDP-specific nodes" vs lore "Move the DP3 and eDP panel specific nodes"; "is moved into" vs lore "keeping the /delete-property/"
Fixes tag present/correct	✅	N/A — no Fixes tag in upstream or PR (not a bug fix)
Authorship preserved	✅	From: matches lore author; FROMLIST: prefix allows submitter to differ
Backport note (if applicable)	N/A	Not a backport — FROMLIST: prefix indicates patch posted to mailing list

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/Makefile	⚠️	Context differs: PR at line 201 (index e5c0e2e00f66d), lore at line 165 (index bb0da34983c8) — content identical but applied to different tree base
arch/arm64/boot/dts/qcom/purwa-iot-evk-edp.dtso	✅	New file — content identical (124 lines, hash 0929fc0358eb)
arch/arm64/boot/dts/qcom/purwa-iot-evk.dts	⚠️	Context differs: PR removes 96 lines starting at index 224ae221b1360, lore removes 107 lines starting at index ad503beec1d3 — deletion content appears identical but line counts differ (96 vs 107)

Issues

1. Commit message body reworded — The PR commit message has been rewritten with slightly different wording compared to the lore patch. Key differences:

   • "Purwa IoT EVKs are available" vs "Purwa IoT EVK variants are available"
   • "Move the eDP-specific nodes" vs "Move the DP3 and eDP panel specific nodes"
   • "is moved into the base DTS instead of the overlay, where it takes effect" vs "keeping the /delete-property/ of #sound-dai-cells in base DTS where it takes effect"

2. Context mismatch in Makefile — The Makefile hunk applies at different line numbers (201 vs 165), indicating the PR is based on a different tree state than the lore patch. The added lines are identical.

3. Line count discrepancy in purwa-iot-evk.dts — PR shows 96 lines deleted, lore shows 107 lines deleted. This suggests the PR may be based on a tree where some of the eDP nodes were already partially removed or the base tree differs.

Verdict

The patch is substantially faithful to the lore upstream with legitimate adaptations for the target tree. The commit message rewording is minor but should ideally preserve the original author's exact wording. The context differences (line numbers, index hashes) are expected when applying to a different tree base. However, the line count discrepancy (96 vs 107 deleted lines) warrants verification that all intended nodes were removed.

Final Summary

1. Lore link present: Yes — https://lore.kernel.org/all/20260818-edp_overlay_for-next-v2-2-bd811d378fb7@oss.qualcomm.com/

2. Lore link matches PR commits: Partial — diff content is faithful to lore but commit message body has been reworded; context differs due to different tree base; line count discrepancy (96 vs 107 deleted lines) suggests possible incomplete removal or different base tree state

3. Upstream patch status: ⏳ Decision Pending — patch posted to linux-arm-msm@vger.kernel.org on 2026-08-18 (v2 series); no merge signals (applied/queued/Reviewed-by/Acked-by) or rejection signals (NAK) found in the fetched thread; patch is recent (posted ~2.5 months ago from current date 2026-11-02) and likely still under review

4. PR present in qcom-next/topics: No — integration_presence_report.md shows FAIL status: commit is missing from both qcom-next (ref 17bbb4b) and all kernel topic branches; no subject, patch-id, or full tree-content match found

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

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] FROMLIST: arm64: dts: qcom: purwa-iot-evk: Add eDP display	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/1
partial_commits: 0/1
missing_commits: 1/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Fail - 1/1 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/41436031333

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	Pre-existing tree issues exposed by new DTB
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no C/H changes)
check-patch-compliance	❌	Content mismatch with upstream link
tag-check	✅	Subject has valid FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #977 - FROMLIST: arm64: dts: qcom: purwa-iot-evk: Add eDP display overlay
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/41436031333
Target branch: qcom-6.18.y

Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	Pre-existing tree issues exposed by new DTB
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no C/H changes)
check-patch-compliance	❌	Content mismatch with upstream link
tag-check	✅	Subject has valid FROMLIST: prefix

---

❌ check-patch-compliance

Root cause: The patch content in the PR differs from the upstream patch at the provided lore.kernel.org link.

Failure details:

Checking commit: FROMLIST: arm64: dts: qcom: purwa-iot-evk: Add eDP display overlay
Change is different from the one mentioned in Link
Link: https://lore.kernel.org/all/20260818-edp_overlay_for-next-v2-2-bd811d378fb7@oss.qualcomm.com/

Analysis:
The checker fetched the upstream patch from lore and found differences in the code changes. This could be due to:

• Context line differences (base tree divergence)
• Additional hunks not in the upstream version
• Missing hunks from the upstream version
• Legitimate adaptations for the vendor tree

Fix:
Fetch the upstream patch and compare:

b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260818-edp_overlay_for-next-v2-2-bd811d378fb7@oss.qualcomm.com/ -o /tmp/upstream
git format-patch -1 40e23cf4406411076f16544dfdc5b9d2a4cef708 --stdout > /tmp/pr.patch
diff <(awk '/^diff/,/^--$/' /tmp/pr.patch | grep -E '^[+-][^+-]') \
     <(awk '/^diff/,/^--$/' /tmp/upstream/*.mbx | grep -E '^[+-][^+-]')

If differences are legitimate adaptations (e.g., Makefile changes for vendor tree structure), document them in the commit message. If differences are unintended, align the patch with upstream.

Reproduce locally:

cd kernel
./scripts/check-patch-compliance.sh --base 5c398266004176fbadb0864af19dd6e6ad3706c6 --head 40e23cf4406411076f16544dfdc5b9d2a4cef708

---

❌ dtb-check

Root cause: Pre-existing devicetree validation errors in the base purwa-iot-evk.dts are exposed when building the new purwa-iot-evk-edp.dtb overlay target.

Failure details:
The new DTB purwa-iot-evk-edp.dtb (base + overlay) triggers 108 validation errors across multiple node types:

CoreSight ETM nodes (8 instances):

soc@0 (simple-bus): etm@13021000: 'anyOf' conditional failed, one must be fixed
soc@0 (simple-bus): etm@13121000: 'anyOf' conditional failed, one must be fixed
[... 6 more etm@ nodes ...]

CoreSight infrastructure (multiple instances):

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
replicator@13490000 (arm,coresight-cpu-replicator): compatible: ['arm,coresight-cpu-replicator'] does not contain items matching the given schema
[... multiple funnel/tmc/replicator nodes ...]

Video codec node:

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

CTCU node:

/soc@0/ctcu@10001000: failed to match any schema with compatible: ['qcom,hamoa-ctcu', 'qcom,sa8775p-ctcu']
ctcu@10001000 (qcom,hamoa-ctcu): compatible: 'oneOf' conditional failed, one must be fixed

Analysis:
None of these failing nodes are introduced by this PR. The overlay (purwa-iot-evk-edp.dtso) only adds:

• backlight node
• vreg_edp_3p3 and vreg_edp_bl regulators
• eDP panel configuration
• Pinctrl states

All failing nodes (etm@, video-codec@, ctcu@, funnel@, tmc@, replicator@) exist in the base purwa-iot-evk.dts file and are pre-existing tree issues. They are exposed now because:

1. This PR creates a new DTB target (purwa-iot-evk-edp.dtb) that didn't exist before
2. The dtb-check baseline comparison cannot filter these out since there's no prior purwa-iot-evk-edp.dtb to compare against
3. The base purwa-iot-evk.dtb may not have been checked recently, or these errors were introduced in earlier commits

These are NOT regressions introduced by this PR.

Fix:
The PR author should not fix these errors as part of this PR. They are unrelated to the eDP overlay functionality. However, the maintainer should be aware that:

1. CoreSight nodes need binding updates or compatible string fixes
2. video-codec@aa00000 needs either:
   • iommus property added, OR
   • Binding updated to accept iommu-map instead of iommus
3. ctcu@10001000 needs a binding for qcom,hamoa-ctcu

These should be fixed in separate patches targeting the base purwa-iot-evk.dts file.

Reproduce locally:

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

---

Verdict

2 blockers to address before merge:

1. check-patch-compliance (BLOCKER): Resolve the content mismatch with the upstream lore patch. Verify differences are intentional adaptations and document them, or align the patch with upstream.

2. dtb-check (NOT A BLOCKER for this PR): The 108 dtb-check errors are pre-existing issues in the base purwa-iot-evk.dts file, not introduced by this PR. The PR correctly implements the eDP overlay functionality. These base tree issues should be fixed in separate follow-up patches, but should not block this PR.

Recommendation: Fix the check-patch-compliance content mismatch, then merge. The dtb-check errors are pre-existing and outside the scope of this PR.

[qcomlnxci]

Test Matrix

Test Case	kbdev-hamoa-iot-evk-multimedia	kbdev-lemans-evk-multimedia	kbdev-monaco-evk-multimedia	kbdev-purwa-iot-evk-multimedia	kbdev-qcs615-ride-multimedia	kbdev-qcs6490-rb3gen2-multimedia	kbdev-qcs8300-ride-multimedia	kbdev-qcs9100-ride-r3-multimedia	kbdev-shikra-iqs-evk-multimedia
BT_FW_KMD_Service	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
BT_ON_OFF	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
BT_SCAN	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
CPUFreq_Validation	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
CPU_affinity	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
DSP_AudioPD	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
Ethernet_Basic_Validation	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
Freq_Scaling	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
GIC	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
IPA	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
Interrupts	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
KVM_Driver	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
KVM_EL2_DTB	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
KVM_Infra	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
OpenCV	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
PCIe	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
Probe_Failure_Check	◻️	❌ Fail	❌ Fail	◻️	◻️	◻️	◻️	◻️	◻️
RMNET	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
UFS_Validation	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
USBHost	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
WiFi_Firmware_Driver	◻️	✅ Pass	❌ Fail	◻️	◻️	◻️	◻️	◻️	◻️
WiFi_OnOff	◻️	✅ Pass	❌ Fail	◻️	◻️	◻️	◻️	◻️	◻️
adsp_remoteproc	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
cdsp_remoteproc	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
gpdsp_remoteproc	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
hotplug	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
irq	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
kaslr	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
pinctrl	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
qcom_hwrng	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
rngtest	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
shmbridge	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
smmu	◻️	❌ Fail	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
watchdog	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️
wpss_remoteproc	◻️	✅ Pass	✅ Pass	◻️	◻️	◻️	◻️	◻️	◻️

[qcomlnxci]

Test jobs on 40e23cf

• multimedia Job 267806 on hamoa-iot-evk
• multimedia Job 267810 on lemans-evk
• multimedia Job 267805 on monaco-evk
• multimedia Job 267809 on purwa-iot-evk
• multimedia Job 267808 on qcs615-ride
• multimedia Job 267811 on qcs6490-rb3gen2
• multimedia Job 267813 on qcs8300-ride
• multimedia Job 267807 on qcs9100-ride-r3
• multimedia Job on qrb2210-rb1
• multimedia Job 267812 on shikra-iqs-evk

[qlijarvis]

LAVA Failed Case Triage Summary

PR: #977

Job 267805 | SoC monaco-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/267805

Failed test cases in LAVA job 267805 (SoC: monaco-evk).

  Case 1: Probe_Failure_Check (WiFi/BT firmware load false positive — suppressed per known benign failure rules)

1. Failed case: Probe_Failure_Check (WiFi/BT firmware load false positive — suppressed per known benign failure rules)
2. Root cause: The Probe_Failure_Check test detected firmware load failures for regulatory.db, Bluetooth firmware (wcnhpbtfw21.tlv, hpbtfw21.tlv), and WiFi firmware (ath11k/WCN6855/hw2.1/nfa765/amss.bin), culminating in ath11k_pci probe failure with error -110 (ETIMEDOUT). However, BT_ON_OFF functional test passed, confirming Bluetooth firmware loaded successfully at runtime. The WiFi probe failure is genuine and unrelated to the PR (which only modifies purwa-iot-evk eDP display DTS, not monaco-evk WiFi/BT configuration).
3. Possible fix: Suppress the Bluetooth firmware load failures per Rule 3 of lava-known-benign-failures.md (BT_ON_OFF passed). The WiFi ath11k_pci probe failure is a pre-existing monaco-evk board/firmware issue not introduced by this PR — the PR changes only purwa-iot-evk display overlay and does not touch WiFi/BT drivers or monaco-evk DTS. Recommend: (1) Mark BT firmware failures as suppressed/benign in CI reporting; (2) Investigate monaco-evk WiFi firmware availability and ath11k_pci timeout separately as a board-specific infra issue; (3) Approve the PR as the failure is not PR-introduced.
4. Detail analysis attachment: failed_case_job267805_1_detailed.md

  Case 2: WiFi_Firmware_Driver

1. Failed case: WiFi_Firmware_Driver
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: Add the missing WCN6855 WiFi firmware files to the rootfs image for monaco-evk. Specifically, ensure ath11k/WCN6855/hw2.1/nfa765/amss.bin and related board files are included in the linux-firmware package or the Yocto image recipe. Verify the firmware path matches the driver's request path exactly.
4. Detail analysis attachment: failed_case_job267805_2_detailed.md

  Case 3: WiFi_OnOff

1. Failed case: WiFi_OnOff
2. Root cause: ath11k_pci driver probe failed with error -110 (ETIMEDOUT) on Monaco EVK due to missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin in the rootfs, causing MHI power-up timeout during WCN6855 hw2.1 PCIe WiFi module initialization.
3. Possible fix: Add the missing WCN6855 firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/ath11k/WCN6855/hw2.1/nfa765/) in the Yocto build configuration or verify that the linux-firmware package includes the nfa765 variant firmware for Monaco EVK's WCN6855 hw2.1 WiFi module.
4. Detail analysis attachment: failed_case_job267805_3_detailed.md

  Case 4: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: LAVA test suite completed all individual test cases but was marked as failed by LAVA infrastructure due to "unfinished test run" despite all tests executing to completion. The test suite ran for 433.96 seconds, executed 35 test cases (32 passed, 3 failed: Probe_Failure_Check, WiFi_Firmware_Driver, WiFi_OnOff), and reached <LAVA_TEST_RUNNER EXIT>, but LAVA dispatcher incorrectly classified the run as "unfinished" and applied a fail verdict at the suite level.
3. Possible fix: This is a LAVA infrastructure false-positive failure. The actual test failures (WiFi probe error -110 for ath11k_pci driver on monaco-evk) are unrelated to the PR changes (which only modify purwa-iot-evk DTS files for eDP overlay). Re-trigger the LAVA job; if the "unfinished test run" error persists, investigate LAVA dispatcher timeout or test runner exit signal handling. The WiFi probe failures are pre-existing board/firmware issues on monaco-evk and should be tracked separately.
4. Detail analysis attachment: failed_case_job267805_4_detailed.md

Job 267806 | SoC hamoa-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/267806

No failed cases detected from the LAVA results section.

Job 267807 | SoC qcs9100-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/267807

No failed cases detected from the LAVA results section.

Job 267808 | SoC qcs615-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/267808

Failed test cases in LAVA job 267808 (SoC: qcs615-ride).

  Case 1: Probe_Failure_Check — regulatory.db firmware load failure (known benign)

1. Failed case: Probe_Failure_Check — regulatory.db firmware load failure (known benign)
2. Root cause: The cfg80211 wireless regulatory subsystem attempted to load the optional regulatory.db firmware file during boot, which is not present in the rootfs. This is a known benign failure because: (1) regulatory.db is optional — cfg80211 falls back to compiled-in regulatory rules when the file is absent, (2) WiFi functionality is confirmed working — ath11k_pci driver probed successfully, PCIe link is active, and wpss_remoteproc test passed, (3) the error is from "faux_driver" (a placeholder name in cfg80211's firmware request path), not an actual driver failure.
3. Possible fix: Suppress this failure in the Probe_Failure_Check test pattern matching — add regulatory.db firmware load errors to the known benign exclusion list. The test should only fail for genuine probe failures that prevent device functionality. Alternatively, if strict firmware presence validation is required, add the linux-firmware package containing regulatory.db to the rootfs image.
4. Detail analysis attachment: failed_case_job267808_1_detailed.md

  Case 2: ** smmu

1. Failed case: ** smmu
2. Root cause: ** Device tree validation failure — video codec child devices (video-decoder, video-encoder) lack explicit IOMMU group sysfs entries, though parent device aa00000.video-codec is correctly attached to IOMMU group 7 and no SMMU runtime errors occurred.
3. Possible fix: This is a test expectation mismatch, not a kernel regression. Either: (1) update qcs615-ride DT to add explicit iommu bindings for video-mem2mem child devices if required by hardware, or (2) adjust the SMMU test to accept inherited IOMMU protection from parent video-codec device when child devices are video-mem2mem instances.
4. Detail analysis attachment: failed_case_job267808_2_detailed.md

Job 267809 | SoC purwa-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/267809

No failed cases detected from the LAVA results section.

Job 267810 | SoC lemans-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/267810

Failed test cases in LAVA job 267810 (SoC: lemans-evk).

  Case 1: Probe_Failure_Check — Benign Firmware Load Failures (Suppressed)

1. Failed case: Probe_Failure_Check — Benign Firmware Load Failures (Suppressed)
2. Root cause: The Probe_Failure_Check test detected three firmware load failures during boot: (1) regulatory.db from faux_driver (a test/placeholder driver, not production), (2) qca/wcnhpbtfw21.tlv and (3) qca/hpbtfw21.tlv from Bluetooth driver. However, all three are benign false positives: Bluetooth firmware fallback succeeded (BT_ON_OFF test passed, hci0 UP with valid BD address), WiFi functional (WiFi_OnOff passed), and regulatory.db is loaded by a non-production faux_driver. These failures are pre-existing infrastructure noise unrelated to the PR (which only modifies eDP display overlay DTS).
3. Possible fix: Suppress these known-benign firmware load failures in the Probe_Failure_Check test logic by adding exception rules: (1) exclude "faux_driver regulatory" messages, (2) exclude Bluetooth firmware load failures when BT_ON_OFF test passes (per lava-known-benign-failures.md Rule 3), (3) exclude WiFi/regulatory firmware failures when WiFi_OnOff passes. No kernel changes required — this is a test framework tuning issue.
4. Detail analysis attachment: failed_case_job267810_1_detailed.md

  Case 2: smmu

1. Failed case: smmu
2. Root cause: Video codec device (aa00000.video-codec) is not attached to any IOMMU group on lemans-evk platform — this is a pre-existing platform configuration issue, not introduced by PR Add eDP display overlays for hamoa and purwa IoT EVKs #977 which only modifies purwa-iot-evk device tree files for eDP display overlay support.
3. Possible fix: Add IOMMU binding for the video codec device node in the lemans-evk device tree (arch/arm64/boot/dts/qcom/sa8775p-lemans-evk.dts or sa8775p.dtsi). The video codec node at 0xaa00000 needs an iommus property pointing to the appropriate SMMU instance and stream ID.
4. Detail analysis attachment: failed_case_job267810_2_detailed.md

  Case 3: 0_qcom-next-ci-premerge-tests (LAVA Test Runner Infrastructure Issue)

1. Failed case: 0_qcom-next-ci-premerge-tests (LAVA Test Runner Infrastructure Issue)
2. Root cause: LAVA test runner marked the test definition as failed despite all individual test cases passing and the test shell completing normally; the "Marking unfinished test run as failed" error indicates LAVA's internal state tracking detected an inconsistency between expected and completed tests, likely due to the test runner expecting additional test cases that were not executed or a mismatch in the test completion signal handling.
3. Possible fix: Re-trigger the LAVA job to confirm this is a transient LAVA infrastructure issue; if the failure persists, review the LAVA job definition and test runner configuration to ensure the expected test list matches the actual tests being executed, and verify that all test completion signals are being properly sent and received by the LAVA dispatcher.
4. Detail analysis attachment: failed_case_job267810_3_detailed.md

Job 267811 | SoC qcs6490-rb3gen2

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/267811

No failed cases detected from the LAVA results section.

Job 267812 | SoC shikra-iqs-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/267812

No failed cases detected from the LAVA results section.

Job 267813 | SoC qcs8300-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/267813

No failed cases detected from the LAVA results section.