Skip to content

lemans: Fix duplicate cdsp_sw cooling device - #939

Merged
Salendarsingh Gaud (sgaud-quic) merged 3 commits into
qualcomm-linux:qcom-6.18.yfrom
dmantre:lemans-cdsp-fix
Aug 30, 2026
Merged

lemans: Fix duplicate cdsp_sw cooling device#939
Salendarsingh Gaud (sgaud-quic) merged 3 commits into
qualcomm-linux:qcom-6.18.yfrom
dmantre:lemans-cdsp-fix

Conversation

@dmantre

@dmantre dmantre commented Aug 11, 2026 •
edited
Loading

Copy link
Copy Markdown

Add a new compatible "qcom,qmi-cooling-cdsp1" with its own instance ID (0x44), and use it for cdsp1's cooling node so each CDSP gets its own distinct cooling device.

CRs-Fixed: 4553608

@qswat-orbit-external

qswat-orbit-external Bot commented Aug 11, 2026

Copy link
Copy Markdown

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

@qlijarvis

qlijarvis commented Aug 11, 2026

Copy link
Copy Markdown

PR #939 — validate-patch

PR: #939

Verdict Issues Detailed Report
❌ 0 Full report

Final Summary

  1. Lore link present: No — no lore.kernel.org link found in commit message; missing vendor prefix to indicate origin
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: N/A — no upstream posting found; appears to be vendor-only fix without proper QCLINUX: prefix
  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: #939 - arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling device
Upstream commit: N/A
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream N/A No upstream link provided
Body preserves rationale ⚠️ Brief description present but no upstream reference
Fixes tag present/correct ❌ Missing - should reference the commit that introduced the duplicate
Authorship preserved N/A No upstream to compare against
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/lemans.dtsi ⚠️ Changes compatible string from qcom,qmi-cooling-cdsp to qcom,qmi-cooling-cdsp1
drivers/soc/qcom/qmi-cooling.c ⚠️ Adds new compatible and instance ID for cdsp1

Issues

  1. Missing vendor prefix: Commit lacks a prefix (QCLINUX:, UPSTREAM:, FROMLIST:, etc.) to indicate its origin and upstream status.

  2. No lore.kernel.org link: No Link: tag pointing to an upstream posting or discussion. If this is vendor-only work, it should be prefixed with QCLINUX:. If it's intended for upstream, it should be posted to the mailing list first and tagged with FROMLIST:.

  3. Missing Fixes tag: This patch fixes a duplicate cooling device issue but doesn't reference the commit that introduced the problem. A Fixes: tag should be added to help with backporting and tracking.

  4. Insufficient commit message: The description is brief and doesn't explain:

    • Why the duplicate exists (was cdsp0 using the same compatible as cdsp1?)
    • What the user-visible impact is (duplicate sysfs entries? thermal management failure?)
    • Whether this is a platform-specific workaround or a proper fix

  5. Not present in qcom-next or topics: According to integration_presence_report.md, this commit is missing from both qcom-next and all topic branches, which is expected for a new PR but confirms it hasn't been integrated yet.

Verdict

Do not merge without corrections. This patch requires:

  1. Add appropriate vendor prefix (QCLINUX: if vendor-only, or FROMLIST: if posted upstream)
  2. Add Fixes: tag referencing the commit that introduced the duplicate
  3. Expand commit message to explain the root cause and impact
  4. If intended for upstream, post to linux-arm-msm and devicetree mailing lists first

Final Summary

  1. Lore link present: No — no lore.kernel.org link found in commit message; missing vendor prefix to indicate origin
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: N/A — no upstream posting found; appears to be vendor-only fix without proper QCLINUX: prefix
  4. PR present in qcom-next/topics: No — 1/1 commit missing from both qcom-next and topics (expected for new PR, but confirms not yet integrated)

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] arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling 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

qlijarvis commented Aug 11, 2026

Copy link
Copy Markdown

PR #939 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ✅ No style issues
dt-binding-check ⏭️ Skipped (no binding changes)
dtb-check ❌ New compatible string not in binding schema
sparse-check ✅ No static analysis issues
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ Missing required subject prefix
tag-check ❌ Subject prefix required for qcom-6.18.y

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #939 - arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling device
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/31507774483

Checker Result Summary
checkpatch ✅ No style issues
dt-binding-check ⏭️ Skipped (no binding changes)
dtb-check ❌ New compatible string not in binding schema
sparse-check ✅ No static analysis issues
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ Missing required subject prefix
tag-check ❌ Subject prefix required for qcom-6.18.y

❌ dtb-check

Root cause: The new compatible string qcom,qmi-cooling-cdsp1 is not declared in the DT binding schema.

Failure details:

lemans-evk.dtb: remoteproc@2a300000 (qcom,sa8775p-cdsp1-pas): cooling:compatible:0: 
  'qcom,qmi-cooling-cdsp1' is not one of ['qcom,qmi-cooling-modem', 'qcom,qmi-cooling-cdsp']
  from schema $id: http://devicetree.org/schemas/remoteproc/qcom,sa8775p-pas.yaml

arch/arm64/boot/dts/qcom/lemans-evk.dtb: /soc@0/remoteproc@2a300000/cooling: 
  failed to match any schema with compatible: ['qcom,qmi-cooling-cdsp1']

This error appears across multiple DTBs: lemans-evk.dtb, lemans-evk-el2.dtb, lemans-camx-el2.dtb, lemans-evk-camera-csi1-imx577.dtb, lemans-evk-camx.dtb, and all sa8775p-ride*.dtb variants.

Fix: Add qcom,qmi-cooling-cdsp1 to the DT binding schema. The binding file is likely Documentation/devicetree/bindings/remoteproc/qcom,sa8775p-pas.yaml or a referenced thermal/cooling binding. Update the enum or oneOf list to include the new compatible string:

properties:
  cooling:
    properties:
      compatible:
        enum:
          - qcom,qmi-cooling-modem
          - qcom,qmi-cooling-cdsp
          - qcom,qmi-cooling-cdsp1  # Add this line

Reproduce locally:

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

❌ check-patch-compliance

Root cause: Commit subject does not start with a required prefix tag.

Failure details:

Checking commit: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling device
Commit summary does not start with a required prefix

Fix: Add a valid prefix to the commit subject. Since this is a vendor-specific fix for a duplicate cooling device issue, the appropriate prefix depends on the patch origin:

  • If this fix is posted to lore.kernel.org → use FROMLIST:
  • If this is a vendor-only fix → use QCLINUX: (note: this will still fail check-patch-compliance due to checker limitations, but is correct for vendor-only changes)
  • If this fix is already merged upstream → use UPSTREAM: or BACKPORT:

Recommended action:

git rebase -i HEAD~1   # mark commit as 'edit'
git commit --amend -m "QCLINUX: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling device"
git rebase --continue

Note: The check-patch-compliance checker only accepts FROMLIST:, FROMGIT:, UPSTREAM:, and BACKPORT: prefixes. If this is a vendor-only change, the checker will continue to fail — this is a known limitation. However, the prefix is still required for all commits targeting branches other than qcom-next or qcom-next-staging.

❌ tag-check

Root cause: Target branch is qcom-6.18.y (not qcom-next or qcom-next-staging), so every commit must have a subject prefix.

Failure details:

Commit fd09da72a082 ("arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling device"): 
  subject line does not start with a required prefix.
All branches except qcom-next and qcom-next-staging require one of:
FROMLIST: / FROMGIT: / UPSTREAM: / BACKPORT: / QCLINUX: / PENDING: / WORKAROUND:

Fix: Same as check-patch-compliance above — add a valid prefix to the commit subject.

Verdict

2 blockers must be fixed before merge:

  1. dtb-check: Add qcom,qmi-cooling-cdsp1 to the DT binding schema (likely in Documentation/devicetree/bindings/remoteproc/qcom,sa8775p-pas.yaml or a referenced cooling binding).

  2. check-patch-compliance + tag-check: Add a subject prefix (QCLINUX: recommended for vendor-only changes, or FROMLIST: if posted upstream).

Note: If this is a vendor-only change and you use QCLINUX:, the check-patch-compliance checker will still fail due to its limitation of only accepting upstream-linkable prefixes. However, the prefix is still required for the tag-check validation and for proper commit categorization in the tree.

@qswat-orbit-external

qswat-orbit-external Bot commented Aug 12, 2026

Copy link
Copy Markdown

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

@qswat-orbit-external

qswat-orbit-external Bot commented Aug 12, 2026

Copy link
Copy Markdown

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

@qswat-orbit-external

qswat-orbit-external Bot commented Aug 12, 2026

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4553608 is not eligible for merge.

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

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

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

@qlijarvis

qlijarvis commented Aug 12, 2026

Copy link
Copy Markdown

PR #939 — validate-patch

PR: #939

Verdict Issues Detailed Report
❌ 0 Full report

Final Summary

  1. Lore link present: No — no lore.kernel.org links found in either commit message. Commits lack required prefix (UPSTREAM:, FROMLIST:, BACKPORT:, or QCLINUX:).

  2. Lore link matches PR commits: N/A — no lore link to compare against.

  3. Upstream patch status: Not upstream — no evidence of mailing list posting or mainline merge. These appear to be new patches that have not been submitted to the community.

  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: #939 - Add CDSP1 support and fix duplicate cdsp_sw cooling
Upstream commit: N/A (no lore.kernel.org links found)
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream ❌ No upstream link to compare against
Body preserves rationale ⚠️ Commit 1/2 has minimal description; Commit 2/2 has brief rationale
Fixes tag present/correct ❌ No Fixes tag in either commit
Authorship preserved N/A No upstream to compare against
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
drivers/soc/qcom/qmi-cooling.c ⚠️ New compatible added without dt-binding documentation reference
arch/arm64/boot/dts/qcom/lemans.dtsi ⚠️ Uses new compatible without upstream acceptance

Issues

Commit 1/2: soc: qcom: qmi-cooling: Add CDSP1 support

  1. Missing lore link: No Link: tag pointing to lore.kernel.org posting
  2. Missing commit prefix: Should have UPSTREAM:, FROMLIST:, BACKPORT:, or QCLINUX: prefix
  3. Missing Fixes tag: This appears to fix an issue (duplicate cooling devices) but has no Fixes: tag
  4. Incomplete description: Commit message doesn't explain why CDSP1 needs instance ID 0x44 or the problem being solved
  5. Missing dt-binding update: Adding a new compatible string requires corresponding dt-binding documentation

Commit 2/2: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling

  1. Missing lore link: No Link: tag pointing to lore.kernel.org posting
  2. Missing commit prefix: Should have UPSTREAM:, FROMLIST:, BACKPORT:, or QCLINUX: prefix
  3. Missing Fixes tag: Subject says "Fix" but no Fixes: tag identifying what commit introduced the duplicate
  4. Dependency on unmerged change: Uses qcom,qmi-cooling-cdsp1 compatible from commit 1/2 which is not yet upstream

Verdict

Do not merge without correction. Both commits lack mandatory upstream attribution (lore links and commit prefixes). If these are vendor-only changes, they must use the QCLINUX: prefix. If they are intended for upstream, they must be posted to the mailing list first and include FROMLIST: prefix with lore links. Additionally, commit 1/2 requires dt-binding documentation updates before it can be accepted upstream.

Final Summary

  1. Lore link present: No — no lore.kernel.org links found in either commit message. Commits lack required prefix (UPSTREAM:, FROMLIST:, BACKPORT:, or QCLINUX:).

  2. Lore link matches PR commits: N/A — no lore link to compare against.

  3. Upstream patch status: Not upstream — no evidence of mailing list posting or mainline merge. These appear to be new patches that have not been submitted to the community.

  4. PR present in qcom-next/topics: Fail — 2/2 commits are missing from both qcom-next and topics (per integration_presence_report.md). This is a validation failure as changes should be present in at least one integration branch before PR merge.

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

Commit Subject qcom-next topics Final
1/2 [PATCH 1/2] soc: qcom: qmi-cooling: Add CDSP1 support 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] arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling 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

qlijarvis commented Aug 12, 2026

Copy link
Copy Markdown

PR #939 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ✅ All commits pass style checks
dt-binding-check ⏭️ No binding changes
dtb-check ❌ New compatible string not in binding schema
sparse-check ✅ No sparse warnings
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ Missing required subject prefix on both commits
tag-check ❌ Subject prefix required (unless target is qcom-next/qcom-next-staging)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #939 - soc: qcom: qmi-cooling: Add CDSP1 support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/31567056921

Checker Result Summary
checkpatch ✅ All commits pass style checks
dt-binding-check ⏭️ No binding changes
dtb-check ❌ New compatible string not in binding schema
sparse-check ✅ No sparse warnings
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ Missing required subject prefix on both commits
tag-check ❌ Subject prefix required (unless target is qcom-next/qcom-next-staging)

❌ dtb-check

Root cause: The new compatible string qcom,qmi-cooling-cdsp1 is used in DTS but not declared in the DT binding schema.

Failure details:

lemans-evk.dtb: remoteproc@2a300000 (qcom,sa8775p-cdsp1-pas): cooling:compatible:0: 
  'qcom,qmi-cooling-cdsp1' is not one of ['qcom,qmi-cooling-modem', 'qcom,qmi-cooling-cdsp']
  from schema $id: http://devicetree.org/schemas/remoteproc/qcom,sa8775p-pas.yaml

arch/arm64/boot/dts/qcom/lemans-evk.dtb: /soc@0/remoteproc@2a300000/cooling: 
  failed to match any schema with compatible: ['qcom,qmi-cooling-cdsp1']

This error appears in multiple DTB files:

  • lemans-evk.dtb
  • lemans-evk-el2.dtb
  • lemans-camx-el2.dtb
  • lemans-evk-camera-csi1-imx577.dtb
  • lemans-evk-camx.dtb

Fix: Add the new compatible string to the DT binding schema. The binding file is likely Documentation/devicetree/bindings/thermal/qcom-qmi-cooling.yaml or referenced within Documentation/devicetree/bindings/remoteproc/qcom,sa8775p-pas.yaml.

Update the binding to include qcom,qmi-cooling-cdsp1 in the compatible enum:

properties:
  compatible:
    enum:
      - qcom,qmi-cooling-modem
      - qcom,qmi-cooling-cdsp
      - qcom,qmi-cooling-cdsp1  # Add this line

Reproduce locally:

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

❌ check-patch-compliance

Root cause: Both commits lack a required subject prefix (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:).

Failure details:

Checking commit: soc: qcom: qmi-cooling: Add CDSP1 support
Commit summary does not start with a required prefix

Checking commit: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling device
Commit summary does not start with a required prefix

Fix: Add an appropriate prefix to each commit subject. Choose based on the patch origin:

For commit 1 (driver change):

git rebase -i <base_sha>   # mark commit as 'edit'
git commit --amend -m "QCLINUX: soc: qcom: qmi-cooling: Add CDSP1 support"
# (or use FROMLIST: if posted upstream, with Link: tag)
git rebase --continue

For commit 2 (DTS change):

git rebase -i <base_sha>   # mark commit as 'edit'
git commit --amend -m "QCLINUX: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling device"
git rebase --continue

Note: If these patches are vendor-only changes with no upstream equivalent, use QCLINUX:. However, be aware that check-patch-compliance only accepts upstream-linkable prefixes (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:), so vendor-only commits will always fail this checker — this is a known limitation.

If the patches have been or will be posted upstream, use FROMLIST: and add a Link: tag pointing to the lore.kernel.org URL.

❌ tag-check

Root cause: Subject prefix is mandatory for all branches except qcom-next and qcom-next-staging.

Applies to: Both commits in this PR.

Fix: Same as check-patch-compliance above — add a valid prefix (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, or WORKAROUND:) to each commit subject.

Note: This check is skipped if the PR targets qcom-next or qcom-next-staging. Unable to verify target branch due to network connectivity; if the target is one of those branches, this check does not apply.

Verdict

2 blockers must be fixed before merge:

  1. DT binding update required — Add qcom,qmi-cooling-cdsp1 to the thermal/remoteproc binding schema to resolve dtb-check failures.

  2. Subject prefix required — Add appropriate prefix tags (QCLINUX: for vendor-only, or FROMLIST:/UPSTREAM: with Link: if posted upstream) to both commit subjects.

Recommended workflow:

  1. Add a third commit (or amend commit 1) to update the DT binding YAML with the new compatible string.
  2. Rebase to add subject prefixes to all commits.
  3. Re-run CI to verify dtb-check and check-patch-compliance pass.

@qlijarvis

qlijarvis commented Aug 12, 2026

Copy link
Copy Markdown

PR #939 — validate-patch

PR: #939

Verdict Issues Detailed Report
❌ 0 Full report

Final Summary

  1. Lore link present: No — no lore.kernel.org Link tags found in either commit message. Per validate-patch skill Step 1, this is a FAIL condition.

  2. Lore link matches PR commits: N/A — no lore link to compare against. Cannot verify diff faithfulness to upstream.

  3. Upstream patch status: N/A — no lore link provided. Cannot determine if patches are posted, under review, accepted, or rejected upstream.

  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: #939 - Add CDSP1 support and fix duplicate cdsp_sw cooling
Upstream commit: N/A
Verdict: ❌ FAIL

Commit Message

Commit 1/2: soc: qcom: qmi-cooling: Add CDSP1 support

Check Status Note
Subject matches upstream ❌ No upstream link to compare against
Body preserves rationale ⚠️ Rationale present but no upstream reference
Fixes tag present/correct N/A Not a fix commit
Authorship preserved ❌ No upstream author to verify against
Backport note (if applicable) N/A Not marked as backport
Commit prefix ❌ Missing required prefix (QCLINUX:/PENDING:/FROMLIST:/UPSTREAM:)

Commit 2/2: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling

Check Status Note
Subject matches upstream ❌ No upstream link to compare against
Body preserves rationale ⚠️ Rationale present but no upstream reference
Fixes tag present/correct ❌ Missing - this fixes a duplicate cooling device issue
Authorship preserved ❌ No upstream author to verify against
Backport note (if applicable) N/A Not marked as backport
Commit prefix ❌ Missing required prefix (QCLINUX:/PENDING:/FROMLIST:/UPSTREAM:)

Diff

Commit 1/2:

File Status Notes
drivers/soc/qcom/qmi-cooling.c ⚠️ Cannot verify against upstream - no lore link provided

Commit 2/2:

File Status Notes
arch/arm64/boot/dts/qcom/lemans.dtsi ⚠️ Cannot verify against upstream - no lore link provided

Issues

Critical Issues:

  1. No lore.kernel.org links found - Both commits lack Link: tags pointing to lore.kernel.org. Per the validate-patch skill Step 1, this is a FAIL condition. The skill can only validate patches against lore.kernel.org sources.

  2. Missing commit prefixes - Neither commit has a required prefix:

    • No UPSTREAM: (would require lore/kernel.org link)
    • No FROMLIST: (would require lore.kernel.org link)
    • No BACKPORT: (would require lore/kernel.org link)
    • No QCLINUX: (vendor-only, no link required)
    • No PENDING: (work-in-progress, no link required)
    • No WORKAROUND: (temporary fix, no link required)

  3. Missing Fixes tag in commit 2/2 - The second commit fixes a duplicate cooling device issue but lacks a Fixes: tag to reference the commit that introduced the duplicate.

  4. Not present in qcom-next or topics - Per integration_presence_report.md, both commits (2/2) are missing from qcom-next and all topic branches. This indicates the changes have not been integrated into the Qualcomm kernel tree.

Commit Message Quality Issues:

  1. Commit 1/2 - The commit message describes adding CDSP1 support but doesn't explain:

    • Why CDSP1 needs a separate instance ID
    • What hardware/platform requires this
    • Whether this is posted upstream or vendor-specific

  2. Commit 2/2 - The commit message mentions "Fix duplicate cdsp_sw cooling" but doesn't:

    • Identify which commit introduced the duplicate
    • Explain the impact of the duplicate (does it cause functional issues?)
    • Reference the first commit as a dependency

Verdict

Do not merge without corrections. Both commits fail validation due to missing lore.kernel.org links and missing commit prefixes required by the Qualcomm kernel tree conventions.

Required actions:

  1. If these are vendor-only changes (not posted upstream):

    • Add QCLINUX: prefix to both commit subjects
    • No lore link required
    • Update commit messages to clarify this is Qualcomm-specific

  2. If these are intended for upstream:

    • Post patches to the appropriate mailing list (linux-arm-msm@vger.kernel.org)
    • Add FROMLIST: prefix to both commit subjects
    • Add Link: https://lore.kernel.org/r/<message-id> tags
    • Re-run validation after posting

  3. Add Fixes tag to commit 2/2:

    Fixes: <sha> ("commit that added duplicate cdsp cooling node")

  4. Improve commit messages:

    • Commit 1/2: Explain why CDSP1 needs separate instance ID
    • Commit 2/2: Explain impact of duplicate and dependency on commit 1/2

Final Summary

  1. Lore link present: No — no lore.kernel.org Link tags found in either commit message. Per validate-patch skill Step 1, this is a FAIL condition.

  2. Lore link matches PR commits: N/A — no lore link to compare against. Cannot verify diff faithfulness to upstream.

  3. Upstream patch status: N/A — no lore link provided. Cannot determine if patches are posted, under review, accepted, or rejected upstream.

  4. PR present in qcom-next/topics: Fail — 2/2 commits are missing from both qcom-next and all topic branches (per integration_presence_report.md). This indicates the changes have not been integrated into the Qualcomm kernel tree.

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

Commit Subject qcom-next topics Final
1/2 [PATCH 1/2] soc: qcom: qmi-cooling: Add CDSP1 support 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] arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling 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

qlijarvis commented Aug 12, 2026

Copy link
Copy Markdown

PR #939 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ✅ All commits pass style checks
dt-binding-check ⏭️ Skipped - no binding changes
dtb-check ❌ New compatible string not in binding schema
sparse-check ✅ No sparse warnings in changed code
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ Missing required subject prefix on both commits
tag-check ❌ Subject prefix required (not qcom-next/qcom-next-staging)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #939 - Add CDSP1 QMI cooling support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/31569627875

Checker Result Summary
checkpatch ✅ All commits pass style checks
dt-binding-check ⏭️ Skipped - no binding changes
dtb-check ❌ New compatible string not in binding schema
sparse-check ✅ No sparse warnings in changed code
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ Missing required subject prefix on both commits
tag-check ❌ Subject prefix required (not qcom-next/qcom-next-staging)

❌ dtb-check

Root cause: The new compatible string qcom,qmi-cooling-cdsp1 is not documented in the device tree binding schema.

Failure details:

arch/arm64/boot/dts/qcom/lemans-evk.dtb: /soc@0/remoteproc@2a300000/cooling: 
  failed to match any schema with compatible: ['qcom,qmi-cooling-cdsp1']

remoteproc@2a300000 (qcom,sa8775p-cdsp1-pas): cooling:compatible:0: 
  'qcom,qmi-cooling-cdsp1' is not one of ['qcom,qmi-cooling-modem', 'qcom,qmi-cooling-cdsp']
  from schema $id: http://devicetree.org/schemas/remoteproc/qcom,sa8775p-pas.yaml

This error appears across multiple DTB files: lemans-evk.dtb, lemans-evk-el2.dtb, lemans-camx-el2.dtb, qcs9100-ride-r3-el2.dtb, sa8775p-ride.dtb, and others.

Fix: Add the new compatible string to the device tree binding schema. The binding file is likely Documentation/devicetree/bindings/remoteproc/qcom,sa8775p-pas.yaml (or a thermal/cooling binding that it references). Update the enum to include:

properties:
  cooling:
    properties:
      compatible:
        enum:
          - qcom,qmi-cooling-modem
          - qcom,qmi-cooling-cdsp
          - qcom,qmi-cooling-cdsp1  # Add this line

Reproduce locally:

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

❌ check-patch-compliance

Root cause: Both commits lack the required subject prefix (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, etc.).

Failure details:

Checking commit: soc: qcom: qmi-cooling: Add CDSP1 support
Commit summary does not start with a required prefix

Checking commit: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling
Commit summary does not start with a required prefix

Fix: Add an appropriate prefix to each commit subject line:

Commit 1: 3d166cc699e8 - "soc: qcom: qmi-cooling: Add CDSP1 support"

git rebase -i HEAD~2
# Mark first commit as 'edit'
git commit --amend -m "QCLINUX: soc: qcom: qmi-cooling: Add CDSP1 support"
# (keep the rest of the commit message)
git rebase --continue

Commit 2: 1b0410fa1e4b - "arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling"

# Mark second commit as 'edit'
git commit --amend -m "QCLINUX: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling"
# (keep the rest of the commit message)
git rebase --continue

Note: Use QCLINUX: if this is a vendor-specific change with no upstream equivalent. If this work has been or will be posted upstream, use FROMLIST: and add a Link: tag pointing to the lore.kernel.org URL.

Reproduce locally:

# From kernel-checkers repo
./check-patch-compliance.sh

❌ tag-check

Root cause: Both commits are missing the mandatory subject prefix required for all branches except qcom-next and qcom-next-staging.

Failure details:

Based on the integration presence report showing these commits are NOT in qcom-next, and the checker failure pattern, this PR is targeting a branch that requires subject prefixes.

Commit 1: 3d166cc699e8 - "soc: qcom: qmi-cooling: Add CDSP1 support"
❌ Subject line does not start with a required prefix.

Commit 2: 1b0410fa1e4b - "arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling"
❌ Subject line does not start with a required prefix.

All branches except qcom-next and qcom-next-staging require one of:

  • FROMLIST: - Patch posted to mailing list (lore.kernel.org)
  • FROMGIT: - Patch taken from a maintainer git tree
  • UPSTREAM: - Patch merged into Linus's mainline tree
  • BACKPORT: - Upstream patch backported with modifications
  • QCLINUX: - Vendor-only change with no upstream equivalent
  • PENDING: - Work-in-progress, not yet posted upstream
  • WORKAROUND: - Temporary fix not suitable for upstream

Fix: Same as check-patch-compliance fix above - add the appropriate prefix to both commit subjects.

Verdict

3 blockers must be fixed before merge:

  1. Add DT binding documentation for qcom,qmi-cooling-cdsp1 to fix dtb-check failures
  2. Add subject prefix to commit 1: "soc: qcom: qmi-cooling: Add CDSP1 support"
  3. Add subject prefix to commit 2: "arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling"

Recommended workflow:

  1. Add the new compatible string to the appropriate DT binding YAML file (likely in Documentation/devicetree/bindings/remoteproc/ or a thermal/cooling binding)
  2. Rebase the two commits to add QCLINUX: prefix (or FROMLIST: if posting upstream)
  3. Re-run CI to verify all checkers pass

@qswat-orbit-external

qswat-orbit-external Bot commented Aug 12, 2026

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4553608 is not eligible for merge.

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

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

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

@dmantre
dmantre force-pushed the lemans-cdsp-fix branch 4 times, most recently from 9989f73 to efe2237 Compare August 12, 2026 10:46
@qlijarvis

qlijarvis commented Aug 12, 2026

Copy link
Copy Markdown

PR #939 — validate-patch

PR: #939

Verdict Issues Detailed Report
❌ 0 Full report

Final Summary

  1. Lore link present: Yes - but all three links are WRONG
  2. Lore link matches PR commits: No - PR content is about qmi-cooling bindings/driver; lore links point to remoteproc TMD patches from a completely different series
  3. Upstream patch status: Cannot determine - wrong lore links provided
  4. PR present in qcom-next/topics: Fail - 3/3 commit(s) are missing from both qcom-next and topics
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #939 - FROMLIST: Add qcom,qmi-cooling-cdsp1 support
Upstream commits: Multiple lore links provided
Verdict: ❌ FAIL

Critical Issue: Wrong Lore Links

The PR commits link to patches from the series "[PATCH v8 0/9] Add support for Qualcomm remoteproc subsystem cooling" but the PR content does NOT match those patches at all.

Lore series (20260809-b4-qmi-tmd-v8) contains:

  • Patch 1/9: "dt-bindings: remoteproc: qcom,pas: add #cooling-cells property"
  • Patch 2/9: "soc: qcom: Add QMI TMD support for remote thermal"
  • Patch 6/9: "arm64: dts: qcom: lemans: Enable CDSP cooling" (adds cooling-maps to remoteproc nodes)

PR commits claim to be:

  • Patch 1: "dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1"
  • Patch 2: "soc: qcom: qmi-cooling: Add CDSP1 support"
  • Patch 3: "arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling"

Commit Message

Check Status Note
Subject matches upstream ❌ Subjects completely different - wrong lore links
Body preserves rationale ❌ Cannot verify - lore links point to wrong patches
Fixes tag present/correct N/A No Fixes tag in PR or lore
Authorship preserved ⚠️ Author changed from Gaurav Kohli to Dipa Ramesh Mantre
Backport note (if applicable) N/A FROMLIST prefix used

Diff

File Status Notes
Documentation/devicetree/bindings/thermal/qcom,qmi-cooling.yaml ❌ File not touched in linked lore patches
drivers/soc/qcom/qmi-cooling.c ❌ File not touched in linked lore patches
arch/arm64/boot/dts/qcom/lemans.dtsi ❌ PR changes compatible string; lore patch 6/9 adds cooling-maps - completely different changes

Issues

  1. Wrong lore message IDs: All three PR commits link to patches from the "remoteproc subsystem cooling" series, but the PR content is about "qmi-cooling" device bindings and driver changes. These are unrelated patch series.

  2. Author mismatch: The lore series author is Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>, but the PR commits show Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com> as author. For FROMLIST commits, the original author's Signed-off-by should be present, but it's missing.

  3. Subject mismatch:

    • PR patch 1 subject mentions "qcom,qmi-cooling" bindings, but lore patch 1/9 is about "qcom,pas" remoteproc bindings
    • PR patch 2 subject mentions "qmi-cooling" driver, but lore patch 2/9 is about "QMI TMD" support
    • PR patch 3 subject mentions "Fix duplicate cdsp_sw", but lore patch 6/9 is about "Enable CDSP cooling"

  4. File path mismatch:

    • PR touches qcom,qmi-cooling.yaml and qmi-cooling.c - these files are NOT modified in the linked lore patches
    • Lore patches touch qcom,pas-common.yaml, add new TMD driver files, and modify remoteproc drivers

  5. Diff content mismatch: The PR changes are structurally incompatible with the lore patches - they modify completely different subsystems (thermal/qmi-cooling vs remoteproc/TMD).

Verdict

DO NOT MERGE - The lore links are completely wrong. The PR appears to be from a different patch series that is not linked in the commit messages. The correct lore links must be found and added before this PR can be validated.

Recommendation

  1. Find the correct lore.kernel.org links for these qmi-cooling patches (search for "qcom,qmi-cooling-cdsp1" on lore)
  2. Update all three commit messages with the correct Link: tags
  3. Verify the original author (should be in From: or have their Signed-off-by: present)
  4. Re-submit the PR with corrected commit messages

Final Summary

  1. Lore link present: Yes - but all three links are WRONG
  2. Lore link matches PR commits: No - PR content is about qmi-cooling bindings/driver; lore links point to remoteproc TMD patches from a completely different series
  3. Upstream patch status: Cannot determine - wrong lore links provided
  4. PR present in qcom-next/topics: No - per integration_presence_report.md, all 3 commits missing from both qcom-next and topics

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

Commit Subject qcom-next topics Final
1/3 [PATCH 1/3] FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
2/3 [PATCH 2/3] FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
3/3 [PATCH 3/3] FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw 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/3
partial_commits: 0/3
missing_commits: 3/3
topics_checked_for_commits: 3/3
final_summary: PR present in qcom-next/topics: Fail - 3/3 commit(s) are missing from both qcom-next and topics

@qlijarvis

qlijarvis commented Aug 12, 2026

Copy link
Copy Markdown

PR #939 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ❌ 1 warning: DT binding split required
dt-binding-check ✅ Passed
dtb-check ✅ Passed
sparse-check ✅ Passed
check-uapi-headers ✅ Passed
check-patch-compliance ❌ 2 commits missing required prefix
tag-check ❌ 2 commits missing FROMLIST: prefix in git tree

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #939 - Add CDSP1 support to qmi-cooling and fix lemans DTS
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/31575094903

Checker Result Summary
checkpatch ❌ 1 warning: DT binding split required
dt-binding-check ✅ Passed
dtb-check ✅ Passed
sparse-check ✅ Passed
check-uapi-headers ✅ Passed
check-patch-compliance ❌ 2 commits missing required prefix
tag-check ❌ 2 commits missing FROMLIST: prefix in git tree

❌ checkpatch

Root cause: Commit 7274bf6 includes both DT binding changes and driver code changes in a single patch.

Failure details:

Commit 7274bf6425e7 ("soc: qcom: qmi-cooling: Add CDSP1 support")
WARNING: DT binding docs and includes should be a separate patch. 
See: Documentation/devicetree/bindings/submitting-patches.rst
7274bf6425e74aa26198bdc213ac28409a426b44 total: 0 errors, 1 warnings, 0 checks, 45 lines checked

Fix: Split the patch into two separate commits:

  1. First commit: DT binding changes only (Documentation/devicetree/bindings/thermal/qcom,qmi-cooling.yaml and include/dt-bindings/thermal/qcom,qmi-cooling.h)
  2. Second commit: Driver implementation (drivers/soc/qcom/qmi_cooling.c)

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 8635749eab9a..69354dffcaa8

❌ check-patch-compliance

Root cause: Two commits in the git tree are missing the required FROMLIST: prefix in their subject lines.

Failure details:

Checking commit: soc: qcom: qmi-cooling: Add CDSP1 support
Commit summary does not start with a required prefix

Checking commit: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling
Commit summary does not start with a required prefix

Analysis: The patch file (pr.patch) shows all 3 commits have FROMLIST: prefix:

  • FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add ...
  • FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support
  • FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling

However, the checker is seeing commits in the git tree without the prefix:

  • soc: qcom: qmi-cooling: Add CDSP1 support (missing FROMLIST:)
  • arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling (missing FROMLIST:)

Note: The first commit (dt-bindings) was not checked by check-patch-compliance, which only checked 2 of the 3 commits.

Fix: Amend the commit messages in the git tree to include the FROMLIST: prefix:

# Interactive rebase to edit commits
git rebase -i 8635749eab9a

# For each commit marked as 'edit':
git commit --amend -m "FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support"
# (keep the rest of the commit message body unchanged)
git rebase --continue

# Repeat for the second commit:
git commit --amend -m "FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling"
git rebase --continue

Required prefix tags: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, or WORKAROUND:

❌ tag-check

Root cause: Same as check-patch-compliance — commits in the git tree are missing the mandatory subject-line prefix.

Failure details:
The following commits do not start with a required prefix:

  • Commit 7274bf6: soc: qcom: qmi-cooling: Add CDSP1 support
  • Commit 69354df: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling

Note: This check applies to all branches except qcom-next and qcom-next-staging. Based on the checker run, the target branch appears to require prefix tags.

Fix: Same as check-patch-compliance above — add FROMLIST: prefix to both commit subjects.

Verdict

3 blockers must be fixed before merge:

  1. Split the DT binding patch — Separate the binding changes from the driver code (checkpatch warning)
  2. Add FROMLIST: prefix to commit 2 — soc: qcom: qmi-cooling: Add CDSP1 support
  3. Add FROMLIST: prefix to commit 3 — arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling

Root cause summary: The patch file shows correct FROMLIST: prefixes, but the actual git commits in the PR branch do not have these prefixes. This suggests the commits were created or amended without the prefix, even though the patch export includes them.

Recommended action:

  1. Rebase interactively to split the binding patch into a separate commit
  2. Amend all commit messages to ensure FROMLIST: prefix is in the actual git commit subject (not just the patch file)
  3. Force-push the corrected branch
  4. Re-trigger CI

@qlijarvis

qlijarvis commented Aug 12, 2026

Copy link
Copy Markdown

PR #939 — validate-patch

PR: #939

Verdict Issues Detailed Report
❌ 3 Full report

Final Summary

  1. Lore link present: Yes — but links point to wrong patches (remoteproc/QMI TMD series instead of qmi-cooling changes)
  2. Lore link matches PR commits: ❌ No — complete subject/file/content mismatch across all three commits
  3. Upstream patch status: ⏳ Unknown — the linked lore patches are ACKed, but they are unrelated to the PR content; actual upstream status of the qmi-cooling patches cannot be determined
  4. PR present in qcom-next/topics: Fail - 3/3 commit(s) are missing from both qcom-next and topics
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #939 - "FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1" (3 commits)
Upstream commit: https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-1-b15d47adc379@oss.qualcomm.com/ (and related)
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream ❌ Complete mismatch — PR subjects reference qcom,qmi-cooling driver; lore subjects reference remoteproc: qcom,pas and QMI TMD
Body preserves rationale ❌ Cannot verify — lore patches are for a different subsystem
Fixes tag present/correct N/A No Fixes tags in PR or lore
Authorship preserved ⚠️ From: is Dipa Ramesh Mantre in both PR and lore, but patches are unrelated
Backport note (if applicable) N/A FROMLIST: prefix used (not a backport)

Diff

File Status Notes
Documentation/devicetree/bindings/thermal/qcom,qmi-cooling.yaml ❌ PR modifies this file; lore patch 1/9 modifies remoteproc/qcom,pas-common.yaml — completely different files
drivers/soc/qcom/qmi-cooling.c ❌ PR modifies this file; lore patch 2/9 adds new file drivers/soc/qcom/qmi_tmd.c — completely different changes
arch/arm64/boot/dts/qcom/lemans.dtsi ❌ PR changes qcom,qmi-cooling-cdsp → qcom,qmi-cooling-cdsp1; lore patch 6/9 adds new cooling node with #cooling-cells — completely different changes

Issues

Critical: Incorrect lore links

The PR commits reference lore.kernel.org message IDs from a completely different patch series:

  • PR commit 1/3: Claims to add qcom,qmi-cooling-cdsp1 compatible to Documentation/devicetree/bindings/thermal/qcom,qmi-cooling.yaml
    Lore patch v8 1/9: Actually adds #cooling-cells property to Documentation/devicetree/bindings/remoteproc/qcom,pas-common.yaml and introduces include/dt-bindings/thermal/qcom,pas.h

  • PR commit 2/3: Claims to add CDSP1 support to drivers/soc/qcom/qmi-cooling.c
    Lore patch v8 2/9: Actually introduces a new driver drivers/soc/qcom/qmi_tmd.c for QMI TMD (Thermal Mitigation Device) support

  • PR commit 3/3: Claims to fix duplicate cdsp_sw cooling by changing compatible string
    Lore patch v8 6/9: Actually enables CDSP cooling by adding a new cooling subnode with #cooling-cells = <3>

The lore series (v8 0/9) is titled "Add support for Qualcomm remoteproc subsystem cooling" and introduces a new QMI TMD framework for remoteproc thermal management. The PR patches are about extending an existing qmi-cooling driver with a new cdsp1 compatible. These are entirely different features.

Root cause: The PR author appears to have copied message IDs from an unrelated patch series. The correct lore links for these qmi-cooling patches do not exist in the provided evidence, suggesting either:

  1. The patches were never posted to lore.kernel.org, or
  2. They were posted under different message IDs that are not referenced in the PR

Upstream Patch Status

Commit Community Verdict
v8 1/9 (remoteproc: qcom,pas) ✅ ACKed — Reviewed-by: Krzysztof Kozlowski, Acked-by: Daniel Lezcano
v8 2/9 (QMI TMD driver) ✅ ACKed — Reviewed-by: Daniel Lezcano
v8 6/9 (lemans: Enable CDSP cooling) ✅ ACKed — Reviewed-by: Dmitry Baryshkov, Daniel Lezcano

Note: The upstream status above applies to the lore patches at the linked message IDs, not the PR patches. Since the PR patches do not match the lore patches, the upstream acceptance status is unknown for the actual PR content.

qcom-next Presence

Per integration_presence_report.md:

Commit Status
1/3 (dt-bindings: thermal: qcom,qmi-cooling) ⚠️ Not in qcom-next — missing from both qcom-next (49dbe0d) and topics
2/3 (soc: qcom: qmi-cooling: Add CDSP1) ⚠️ Not in qcom-next — missing from both qcom-next and topics
3/3 (arm64: dts: qcom: lemans: Fix duplicate) ⚠️ Not in qcom-next — missing from both qcom-next and topics

Overall: 0/3 commits present in qcom-next or topics.

Verdict

❌ DO NOT MERGE

This PR has incorrect lore.kernel.org links. The referenced message IDs point to a remoteproc/QMI TMD patch series that is completely unrelated to the PR's actual content (qmi-cooling driver changes). This violates the fundamental requirement of the FROMLIST: prefix, which mandates that the Link: tag must point to the actual upstream posting of the patch.

Required actions before merge:

  1. Verify upstream posting: Confirm whether these qmi-cooling patches were actually posted to lore.kernel.org. If yes, update the Link: tags with the correct message IDs.

  2. If not posted upstream: Change the prefix from FROMLIST: to PENDING: or QCLINUX: depending on intent, and remove the lore links.

  3. If these are backports of accepted patches: Change prefix to UPSTREAM: or BACKPORT: and link to the merged kernel.org commits.

  4. Verify qcom-next presence: All three commits are missing from qcom-next and topics. If these are intended for integration, they should be present in at least one topic branch before merging to qcom-next.

Final Summary

  1. Lore link present: Yes — but links point to wrong patches (remoteproc/QMI TMD series instead of qmi-cooling changes)
  2. Lore link matches PR commits: ❌ No — complete subject/file/content mismatch across all three commits
  3. Upstream patch status: ⏳ Unknown — the linked lore patches are ACKed, but they are unrelated to the PR content; actual upstream status of the qmi-cooling patches cannot be determined
  4. PR present in qcom-next/topics: ❌ Fail — 3/3 commits missing from both qcom-next (49dbe0d) and all topic branches

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

Commit Subject qcom-next topics Final
1/3 [PATCH 1/3] FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
2/3 [PATCH 2/3] FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
3/3 [PATCH 3/3] FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw 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/3
partial_commits: 0/3
missing_commits: 3/3
topics_checked_for_commits: 3/3
final_summary: PR present in qcom-next/topics: Fail - 3/3 commit(s) are missing from both qcom-next and topics

@qlijarvis

qlijarvis commented Aug 12, 2026

Copy link
Copy Markdown

PR #939 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ✅ All commits pass style checks
dt-binding-check ✅ Binding validation passed
dtb-check ✅ DTB validation passed
sparse-check ✅ No sparse warnings
check-uapi-headers ✅ No UAPI changes detected
check-patch-compliance ❌ 3 commits missing required prefix
tag-check ❌ Subject prefix required (assuming non-qcom-next branch)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #939 - FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/31578988755

Checker Result Summary
checkpatch ✅ All commits pass style checks
dt-binding-check ✅ Binding validation passed
dtb-check ✅ DTB validation passed
sparse-check ✅ No sparse warnings
check-uapi-headers ✅ No UAPI changes detected
check-patch-compliance ❌ 3 commits missing required prefix
tag-check ❌ Subject prefix required (assuming non-qcom-next branch)

❌ check-patch-compliance

Root cause: All three commits in the PR are missing the required subject-line prefix (FROMLIST:, FROMGIT:, UPSTREAM:, or BACKPORT:).

Failure details:

Checking commit: dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1
Commit summary does not start with a required prefix

Checking commit: soc: qcom: qmi-cooling: Add CDSP1 support
Commit summary does not start with a required prefix

Checking commit: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling
Commit summary does not start with a required prefix

Analysis:

The checker detected that the actual git commit subjects in the PR branch do not contain the FROMLIST: prefix, even though:

  1. The commits have Link: trailers pointing to lore.kernel.org
  2. The patch file (pr.patch) shows FROMLIST: in the subjects

This indicates a mismatch between the patch file and the actual git commits in the PR branch. The git commits need to be amended to include the prefix.

Affected commits:

  • c5ad079e8a5b - "dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1"
  • 66011d9573a7 - "soc: qcom: qmi-cooling: Add CDSP1 support"
  • ead4076343a8 - "arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling"

Fix:

Each commit subject must start with FROMLIST: since these patches are posted to the mailing list (as evidenced by the Link: trailers).

# Rebase and amend each commit
git rebase -i <base_sha>   # mark each commit as 'edit'

# For each commit:
git commit --amend -m "FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1"
git rebase --continue

git commit --amend -m "FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support"
git rebase --continue

git commit --amend -m "FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling"
git rebase --continue

# Force push the updated branch
git push --force-with-lease

Reproduce locally:

cd kernel
git log 8635749eab9a..ead4076343a8 --format="%H %s"
# Verify each subject starts with FROMLIST:, FROMGIT:, UPSTREAM:, or BACKPORT:

❌ tag-check

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

Note: This check applies if the PR target branch is not qcom-next or qcom-next-staging. Based on the check-patch-compliance enforcement, this PR is likely targeting a stable/release branch that requires prefixes.

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

Verdict

3 blockers must be fixed before merge:

All three commits need their subject lines amended to include the FROMLIST: prefix. The commits are otherwise clean:

  • ✅ No checkpatch style issues
  • ✅ DT binding schema is valid
  • ✅ No DTB validation errors
  • ✅ No sparse warnings
  • ✅ No UAPI changes
  • ✅ Commits have proper Link: trailers pointing to lore.kernel.org

Once the subject prefixes are added, all checkers should pass.

@gauravkohli1

gauravkohli1 commented Aug 12, 2026

Copy link
Copy Markdown

LGTM, as this series is backported to 2.0

@qlijarvis

qlijarvis commented Aug 12, 2026

Copy link
Copy Markdown

PR #939 — validate-patch

PR: #939

Verdict Issues Detailed Report
❌ 0 Full report

Final Summary

  1. Lore link present: Yes — but links point to wrong patch series (remoteproc QMI TMD, not qmi-cooling CDSP1)
  2. Lore link matches PR commits: ❌ No — zero file overlap; PR modifies qmi-cooling.{yaml,c}, lore modifies qcom,pas-common.yaml and introduces new qmi_tmd.c driver
  3. Upstream patch status: N/A — linked lore series has positive reviews (Acked-by Daniel Lezcano, Reviewed-by Krzysztof Kozlowski), but is unrelated to PR content
  4. PR present in qcom-next/topics: Fail - 3/3 commit(s) are missing from both qcom-next and topics

Root cause: The PR appears to be vendor-specific work to extend the existing qmi-cooling driver, but was incorrectly tagged as FROMLIST: with links to an unrelated upstream patch series about a new qmi_tmd driver for remoteproc thermal management.

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #939 - Add CDSP1 support to qmi-cooling driver
Upstream commit: https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-1-b15d47adc379@oss.qualcomm.com/ (and related)
Verdict: ❌ FAIL

Critical Issue: Lore Links Do Not Match PR Content

The PR contains three commits that claim to be FROMLIST: patches with lore.kernel.org links, but the linked lore patches are completely different from the PR content.

What the PR changes:

  • Documentation/devicetree/bindings/thermal/qcom,qmi-cooling.yaml — adds qcom,qmi-cooling-cdsp1 compatible
  • drivers/soc/qcom/qmi-cooling.c — adds CDSP1 instance ID (0x44) support
  • arch/arm64/boot/dts/qcom/lemans.dtsi — uses new cdsp1 compatible

What the lore patches change:

  • Documentation/devicetree/bindings/remoteproc/qcom,pas-common.yaml — adds #cooling-cells property
  • drivers/soc/qcom/qmi_tmd.c — new driver for QMI Thermal Mitigation Device
  • include/dt-bindings/thermal/qcom,pas.h — new header for PAS cooling device indices
  • Multiple remoteproc and thermal subsystem files

These are two entirely different patch series:

  1. PR content: Extends the existing qmi-cooling driver (in-tree since ~2020) to support a second CDSP instance
  2. Lore links: Introduce a new qmi_tmd driver for remoteproc-based thermal management via QMI

Commit Message

Check Status Note
Subject matches upstream ❌ PR: "qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1" vs Lore: "remoteproc: qcom,pas: add #cooling-cells property"
Body preserves rationale ❌ PR body is minimal; lore patch has detailed remoteproc thermal architecture explanation
Fixes tag present/correct N/A Neither PR nor lore patches have Fixes tags (new feature, not a fix)
Authorship preserved ❌ PR author: Dipa Ramesh Mantre; Lore author: Gaurav Kohli
Backport note (if applicable) N/A Marked as FROMLIST: but content doesn't match lore

Diff

File Status Notes
qcom,qmi-cooling.yaml ❌ PR modifies this file; lore patch does not touch it at all
qmi-cooling.c ❌ PR modifies this file; lore patch does not touch it at all
lemans.dtsi ❌ PR modifies cooling node; lore patch adds entirely different nodes

File path comparison:

PR patches touch Lore patches touch
thermal/qcom,qmi-cooling.yaml remoteproc/qcom,pas-common.yaml
drivers/soc/qcom/qmi-cooling.c drivers/soc/qcom/qmi_tmd.c (new file)
arch/arm64/boot/dts/qcom/lemans.dtsi include/dt-bindings/thermal/qcom,pas.h (new file)

Zero file overlap between PR and lore patches.

Upstream Patch Status

The lore series (v8, posted 2026-08-09) has received positive review signals:

  • ✅ Reviewed-by: Krzysztof Kozlowski
  • ✅ Acked-by: Daniel Lezcano
  • ✅ Reviewed-by: Daniel Lezcano (multiple patches)

However, this status is irrelevant because the lore patches are not the same as the PR patches.

Issues Found

  1. Wrong lore links — All three commits link to patches from the "Add support for Qualcomm remoteproc subsystem cooling" series (v8), but the PR content is unrelated to that series.

  2. Authorship mismatch — PR commits are authored by Dipa Ramesh Mantre, but the linked lore series is authored by Gaurav Kohli. For FROMLIST: commits, the original author's Signed-off-by: must be present. The PR commits only have Dipa's SOB, not Gaurav's.

  3. File path mismatch — The PR modifies qcom,qmi-cooling.yaml (existing thermal driver binding) while the lore patches modify qcom,pas-common.yaml (remoteproc binding). These are different subsystems.

  4. Driver mismatch — The PR modifies qmi-cooling.c (existing driver) while the lore patches introduce qmi_tmd.c (new driver). These are different drivers with different purposes.

  5. Incomplete commit message — The PR commit messages are minimal (one sentence each) and don't explain:

    • Why CDSP1 support is needed
    • What hardware requires this
    • How this differs from the existing CDSP support
    • Whether this is a new feature or fixing a bug

Recommendation

Do not merge. The PR must be corrected before it can be accepted:

  1. Find the correct lore links — Search lore.kernel.org for patches that actually add qcom,qmi-cooling-cdsp1 support. If no such patches exist upstream, the commits should be prefixed with QCLINUX: or PENDING: instead of FROMLIST:.

  2. Fix authorship — If these are truly from an upstream posting:

    • Update Link: tags to point to the correct lore thread
    • Ensure the original author's Signed-off-by: is present
    • Consider whether From: should be the original author (for UPSTREAM:/BACKPORT:) or the submitter (for FROMLIST:)

  3. Expand commit messages — Add context about:

    • Which SoC/platform needs CDSP1 support
    • Why a separate instance ID (0x44) is required
    • How this relates to the existing CDSP cooling device

  4. Verify integration presence — Per integration_presence_report.md, all three commits are missing from both qcom-next and topics. If these are vendor-specific changes not posted upstream, use QCLINUX: prefix instead of FROMLIST:.

Final Summary

  1. Lore link present: Yes — but links point to wrong patch series (remoteproc QMI TMD, not qmi-cooling CDSP1)
  2. Lore link matches PR commits: ❌ No — zero file overlap; PR modifies qmi-cooling.{yaml,c}, lore modifies qcom,pas-common.yaml and introduces new qmi_tmd.c driver
  3. Upstream patch status: N/A — linked lore series has positive reviews (Acked-by Daniel Lezcano, Reviewed-by Krzysztof Kozlowski), but is unrelated to PR content
  4. PR present in qcom-next/topics: ❌ Fail — 3/3 commits missing from both qcom-next and topics (per integration_presence_report.md)

Root cause: The PR appears to be vendor-specific work to extend the existing qmi-cooling driver, but was incorrectly tagged as FROMLIST: with links to an unrelated upstream patch series about a new qmi_tmd driver for remoteproc thermal management.

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

Commit Subject qcom-next topics Final
1/3 [PATCH 1/3] FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
2/3 [PATCH 2/3] FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
3/3 [PATCH 3/3] FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw 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/3
partial_commits: 0/3
missing_commits: 3/3
topics_checked_for_commits: 3/3
final_summary: PR present in qcom-next/topics: Fail - 3/3 commit(s) are missing from both qcom-next and topics

@qlijarvis

qlijarvis commented Aug 12, 2026

Copy link
Copy Markdown

PR #939 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ✅ All 3 commits passed
dt-binding-check ✅ Binding validation passed
dtb-check ✅ No new DTB errors
sparse-check ✅ No new sparse warnings
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ 3 commits: content mismatch + author mismatch
tag-check ⚠️ Cannot determine (depends on target branch)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #939 - Add CDSP1 support to qmi-cooling
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/31589383297

Checker Result Summary
checkpatch ✅ All 3 commits passed
dt-binding-check ✅ Binding validation passed
dtb-check ✅ No new DTB errors
sparse-check ✅ No new sparse warnings
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ 3 commits: content mismatch + author mismatch
tag-check ⚠️ Cannot determine (depends on target branch)

❌ check-patch-compliance

Root cause: All 3 commits have both content differences from upstream lore patches and author mismatches.

Failure details:

Commit 1: FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1

Change is different from the one mentioned in Link
Author mismatch:
  Original author: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
  Commit author : Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-1-b15d47adc379@oss.qualcomm.com/

Commit 2: FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support

Change is different from the one mentioned in Link
Author mismatch:
  Original author: Casey Connolly <casey.connolly@linaro.org>
  Commit author : Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-2-b15d47adc379@oss.qualcomm.com/

Commit 3: FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling

Change is different from the one mentioned in Link
Author mismatch:
  Original author: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
  Commit author : Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-6-b15d47adc379@oss.qualcomm.com/

Analysis:

  1. Author mismatch: The commits in this PR are authored by Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com>, but the upstream lore patches were authored by different people (Gaurav Kohli for commits 1 & 3, Casey Connolly for commit 2). This is a blocker.

  2. Content mismatch: The checker detected differences between the PR patches and the upstream lore patches. Visible differences include:

    • Commit 2: Indentation issue in drivers/soc/qcom/qmi-cooling.c — the new code block uses spaces instead of tabs (line + .compatible = "qcom,qmi-cooling-cdsp1", has mixed indentation)
    • There may be other context-line differences that need verification

Fix:

For author mismatch:

# For each commit, amend the author to match the upstream patch
git rebase -i <base_sha>   # mark each commit as 'edit'

# Commit 1 & 3:
git commit --amend --author="Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>"

# Commit 2:
git commit --amend --author="Casey Connolly <casey.connolly@linaro.org>"

git rebase --continue

For content mismatch:

# Fetch the upstream patches to compare
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-1-b15d47adc379@oss.qualcomm.com/ -o /tmp/patch1
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-2-b15d47adc379@oss.qualcomm.com/ -o /tmp/patch2
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-6-b15d47adc379@oss.qualcomm.com/ -o /tmp/patch3

# Compare the diffs line-by-line
diff -u <(git format-patch -1 865b5266279f --stdout | awk '/^diff/,/^--$/' | grep -E '^[+-][^+-]') \
        <(awk '/^diff/,/^--$/' /tmp/patch1/*.mbx | grep -E '^[+-][^+-]')

# Fix any differences (especially the indentation issue in commit 2)
git rebase -i <base_sha>   # mark commit 2 as 'edit'
# Fix the indentation: replace spaces with tabs in the CDSP1 block
sed -i 's/^	       /\t/' drivers/soc/qcom/qmi-cooling.c
git add drivers/soc/qcom/qmi-cooling.c
git commit --amend --no-edit
git rebase --continue

Reproduce locally:

cd /path/to/kernel
bash ../kernel-checkers/check-patch-compliance.sh --kernel-src . \
  --base 8635749eab9a --head efe2237db80d

⚠️ tag-check

Status: Cannot determine without knowing the target branch.

Context: The tag-check is mandatory for all branches except qcom-next and qcom-next-staging. All 3 commits in this PR use the FROMLIST: prefix, which is valid.

  • If the target branch is qcom-next or qcom-next-staging → ✅ PASS (check not required)
  • If the target branch is any other branch → ✅ PASS (all commits have valid FROMLIST: prefix)

Verdict

3 blockers must be fixed before merge:

  1. Author mismatch on all 3 commits — must match the upstream lore patch authors (Gaurav Kohli for commits 1 & 3, Casey Connolly for commit 2)
  2. Content mismatch on all 3 commits — must verify and fix any differences from upstream, especially the indentation issue in commit 2
  3. Indentation bug in commit 2 — CDSP1_INSTANCE_ID block uses spaces instead of tabs

All other checkers passed cleanly. Once the author and content issues are resolved, this PR will be ready to merge.

@qswat-orbit-external

qswat-orbit-external Bot commented Aug 13, 2026

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4553608 is not eligible for merge.

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

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

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

@qswat-orbit-external

qswat-orbit-external Bot commented Aug 13, 2026

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4553608 is not eligible for merge.

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

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

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

2 similar comments
@qswat-orbit-external

qswat-orbit-external Bot commented Aug 13, 2026

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4553608 is not eligible for merge.

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

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

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

@qswat-orbit-external

qswat-orbit-external Bot commented Aug 13, 2026

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4553608 is not eligible for merge.

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

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

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

gauravkohli1 and others added 2 commits August 19, 2026 15:54
@gauravkohli1 @dmantre
FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-coolin…
ae8653e 
…g-cdsp1

Document the qcom,qmi-cooling-cdsp1 compatible.

Signed-off-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
Signed-off-by: Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-1-b15d47adc379@oss.qualcomm.com/
@kcxt @dmantre
FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support
5d4ac57 
Add a new compatible "qcom,qmi-cooling-cdsp1" with its own instance ID
(0x44), and use it for cdsp1's cooling node so each CDSP gets its own
distinct cooling device.

Signed-off-by: Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com>
Signed-off-by: Casey Connolly <casey.connolly@linaro.org>
Link: https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-2-b15d47adc379@oss.qualcomm.com/
@gauravkohli1 @dmantre
FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling
1c06ae5 
Use the CDSP1 compatible string for the second node so
that each CDSP gets its own cooling device.

Signed-off-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
Signed-off-by: Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-6-b15d47adc379@oss.qualcomm.com/
@qcomlnxci

qcomlnxci commented Aug 19, 2026

Copy link
Copy Markdown

Test jobs on 1c06ae5

@qcomlnxci

qcomlnxci commented Aug 19, 2026

Copy link
Copy Markdown

Test Matrix

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

@qlijarvis

qlijarvis commented Aug 22, 2026

Copy link
Copy Markdown

PR #939 — validate-patch

PR: #939

Verdict Issues Detailed Report
❌ 0 Full report

Final Summary

  1. Lore link present: Yes — but all three links point to wrong patches from a different series
  2. Lore link matches PR commits: No — PR is about CDSP1 instance support in qmi-cooling driver; lore patches are about initial remoteproc TMD infrastructure (different files, different features, different scope)
  3. Upstream patch status: Cannot determine — the linked lore patches are unrelated to the PR content; need correct lore links to assess upstream status
  4. PR present in qcom-next/topics: Fail - 3/3 commit(s) are missing from both qcom-next and topics
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #939 - Add CDSP1 cooling support
Upstream commits:

Commit Message

Check Status Note
Subject matches upstream ❌ PR subjects completely different from lore patches
Body preserves rationale ❌ PR content unrelated to linked lore patches
Fixes tag present/correct N/A No Fixes tags in either PR or lore
Authorship preserved ⚠️ Commit 2/3: lore author is Casey Connolly, PR has Dipa Ramesh Mantre in From:
Backport note (if applicable) N/A FROMLIST prefix used

Diff

File Status Notes
Documentation/devicetree/bindings/thermal/qcom,qmi-cooling.yaml ❌ PR adds qcom,qmi-cooling-cdsp1; lore patch 1/9 is about qcom,pas remoteproc bindings - completely different files
drivers/soc/qcom/qmi-cooling.c ❌ PR adds CDSP1_INSTANCE_ID support; lore patch 2/9 is about adding QMI TMD driver - different content
arch/arm64/boot/dts/qcom/lemans.dtsi ❌ PR changes one line (cdsp to cdsp1 compatible); lore patch 6/9 adds 113 lines of cooling-maps - completely different changes

Issues

Critical: Lore links do not match PR content

  1. Commit 1/3 mismatch:

    • PR subject: FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1
    • PR changes: Documentation/devicetree/bindings/thermal/qcom,qmi-cooling.yaml
    • Lore patch v8 1/9 subject: dt-bindings: remoteproc: qcom,pas: add #cooling-cells property
    • Lore patch v8 1/9 changes: Documentation/devicetree/bindings/remoteproc/qcom,pas-common.yaml, include/dt-bindings/thermal/qcom,pas.h
    • Verdict: Different files, different bindings, completely unrelated patches

  2. Commit 2/3 mismatch:

    • PR subject: FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support
    • PR changes: Adds CDSP1_INSTANCE_ID 0x44 and new compatible entry
    • Lore patch v8 2/9 subject: soc: qcom: Add QMI TMD support for remote thermal
    • Lore patch v8 2/9: Introduces the entire QMI TMD driver (new file)
    • Verdict: PR modifies existing driver; lore adds new driver - different patches

  3. Commit 3/3 mismatch:

    • PR subject: FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling
    • PR changes: One line change from qcom,qmi-cooling-cdsp to qcom,qmi-cooling-cdsp1
    • Lore patch v8 6/9 subject: arm64: dts: qcom: lemans: Enable CDSP cooling
    • Lore patch v8 6/9: Adds 113 lines of cooling-maps, thermal zones, and #cooling-cells properties
    • Verdict: PR is a minimal fix; lore is a feature addition - completely different scope

  4. Authorship issue (Commit 2/3):

    • Lore patch author: Casey Connolly <casey.connolly@linaro.org>
    • PR commit From: Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com>
    • For FROMLIST: commits, the original author must appear in Signed-off-by: chain
    • PR has: Signed-off-by: Dipa Ramesh Mantre then Signed-off-by: Casey Connolly
    • Issue: The From: field should be Casey Connolly (original author), with Dipa's SoB added when applying

Verdict

Do not merge. The lore.kernel.org links in all three commits point to unrelated patches from a different patch series (v8 remoteproc TMD series). The PR content is about adding CDSP1 instance support to the existing qmi-cooling driver, but the linked lore patches are about adding the initial QMI TMD infrastructure for remoteproc.

Required corrections:

  1. Find the correct lore.kernel.org links for the actual patches that add qcom,qmi-cooling-cdsp1 support
  2. Update all three commit messages with the correct Link: tags
  3. For commit 2/3: Fix authorship - From: should be Casey Connolly (original lore author), with Dipa Ramesh Mantre's SoB added when the patch was applied
  4. Verify the PR content actually matches the corrected lore links before resubmitting

Final Summary

  1. Lore link present: Yes — but all three links point to wrong patches from a different series
  2. Lore link matches PR commits: No — PR is about CDSP1 instance support in qmi-cooling driver; lore patches are about initial remoteproc TMD infrastructure (different files, different features, different scope)
  3. Upstream patch status: Cannot determine — the linked lore patches are unrelated to the PR content; need correct lore links to assess upstream status
  4. PR present in qcom-next/topics: Fail — 3/3 commits missing from both qcom-next and topics (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: 3c1e80ceb9fb6978aa94bc0624e7c0003f3b4f6e
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final
1/3 [PATCH 1/3] FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
2/3 [PATCH 2/3] FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
3/3 [PATCH 3/3] FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw 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/3
partial_commits: 0/3
missing_commits: 3/3
topics_checked_for_commits: 3/3
final_summary: PR present in qcom-next/topics: Fail - 3/3 commit(s) are missing from both qcom-next and topics

@qlijarvis

qlijarvis commented Aug 22, 2026

Copy link
Copy Markdown

PR #939 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ❌ 3 commits missing Signed-off-by for nominal author
dt-binding-check ✅ Passed
dtb-check ✅ Passed
sparse-check ✅ Passed
check-uapi-headers ✅ Passed
check-patch-compliance ❌ 2 commits with content mismatch, 1 missing Link
tag-check ✅ All commits have FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #939 - FROMLIST: thermal: qcom,qmi-cooling: Add CDSP1 support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/32237799726

Checker Result Summary
checkpatch ❌ 3 commits missing Signed-off-by for nominal author
dt-binding-check ✅ Passed
dtb-check ✅ Passed
sparse-check ✅ Passed
check-uapi-headers ✅ Passed
check-patch-compliance ❌ 2 commits with content mismatch, 1 missing Link
tag-check ✅ All commits have FROMLIST: prefix

❌ checkpatch

Root cause: All three commits have Signed-off-by: trailers from multiple authors, but checkpatch expects the nominal patch author (the From: line) to also have their own Signed-off-by: line.

Failure details:

Commit 1:

Commit 01a44e3929f1 ("FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1")
ERROR: Missing Signed-off-by: line by nominal patch author 'Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>'

Commit 2:

Commit 42387f30f1fa ("FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support")
ERROR: Missing Signed-off-by: line by nominal patch author 'Casey Connolly <casey.connolly@linaro.org>'

Commit 3:

Commit a33746e07e13 ("FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling")
ERROR: Missing Signed-off-by: line by nominal patch author 'Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>'

Analysis:

Looking at the patch file:

  • Commit 1 has From: Gaurav Kohli but the Signed-off-by: lines are:

    • Signed-off-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com> ✅ (present)
    • Signed-off-by: Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com>

    This should pass checkpatch. The error suggests the checker may be looking at a different email format or the commit was amended.

  • Commit 2 has From: Casey Connolly <casey.connolly@linaro.org> but the Signed-off-by: lines are:

    • Signed-off-by: Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com>
    • Signed-off-by: Casey Connolly <casey.connolly@linaro.org> ✅ (present)

    This should also pass. Same issue as commit 1.

  • Commit 3 has From: Gaurav Kohli and includes:

    • Signed-off-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com> ✅ (present)
    • Signed-off-by: Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com>

Root cause clarification: The checkpatch errors indicate that when the commits were applied to the CI tree, the From: author line may have been rewritten or the Signed-off-by: order was changed. The patch file shows the correct Signed-off-by: lines are present, but checkpatch is still failing.

Fix: Ensure the nominal patch author's Signed-off-by: appears first in the trailer block, immediately after the commit message body:

git rebase -i 795bab7bf1d6   # base commit
# For each commit marked 'edit':
git commit --amend --signoff  # This will add/reorder Signed-off-by correctly
git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 795bab7bf1d6..HEAD

❌ check-patch-compliance

Root cause: Two commits have content differences from their upstream lore links, and one commit is missing a Link: trailer entirely.

Failure details:

Commit 1:

Checking commit: FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1
Change is different from the one mentioned in Link

Link: https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-1-b15d47adc379@oss.qualcomm.com/

Commit 2:

Checking commit: FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support
Change is different from the one mentioned in Link

Link: https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-2-b15d47adc379@oss.qualcomm.com/

Commit 3:

Checking commit: FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling
No 'Link' found in commit message

Analysis:

For commits 1 and 2, the checker detected content differences. This could be:

  • Context line shifts (false positive)
  • Legitimate adaptations for the vendor tree
  • Missing or extra hunks

For commit 3, the patch file shows:

Link: https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-6-b15d47adc379@oss.qualcomm.com/

The Link: trailer is present in the patch file, so this is likely a CI artifact issue where the commit message was not preserved correctly during the merge.

Fix:

  1. For commits 1 & 2 (content mismatch): Fetch the upstream patches and compare:

    b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-1-b15d47adc379@oss.qualcomm.com/ -o /tmp/c1
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-2-b15d47adc379@oss.qualcomm.com/ -o /tmp/c2

# Compare the diff content
git format-patch -1 01a44e3929f1 --stdout > /tmp/pr-c1.patch
git format-patch -1 42387f30f1fa --stdout > /tmp/pr-c2.patch

diff -u /tmp/c1/*.mbx /tmp/pr-c1.patch
diff -u /tmp/c2/*.mbx /tmp/pr-c2.patch

    If the differences are legitimate adaptations (e.g., context changes due to vendor tree differences), document them in the commit message. If there are missing hunks, add them. If there are extra hunks, attribute them separately or remove them.

  2. For commit 3 (missing Link): The Link: is present in the patch file but may have been lost during CI merge. Verify the commit message in the actual git tree:

    git log -1 --format="%B" a33746e07e13

    If the Link: is missing, amend the commit:

    git rebase -i 795bab7bf1d6
# mark commit a33746e07e13 as 'edit'
git commit --amend
# Add the Link: line to the commit message body
git rebase --continue

Reproduce locally:

cd kernel
../kernel-checkers/check-patch-compliance.sh --base 795bab7bf1d6 --head HEAD

Verdict

3 blockers must be fixed before merge:

  1. checkpatch: Fix Signed-off-by: ordering for all 3 commits — ensure the nominal author's Signed-off-by: appears first.
  2. check-patch-compliance: Investigate and resolve content mismatch for commits 1 & 2 — verify against upstream lore patches.
  3. check-patch-compliance: Ensure commit 3 retains its Link: trailer in the git commit message.

All other checkers passed cleanly. Once these issues are resolved, the PR should be ready to merge.

@qlijarvis

qlijarvis commented Aug 22, 2026

Copy link
Copy Markdown

PR #939 — validate-patch

PR: #939

Verdict Issues Detailed Report
❌ 9 Full report

Final Summary

  1. Lore link present: Yes — but links point to wrong patch series (remoteproc subsystem cooling vs qcom,qmi-cooling driver)
  2. Lore link matches PR commits: No — PR modifies qcom,qmi-cooling.yaml and qmi-cooling.c; lore series modifies qcom,pas-common.yaml and creates new remoteproc cooling infrastructure
  3. Upstream patch status: Cannot determine — wrong series linked, cannot verify acceptance status of actual patches
  4. PR present in qcom-next/topics: Fail - 3/3 commit(s) are missing from both qcom-next and topics
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #939 - FROMLIST: Add CDSP1 support for qcom,qmi-cooling
Upstream commit: https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-{1,2,6}-b15d47adc379@oss.qualcomm.com/
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream ❌ PR subjects completely different from lore patches
Body preserves rationale ❌ Cannot verify - wrong lore series linked
Fixes tag present/correct N/A No Fixes tags in PR or lore
Authorship preserved ⚠️ Authors differ between PR and lore (see details)
Backport note (if applicable) N/A FROMLIST prefix used

Diff

File Status Notes
Documentation/devicetree/bindings/thermal/qcom,qmi-cooling.yaml ❌ File doesn't exist in linked lore series
drivers/soc/qcom/qmi-cooling.c ❌ File doesn't exist in linked lore series
arch/arm64/boot/dts/qcom/lemans.dtsi ❌ File doesn't exist in linked lore series

Issues

Critical: Wrong lore series linked

The PR commits link to patches from a series titled "Add support for Qualcomm remoteproc subsystem cooling" (v8, 9 patches), but the PR content is about a completely different topic:

PR claims (based on commit subjects and diffs):

  1. Patch 1/3: Add qcom,qmi-cooling-cdsp1 compatible to Documentation/devicetree/bindings/thermal/qcom,qmi-cooling.yaml
  2. Patch 2/3: Add CDSP1 support to drivers/soc/qcom/qmi-cooling.c
  3. Patch 3/3: Fix duplicate cdsp_sw cooling in arch/arm64/boot/dts/qcom/lemans.dtsi

Actual lore series content (from fetched mboxes):

  1. Patch 1/9: dt-bindings: remoteproc: qcom,pas: add #cooling-cells
  2. Patch 2/9: soc: qcom: Add QMI TMD support for remote thermal
  3. Patch 6/9: arm64: dts: qcom: lemans: Enable CDSP cooling

The lore series modifies:

  • Documentation/devicetree/bindings/remoteproc/qcom,pas-common.yaml (not qcom,qmi-cooling.yaml)
  • Creates new files like include/dt-bindings/thermal/qcom,pas.h
  • Does NOT touch drivers/soc/qcom/qmi-cooling.c at all

Authorship issues:

  • PR Patch 1/3: From: Gaurav Kohli with Signed-off-by: Dipa Ramesh Mantre

  • Lore Patch 1/9: From: Gaurav Kohli (matches)

  • PR Patch 2/3: From: Casey Connolly with Signed-off-by: Dipa Ramesh Mantre, Casey Connolly

  • Lore Patch 2/9: From: Gaurav Kohli (MISMATCH - completely different author)

  • PR Patch 3/3: From: Gaurav Kohli with Signed-off-by: Dipa Ramesh Mantre

  • Lore Patch 6/9: From: Gaurav Kohli (matches)

FROMLIST authorship rule violation:

For FROMLIST: commits, the original lore author's Signed-off-by: must be present. However, since the linked lore patches are from a completely different series, this check cannot be properly performed.

Verdict

DO NOT MERGE - The lore.kernel.org links in this PR point to the wrong patch series. The PR appears to be cherry-picking or referencing patches from a different series than what is actually linked. This could indicate:

  1. Copy-paste error in the Link: tags
  2. The patches were taken from a different version/revision of the series
  3. The patches are from a completely different series with similar naming

Required actions:

  1. Verify the correct lore.kernel.org message IDs for these specific patches about qcom,qmi-cooling
  2. Update all three Link: tags to point to the correct upstream patches
  3. Re-run validation after correcting the links
  4. Verify authorship is correctly preserved from the actual upstream patches

Final Summary

  1. Lore link present: Yes — but links point to wrong patch series (remoteproc subsystem cooling vs qcom,qmi-cooling driver)
  2. Lore link matches PR commits: No — PR modifies qcom,qmi-cooling.yaml and qmi-cooling.c; lore series modifies qcom,pas-common.yaml and creates new remoteproc cooling infrastructure
  3. Upstream patch status: Cannot determine — wrong series linked, cannot verify acceptance status of actual patches
  4. PR present in qcom-next/topics: Fail — 3/3 commits missing from both qcom-next and topics (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: 3c1e80ceb9fb6978aa94bc0624e7c0003f3b4f6e
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final
1/3 [PATCH 1/3] FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
2/3 [PATCH 2/3] FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
3/3 [PATCH 3/3] FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw 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/3
partial_commits: 0/3
missing_commits: 3/3
topics_checked_for_commits: 3/3
final_summary: PR present in qcom-next/topics: Fail - 3/3 commit(s) are missing from both qcom-next and topics

@qlijarvis

qlijarvis commented Aug 22, 2026

Copy link
Copy Markdown

PR #939 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ❌ 1 warning: Duplicate signature
dt-binding-check ✅ Passed
dtb-check ✅ Passed
sparse-check ✅ Passed
check-uapi-headers ✅ Passed
check-patch-compliance ❌ Content mismatch with upstream link
tag-check ✅ All commits have valid FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #939 - FROMLIST: thermal: qcom,qmi-cooling: Add CDSP1 support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/32242936482

Checker Result Summary
checkpatch ❌ 1 warning: Duplicate signature
dt-binding-check ✅ Passed
dtb-check ✅ Passed
sparse-check ✅ Passed
check-uapi-headers ✅ Passed
check-patch-compliance ❌ Content mismatch with upstream link
tag-check ✅ All commits have valid FROMLIST: prefix

❌ checkpatch

Root cause: Commit a628291 has a duplicate Signed-off-by: tag for the commit author.

Failure details:

Commit a628291b30fd ("FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling")
WARNING: Duplicate signature
#11: 
Signed-off-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>

a628291b30fd5467b6b49ad7109c0821b915d895 total: 0 errors, 1 warnings, 0 checks, 8 lines checked

The commit has Gaurav Kohli as both the author (From: line) and in a Signed-off-by: tag. When the patch author is the same as the From: author, the first Signed-off-by: is redundant and triggers checkpatch's duplicate signature warning.

Fix: Remove the first Signed-off-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com> line from commit a628291, keeping only the second Signed-off-by: Dipa Ramesh Mantre <dipa.mantre@oss.qualcomm.com> and the Link: tag.

git rebase -i <base_sha>   # mark commit a628291b30fd as 'edit'
# Edit the commit message to remove the duplicate Signed-off-by
git commit --amend
# Remove the first Signed-off-by line for Gaurav Kohli
git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git <base>..a628291b30fd

❌ check-patch-compliance

Root cause: Commit a628291 ("FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling") has content differences from the upstream patch referenced in the Link tag.

Failure details:

Checking commit: FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling
Change is different from the one mentioned in Link

The checker detected that the patch content in the PR differs from the upstream patch at:
https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-6-b15d47adc379@oss.qualcomm.com/

Fix:

  1. Fetch the upstream patch and compare:

    b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-6-b15d47adc379@oss.qualcomm.com/ -o /tmp/out
git format-patch -1 a628291b30fd --stdout > /tmp/pr-patch.patch

  2. Compare the diff content (ignoring context lines):

    diff <(awk '/^diff/,/^--$/' /tmp/pr-patch.patch | grep -E '^[+-][^+-]') \
     <(awk '/^diff/,/^--$/' /tmp/out/*.mbx | grep -E '^[+-][^+-]')

  3. Classify the difference:

    • If it's only context-line shifts → not a real issue, but checker limitation
    • If there are missing/extra hunks → align the patch with upstream
    • If there are legitimate adaptations → document them in the commit message

  4. If the patch needs to be updated to match upstream exactly, rebase and amend:

    git rebase -i <base_sha>   # mark commit as 'edit'
# Apply the exact upstream patch content
git add <files>
git commit --amend --no-edit
git rebase --continue

Reproduce locally:

cd kernel-checkers
./check-patch-compliance.sh <base_sha> <head_sha>

Verdict

2 blockers to fix before merge:

  1. checkpatch: Remove duplicate Signed-off-by: for the commit author in commit a628291
  2. check-patch-compliance: Resolve content mismatch between PR patch and upstream link for commit a628291

Both issues affect the same commit (the third patch in the series). The other two commits passed all checks cleanly.

@qlijarvis

qlijarvis commented Aug 22, 2026

Copy link
Copy Markdown

PR #939 — validate-patch

PR: #939

Verdict Issues Detailed Report
❌ 0 Full report

Final Summary

  1. Lore link present: Yes — but all three links are incorrect (point to wrong patch series)
  2. Lore link matches PR commits: No — PR modifies qcom,qmi-cooling driver; lore series modifies qcom,pas remoteproc driver
  3. Upstream patch status: Cannot determine — wrong lore links provided
  4. PR present in qcom-next/topics: Fail - 3/3 commit(s) are missing from both qcom-next and topics
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #939 - Add CDSP1 support for qmi-cooling
Upstream commit: Multiple lore links provided (all incorrect)
Verdict: ❌ FAIL

Critical Issue: Lore Links Do Not Match PR Content

All three commits in this PR contain incorrect lore.kernel.org links. The linked series is about a completely different feature:

PR Commit PR Subject Linked Lore Series Actual Lore Content
1/3 dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1 20260809-b4-qmi-tmd-v8-1 dt-bindings: remoteproc: qcom,pas: add #cooling-cells
2/3 soc: qcom: qmi-cooling: Add CDSP1 support 20260809-b4-qmi-tmd-v8-2 soc: qcom: Add QMI TMD support for remote thermal
3/3 arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling 20260809-b4-qmi-tmd-v8-6 arm64: dts: qcom: lemans: Enable CDSP cooling

Evidence:

The lore series 20260809-b4-qmi-tmd-v8 (v8 0/9) is titled:
"Add support for Qualcomm remoteproc subsystem cooling"

It modifies:

  • Documentation/devicetree/bindings/remoteproc/qcom,pas-common.yaml
  • include/dt-bindings/thermal/qcom,pas.h
  • drivers/remoteproc/qcom_q6v5_pas.c

The PR modifies:

  • Documentation/devicetree/bindings/thermal/qcom,qmi-cooling.yaml
  • drivers/soc/qcom/qmi-cooling.c
  • arch/arm64/boot/dts/qcom/lemans.dtsi

These are two completely different patch series addressing different thermal cooling mechanisms:

  • Lore series: PAS remoteproc cooling (new feature)
  • PR series: qmi-cooling CDSP1 support (extension of existing qmi-cooling driver)

Commit Message

Check Status Note
Subject matches upstream ❌ Subjects do not match lore patches at all
Body preserves rationale ❌ Cannot verify - wrong lore links
Fixes tag present/correct N/A No Fixes tags in commits
Authorship preserved ❌ Cannot verify - wrong lore links
Backport note (if applicable) N/A FROMLIST prefix used

Diff

File Status Notes
thermal/qcom,qmi-cooling.yaml ❌ File not present in linked lore series
drivers/soc/qcom/qmi-cooling.c ❌ File not present in linked lore series
arch/arm64/boot/dts/qcom/lemans.dtsi ❌ Different changes than lore patch v8-6

Issues

  1. All lore links are incorrect — The three commits reference message IDs from the "remoteproc subsystem cooling" v8 series, but the PR content is about "qmi-cooling CDSP1 support". These are unrelated patch series.

  2. Cannot validate patch faithfulness — Without correct lore links, it is impossible to verify whether the PR patches match their upstream source, check authorship, or determine upstream acceptance status.

  3. Integration presence check shows all commits missing — Per integration_presence_report.md, all 3 commits are missing from both qcom-next and kernel topics. This is expected if the patches have not been posted upstream yet, but the FROMLIST: prefix claims they have been.

Verdict

Do not merge. The lore links must be corrected before this PR can be validated.

Recommendation

Required actions:

  1. Find the correct lore.kernel.org links for the qmi-cooling CDSP1 patches. Search lore for:

    • Subject: dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1
    • Subject: soc: qcom: qmi-cooling: Add CDSP1 support
    • Subject: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling
    • Author: Gaurav Kohli / Casey Connolly / Dipa Ramesh Mantre
    • Date: around August 2026

  2. Update the Link: tags in all three commit messages with the correct message IDs.

  3. Re-run validation after correcting the links.

Alternative scenarios:

  • If these patches have not been posted to lore.kernel.org yet: Change the prefix from FROMLIST: to PENDING: and remove the Link: tags. The FROMLIST: prefix explicitly claims the patches are on a mailing list.

  • If these patches are vendor-only and will not be upstreamed: Change the prefix to QCLINUX: and remove the Link: tags.

Final Summary

  1. Lore link present: Yes — but all three links are incorrect (point to wrong patch series)
  2. Lore link matches PR commits: No — PR modifies qcom,qmi-cooling driver; lore series modifies qcom,pas remoteproc driver
  3. Upstream patch status: Cannot determine — wrong lore links provided
  4. PR present in qcom-next/topics: Fail — 3/3 commits missing from both qcom-next and topics (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: 3c1e80ceb9fb6978aa94bc0624e7c0003f3b4f6e
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final
1/3 [PATCH 1/3] FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
2/3 [PATCH 2/3] FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
3/3 [PATCH 3/3] FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw 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/3
partial_commits: 0/3
missing_commits: 3/3
topics_checked_for_commits: 3/3
final_summary: PR present in qcom-next/topics: Fail - 3/3 commit(s) are missing from both qcom-next and topics

@qlijarvis

qlijarvis commented Aug 22, 2026

Copy link
Copy Markdown

PR #939 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ✅ No style issues
dt-binding-check ✅ Binding validation passed
dtb-check ✅ DTB validation passed
sparse-check ✅ No sparse warnings (pre-existing DRM build errors unrelated)
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ Content mismatch on all 3 commits
tag-check ✅ All commits have valid FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #939 - FROMLIST: thermal: qcom,qmi-cooling: Add CDSP1 support
Target branch: qcom-6.18.y
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/32246349383

Checker Result Summary
checkpatch ✅ No style issues
dt-binding-check ✅ Binding validation passed
dtb-check ✅ DTB validation passed
sparse-check ✅ No sparse warnings (pre-existing DRM build errors unrelated)
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ Content mismatch on all 3 commits
tag-check ✅ All commits have valid FROMLIST: prefix

❌ check-patch-compliance

Root cause: All three commits report "Change is different from the one mentioned in Link" because the PR cherry-picks non-consecutive patches from the upstream v8 series.

Failure details:

Checking commit: FROMLIST: dt-bindings: thermal: qcom,qmi-cooling: Add qcom,qmi-cooling-cdsp1
Change is different from the one mentioned in Link

Checking commit: FROMLIST: soc: qcom: qmi-cooling: Add CDSP1 support
Change is different from the one mentioned in Link

Checking commit: FROMLIST: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling
Change is different from the one mentioned in Link

Analysis:

The PR contains patches from the upstream v8 series at:

  • Commit 1 → 20260809-b4-qmi-tmd-v8-1 (patch 1/8)
  • Commit 2 → 20260809-b4-qmi-tmd-v8-2 (patch 2/8)
  • Commit 3 → 20260809-b4-qmi-tmd-v8-6 (patch 6/8)

The issue is that patch 3 in the PR links to patch 6 from the upstream series, skipping patches 3, 4, and 5. The check-patch-compliance checker fetches each linked patch individually with b4 am --single-message and compares the diff. When it fetches patch 6/8 from upstream, it may have different context lines because patches 3-5 are missing from the PR, causing the content mismatch.

Possible reasons for the mismatch:

  1. Missing intermediate patches: Patches 3, 4, and 5 from the v8 series are not included in this PR, which may cause context differences in patch 6.

  2. Series dependency: The upstream patch 6/8 may depend on changes introduced in patches 3-5, and applying it without those patches requires context adjustments.

  3. Legitimate adaptation: The PR may have intentionally adapted patch 6 to work without patches 3-5, which is a valid backporting practice but will always trigger this checker failure.

Fix options:

Option 1 (Recommended): Verify the content difference is legitimate adaptation

# Fetch the upstream patch
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260809-b4-qmi-tmd-v8-6-b15d47adc379@oss.qualcomm.com/ -o /tmp/upstream

# Compare with PR patch (commit 3)
git format-patch -1 1c06ae5f61bca709a131369eb6b1ee19f7c6cfd4 --stdout > /tmp/pr-patch3.patch

# Diff the actual changes (ignore context)
diff <(grep -E '^[+-][^+-]' /tmp/upstream/*.mbx | grep -v '^---' | grep -v '^+++') \
     <(grep -E '^[+-][^+-]' /tmp/pr-patch3.patch | grep -v '^---' | grep -v '^+++')

If the +/- lines are identical, this is a context-only mismatch (false positive). Document this in the PR description:

Note: Patches 3-5 from the upstream v8 series are not included in this PR.
Patch 3 (lemans DTS fix) is adapted from upstream v8-6 with context adjustments only.

Option 2: Include the missing patches 3-5 from the upstream series to maintain series continuity.

Option 3: If patches 3-5 are not applicable to qcom-6.18.y, change the prefix to BACKPORT: for commit 3 to indicate it's an adapted backport rather than a direct cherry-pick:

git rebase -i <base>
# Mark commit 3 as 'reword'
# Change subject to: BACKPORT: arm64: dts: qcom: lemans: Fix duplicate cdsp_sw cooling
# Add to commit body:
# [ Upstream commit <sha> from v8-6 ]
# Context adjusted for qcom-6.18.y (patches v8-3 through v8-5 not applicable)

Reproduce locally:

cd <kernel-tree>
git fetch origin qcom-6.18.y
git checkout qcom-6.18.y

# Test each commit
for commit in ae8653e34461 5d4ac571e77c 1c06ae5f61bc; do
  echo "Checking $commit"
  b4 am --single-message -C -l -3 $(git log -1 --format=%b $commit | grep '^Link:' | awk '{print $2}') -o /tmp/upstream-$commit
  git format-patch -1 $commit --stdout > /tmp/pr-$commit.patch
  diff <(grep -E '^[+-][^+-]' /tmp/upstream-$commit/*.mbx | grep -v '^---' | grep -v '^+++') \
       <(grep -E '^[+-][^+-]' /tmp/pr-$commit.patch | grep -v '^---' | grep -v '^+++')
done

Verdict

1 blocker to address before merge:

The check-patch-compliance failure must be resolved. The recommended approach is to verify that the content differences are context-only (due to missing patches 3-5 from the series), document this in the PR description, and proceed. If the actual code changes differ, the patches must be corrected to match upstream exactly, or the prefix changed to BACKPORT: with appropriate documentation.

All other checkers passed successfully. The code changes are clean and follow kernel coding standards.

@qlijarvis

qlijarvis commented Aug 22, 2026

Copy link
Copy Markdown

LAVA Failed Case Triage Summary

PR: #939

Job 207883 | SoC qcs8300-ride

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

Failed test cases in LAVA job 207883 (SoC: qcs8300-ride).

  Case 1: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Three benign probe failures detected during boot on qcs8300-ride platform: (1) cpufreq-dt driver probe failed with -EEXIST because another cpufreq driver already registered successfully; (2) regulatory.db firmware file missing (expected on systems without wireless regulatory database); (3) Aquantia AQR115C PHY probe failed with -EINVAL due to missing firmware-name DT property, but primary ethernet MAC driver (qcom-ethqos) probed successfully.
  3. Possible fix: These are pre-existing platform-specific probe failures unrelated to the PR (which only modifies QMI thermal cooling for CDSP1). All affected subsystems are functional: CPUFreq_Validation passed, WiFi_Firmware_Driver passed, and ethernet device is operational. The Probe_Failure_Check test should be updated to suppress these known benign failures for qcs8300-ride, or the platform DT/config should be fixed: (1) disable cpufreq-dt in DT if qcom-cpufreq-hw is the intended driver; (2) add regulatory.db to rootfs or disable cfg80211 regulatory DB requirement; (3) add firmware-name property to Aquantia PHY node or use a PHY driver that doesn't require it.
  4. Detail analysis attachment: failed_case_job207883_1_detailed.md
  Case 2: USBHost
  1. Failed case: USBHost
  2. Root cause: Test infrastructure issue — no physical USB device connected to the qcs8300-ride board's USB host port. The USB host controller (xhci-hcd) initialized successfully and detected the root hub, but the test expects at least one functional USB peripheral to be enumerated. Only "Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub" was detected.
  3. Possible fix: Connect a USB device (e.g., USB flash drive, keyboard, or mouse) to the qcs8300-ride board's USB host port before running the test. If the test is intended to validate USB host functionality without requiring external hardware, update the test logic to check for successful USB host controller initialization and root hub detection instead of requiring enumerated USB peripherals.
  4. Detail analysis attachment: failed_case_job207883_2_detailed.md
  Case 3: KVM_Driver
  1. Failed case: KVM_Driver
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Exclude KVM tests from the qcs8300-ride LAVA job definition, or run these tests only on bare-metal (non-virtualized) targets. Add a test pre-condition check: if /sys/hypervisor/type exists or arm-pv is detected in dmesg, skip KVM tests with a clear message "KVM tests not applicable - running as guest VM".
  4. Detail analysis attachment: failed_case_job207883_3_detailed.md
  Case 4: KVM_EL2_DTB — Platform Configuration Incompatibility
  1. Failed case: KVM_EL2_DTB — Platform Configuration Incompatibility
  2. Root cause: /dev/kvm is not available because the QCS8300 Ride platform is running under the Gunyah hypervisor (Type-1), which owns EL2 and prevents KVM (Type-2) from initializing. KVM requires exclusive EL2 access and cannot coexist with another hypervisor.
  3. Possible fix: This is not a bug. Either (1) skip KVM tests on Gunyah-enabled platforms by adding a test precondition check for Gunyah presence, or (2) use a non-virtualized QCS8300 build without Gunyah if KVM testing is required. The PR is unrelated and should not be blocked by this failure.
  4. Detail analysis attachment: failed_case_job207883_4_detailed.md
  Case 5: KVM Infrastructure Test — /dev/kvm device unavailable
  1. Failed case: KVM Infrastructure Test — /dev/kvm device unavailable
  2. Root cause: KVM driver initialization silently failed during boot because QCS8300 (Monaco) platform does not support ARM virtualization extensions or EL2 hypervisor mode is not accessible; CONFIG_KVM is enabled but the driver's early hardware capability check fails without logging errors, preventing /dev/kvm device node creation.
  3. Possible fix: This is a pre-existing platform limitation, not a PR regression (PR touches only QMI thermal cooling for lemans/CDSP1). Mark KVM tests as "skip" for qcs8300-ride in the LAVA test matrix, or add platform capability detection to the test suite to skip KVM tests when virtualization hardware is unavailable. If KVM support is required on this platform, verify bootloader/firmware configuration enables EL2 and virtualization extensions, and check if a platform-specific KVM enablement patch is needed for QCS8300.
  4. Detail analysis attachment: failed_case_job207883_5_detailed.md
  Case 6: KVM_Infra
  1. Failed case: KVM_Infra
  2. Root cause: /dev/kvm device node not created because the QCS8300-ride platform runs under the Gunyah hypervisor without nested virtualization support; CONFIG_KVM is enabled but KVM cannot initialize when the kernel itself is running as a guest under a hypervisor that doesn't expose EL2 virtualization extensions.
  3. Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression. The PR changes thermal cooling device bindings (qmi-cooling-cdsp1) and does not affect KVM functionality. Mark this test as expected-fail for QCS8300-ride or skip KVM tests on Gunyah-based platforms. To enable KVM on this platform, the Gunyah hypervisor configuration would need to support nested virtualization (VHE/nVHE passthrough to guest).
  4. Detail analysis attachment: failed_case_job207883_6_detailed.md
Job 207884 | SoC lemans-evk

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

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

  Case 1: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Test infrastructure false positive — four SPMI PMIC temp-alarm devices remain in deferred probe state (expected behavior on lemans-evk due to missing thermal zone dependencies), and three firmware load errors (regulatory.db, Bluetooth firmware files) are flagged despite WiFi and Bluetooth functional tests passing, confirming firmware loaded successfully at runtime.
  3. Possible fix: Update Probe_Failure_Check test to exclude known-benign patterns: (1) suppress temp-alarm@a00 deferred probe entries for lemans-evk (these devices defer until thermal zones are registered, which is expected and non-blocking), (2) apply lava-known-benign-failures suppression rules — ignore firmware load errors when corresponding functional ON/OFF tests pass (BT_ON_OFF and WiFi_OnOff both passed).
  4. Detail analysis attachment: failed_case_job207884_1_detailed.md
  Case 2: smmu
  1. Failed case: smmu
  2. Root cause: Video codec device (aa00000.video-codec) on lemans-evk is not attached to any IOMMU group, failing the SMMU test's critical master protection validation.
  3. Possible fix: Verify that the video codec device tree node at aa00000.video-codec includes the required iommus property referencing the appropriate SMMU instance, or if the device is intentionally not using IOMMU protection, update the SMMU test's critical master list to exclude this device for lemans-evk.
  4. Detail analysis attachment: failed_case_job207884_2_detailed.md
  Case 3: 0_qcom-next-ci-premerge-tests
  1. Failed case: 0_qcom-next-ci-premerge-tests
  2. Root cause: LAVA infrastructure issue — test runner completed all tests successfully (including qcom_hwrng as the final test at 13:17:28, followed by <LAVA_TEST_RUNNER EXIT>), but LAVA dispatcher marked the test definition as "unfinished" and failed it with error "Marking unfinished test run as failed" despite receiving the proper exit signal.
  3. Possible fix: Re-trigger the LAVA job. This is a known LAVA dispatcher race condition where the test completion signal is received but the dispatcher's internal state machine incorrectly marks the run as incomplete. The two individual test failures (Probe_Failure_Check: deferred probe + firmware load errors; smmu: missing IOMMU group for video codec) are pre-existing platform issues unrelated to the PR changes (QMI cooling device tree bindings) and do not explain the overall test definition failure.
  4. Detail analysis attachment: failed_case_job207884_3_detailed.md
Job 207885 | SoC qcs6490-rb3gen2

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

Failed test cases in LAVA job 207885 (SoC: qcs6490-rb3gen2).

  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 framework attempted to load the optional regulatory.db firmware file from userspace, but the file is not present in the LAVA test rootfs. This is a benign failure because cfg80211 has compiled-in regulatory rules as a fallback, and all WiFi functional tests (WiFi_Firmware_Driver, WiFi_OnOff) passed successfully, proving wireless functionality is unaffected.
  3. Possible fix: This is a known benign failure that should be suppressed in the Probe_Failure_Check test. The test should exclude regulatory.db firmware load failures when WiFi functional tests pass. No kernel fix is required. To eliminate the warning, the LAVA rootfs image can be updated to include the regulatory.db file from the wireless-regdb package, but this is optional.
  4. Detail analysis attachment: failed_case_job207885_1_detailed.md
  Case 2: USBHost
  1. Failed case: USBHost
  2. Root cause: Test infrastructure issue — no external USB devices physically connected to the qcs6490-rb3gen2 board's USB host ports during test execution; USB core subsystem initialized correctly (usbcore registered, USB controllers 8c00000.usb and a600000.usb added to IOMMU groups 8 and 9), but lsusb enumeration returned empty because no physical USB peripherals were attached to the host ports.
  3. Possible fix: This is not a kernel regression introduced by PR lemans: Fix duplicate cdsp_sw cooling device #939 (which modifies QMI thermal cooling for CDSP, unrelated to USB). Verify USB host port hardware connectivity in the LAVA lab setup for qcs6490-rb3gen2; if the board is expected to have built-in USB devices or if external USB peripherals should be connected during CI runs, update the lab hardware configuration or test fixture to ensure USB devices are present before running the USBHost test case.
  4. Detail analysis attachment: failed_case_job207885_2_detailed.md
  Case 3: KVM_Driver
  1. Failed case: KVM_Driver
  2. Root cause: qcs6490-rb3gen2 (Kodiak) platform does not support ARM EL2/HYP mode, which is a hardware prerequisite for KVM virtualization; kernel correctly detects this limitation and reports "HYP mode not available" at boot, preventing /dev/kvm device node creation.
  3. Possible fix: This is not a kernel bug or PR-introduced regression — it is a platform hardware limitation. The KVM_Driver test should be skipped on qcs6490-rb3gen2 targets in the LAVA test suite configuration, or the test should be updated to check for HYP mode availability before attempting /dev/kvm validation and report SKIP instead of FAIL when HYP mode is unavailable.
  4. Detail analysis attachment: failed_case_job207885_3_detailed.md
  Case 4: KVM_EL2_DTB — Test Infrastructure Issue (Platform Limitation)
  1. Failed case: KVM_EL2_DTB — Test Infrastructure Issue (Platform Limitation)
  2. Root cause: The qcs6490-rb3gen2 board runs Linux as a guest under Gunyah hypervisor (EL1), which prevents KVM from accessing EL2 (HYP mode). The kernel correctly reports "HYP mode not available" at boot, and /dev/kvm is not created. This is expected behavior for this platform configuration, not a kernel regression.
  3. Possible fix: Exclude KVM tests (KVM_Driver, KVM_EL2_DTB, KVM_Infra) from the LAVA test suite for qcs6490-rb3gen2 when running under Gunyah hypervisor, or mark them as expected-to-skip. KVM cannot function when Linux runs as a guest VM under another hypervisor. This is a test infrastructure issue, not a kernel bug.
  4. Detail analysis attachment: failed_case_job207885_4_detailed.md
  Case 5: KVM_Infra
  1. Failed case: KVM_Infra
  2. Root cause: KVM cannot initialize on qcs6490-rb3gen2 because Gunyah hypervisor is already running at EL2 (HYP mode). KVM requires exclusive EL2 access for virtualization, but Gunyah occupies EL2 for its own hypervisor operations. The kernel message "kvm [1]: HYP mode not available" confirms EL2 is unavailable to KVM. This is a platform configuration issue, not a kernel regression.
  3. Possible fix: Disable Gunyah hypervisor in the platform firmware/bootloader configuration if KVM functionality is required, OR accept that KVM tests will fail on Gunyah-enabled platforms and exclude KVM tests from the CI test suite for qcs6490-rb3gen2. The two hypervisors are mutually exclusive on ARM64.
  4. Detail analysis attachment: failed_case_job207885_5_detailed.md
  Case 6: 0_qcom-next-ci-premerge-tests
  1. Failed case: 0_qcom-next-ci-premerge-tests
  2. Root cause: KVM tests failed because the qcs6490-rb3gen2 (Kodiak) platform does not support ARM virtualization extensions (EL2/HYP mode); kernel message "kvm [1]: HYP mode not available" at boot confirms the platform lacks hardware virtualization support, preventing /dev/kvm device creation.
  3. Possible fix: Mark KVM tests as "skip" or "not applicable" for qcs6490-rb3gen2 in the LAVA test plan, as this platform does not have the required hardware virtualization extensions; alternatively, exclude Virtualization/KVM test suite from qcom-next-ci-premerge.yaml for boards without EL2 support.
  4. Detail analysis attachment: failed_case_job207885_6_detailed.md
Job 207886 | SoC qcs9100-ride

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

Failed test cases in LAVA job 207886 (SoC: qcs9100-ride).

  Case 1: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Pre-existing platform configuration issues unrelated to PR changes: (1) Four SPMI PMIC temp-alarm devices (pmic@0/2/4/6:temp-alarm@a00) remain in deferred probe state due to missing IIO ADC thermal zone dependency; (2) regulatory.db firmware file missing from rootfs (-ENOENT); (3) Aquantia AQR115C Ethernet PHY at stmmac-0:08 fails probe with -EINVAL due to missing or malformed firmware-name DT property.
  3. Possible fix: These are pre-existing board/infra issues not introduced by this PR (which only adds qmi-cooling-cdsp1 support for lemans.dtsi). (1) For temp-alarm deferred probes: verify qcs9100-ride DT includes required IIO ADC thermal zone nodes and that the qcom-spmi-adc5 driver probes successfully; if ADC driver is missing, enable CONFIG_QCOM_SPMI_ADC5. (2) For regulatory.db: add regulatory.db firmware file to /lib/firmware/ in the rootfs image. (3) For Aquantia PHY: add or fix the "firmware-name" property in the qcs9100-ride DT node for stmmac-0:08 Ethernet PHY, or mark the property as optional if firmware is not required for this PHY variant.
  4. Detail analysis attachment: failed_case_job207886_1_detailed.md
  Case 2: smmu
  1. Failed case: smmu
  2. Root cause: The SMMU test expects a video codec device at aa00000.video-codec to be attached to an IOMMU group, but this device is not present or not attached on the qcs9100-ride platform. All SMMU functional checks passed (60 IOMMU groups present, critical masters UFS/Display/GPU/USB protected, no SMMU/IOMMU errors in kernel log), but the test failed because the hardcoded video codec device check did not find the expected device.
  3. Possible fix: This is a pre-existing platform/test configuration issue unrelated to PR lemans: Fix duplicate cdsp_sw cooling device #939 (which only modifies QMI cooling for CDSP). The test script should be updated to make the video codec check conditional based on platform capabilities, or the qcs9100-ride device tree should be verified to confirm whether video codec hardware is present and properly configured. Re-run the test on a platform with video codec support, or update the test to skip video codec validation on platforms where it's not available.
  4. Detail analysis attachment: failed_case_job207886_2_detailed.md
  Case 3: USBHost
  1. Failed case: USBHost
  2. Root cause: Test infrastructure issue — no external USB devices physically connected to the qcs9100-ride board; only USB root hubs (Bus 001/002/003) are enumerated. The test expects functional USB devices beyond root hubs but the lab setup has no USB peripherals attached. This is not a kernel regression; USB controllers initialized successfully and the PR changes (QMI thermal cooling for CDSP) do not affect USB functionality.
  3. Possible fix: Connect a functional USB device (e.g., USB flash drive, keyboard, or mouse) to one of the USB ports on the qcs9100-ride board before running the USBHost test. If this is a known lab limitation for this board, add USBHost to the known-benign-failures suppression list for qcs9100-ride, or mark the test as SKIP when no USB devices are expected to be present.
  4. Detail analysis attachment: failed_case_job207886_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 runner marked the test definition as "unfinished" and failed it after receiving <LAVA_TEST_RUNNER EXIT> signal, despite all individual test cases completing execution (including 3 genuine test failures: Probe_Failure_Check, smmu, USBHost). This is a LAVA test infrastructure issue, not a kernel crash or build load failure.
  3. Possible fix: The three genuine test failures should be addressed individually: (1) Probe_Failure_Check: resolve deferred probe issues for PMIC temp-alarm devices and fix Aquantia AQR115C Ethernet PHY probe failure (-EINVAL); (2) smmu: add IOMMU group attachment for Video codec (aa00000.video-codec); (3) USBHost: connect a functional USB device to the test board (currently only USB hubs are detected). The LAVA "unfinished" marking is likely a test harness configuration issue and should be investigated separately.
  4. Detail analysis attachment: failed_case_job207886_4_detailed.md
Job 207887 | SoC qcs615-ride

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

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

  Case 1: Build Load Failure — EDL/Sahara protocol communication failure during QDL flash
  1. Failed case: Build Load Failure — EDL/Sahara protocol communication failure during QDL flash
  2. Root cause: Result: Build Load Failure. The flash-universal.sh script failed during the EDL flashing stage when QDL attempted to collect crash dump from the device (PID 0x900e, serial EBF85AD4). The Sahara protocol handshake failed with "qdl: failed to open OCIMEM.BIN: No such file or directory" followed by "failed to read sahara request from device", preventing the device from being flashed. This is an infrastructure/board-level EDL communication issue on the qcs615-ride target, not a kernel or build artifact problem.
  3. Possible fix: Re-trigger the CI job. If the failure recurs, investigate the qcs615-ride board's EDL mode entry and USB connection stability — verify the board successfully enters EDL mode, check USB cable/hub connectivity, confirm the QDL tool version supports this board's Sahara protocol requirements, and verify the board's bootloader/PBL is not in a corrupted state requiring manual recovery. This is a lab infrastructure issue unrelated to the PR changes (thermal cooling driver for lemans SoC).
  4. Detail analysis attachment: failed_case_job207887_1_detailed.md
  Case 2: deploy-flasher-retry
  1. Failed case: deploy-flasher-retry
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Re-trigger the CI job; if the issue persists, investigate the qcs615-ride board state (may be stuck in crash dump mode) and power-cycle the board to clear any stale state. Verify the flash image package includes all required Sahara protocol files, or update the flash script to skip crash dump collection during normal flash operations.
  4. Detail analysis attachment: failed_case_job207887_2_detailed.md
  Case 3: Build Load Failure — QDL flash failure (missing OCIMEM.BIN)
  1. Failed case: Build Load Failure — QDL flash failure (missing OCIMEM.BIN)
  2. Root cause: Result: Build Load Failure. The flash process failed during QDL (Qualcomm Download Mode) crash dump collection phase with error "qdl: failed to open 'OCIMEM.BIN': No such file or directory" followed by "failed to read sahara request from device". This is a LAVA infrastructure issue on the qcs615-ride board — the device entered crash dump mode during flash but the required OCIMEM.BIN file was not present in the flash image package, causing the QDL tool to fail and the entire flash operation to abort.
  3. Possible fix: Re-trigger the CI job. If the issue recurs, verify that the qcom-multimedia-image-qcs615-ride.rootfs.qcomflash.tar.gz build artifact includes all required crash dump files (OCIMEM.BIN, etc.) or configure the flash script to skip crash dump collection on qcs615-ride. This is a pre-existing infrastructure issue unrelated to the PR changes (thermal QMI cooling for CDSP1 on lemans SoC).
  4. Detail analysis attachment: failed_case_job207887_3_detailed.md
Job 207888 | SoC hamoa-evk

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

Failed test cases in LAVA job 207888 (SoC: hamoa-evk).

  Case 1: Probe_Failure_Check
  1. Failed case: Probe_Failure_Check
  2. Root cause: Three pre-existing platform-specific probe failures unrelated to PR changes: (1) qcom_qseecom_uefisecapp probe failed with -EBUSY (secure firmware resource conflict), (2) qcom-spmi-lpg probe failed with -EINVAL (DT multi-led "reg" property misconfiguration), (3) regulatory.db firmware load failed with -ENOENT (expected on systems without wireless-regdb package).
  3. Possible fix: These are not PR-introduced regressions. The PR modifies only QMI thermal cooling (dt-bindings, driver, and lemans.dtsi) and does not touch qseecom, spmi-lpg, or cfg80211. Suppress this test failure as a false positive for this PR, or adjust the Probe_Failure_Check test to exclude known benign probe failures on hamoa-evk (qseecom -EBUSY when secure firmware is unavailable, spmi-lpg -EINVAL when multi-led DT is incomplete, regulatory.db -ENOENT when wireless-regdb is not installed).
  4. Detail analysis attachment: failed_case_job207888_1_detailed.md
  Case 2: smmu
  1. Failed case: smmu
  2. Root cause: Test validation failure — six USB controllers (a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb) and one video codec (aa00000.video-codec) are missing IOMMU group attachments on hamoa-evk; kernel logs show no SMMU/IOMMU errors, indicating this is a device tree configuration gap rather than a runtime failure.
  3. Possible fix: This is a pre-existing platform configuration issue unrelated to PR lemans: Fix duplicate cdsp_sw cooling device #939 (which modifies QMI cooling for CDSP). Add iommus properties to the missing USB controller and video codec device tree nodes in arch/arm64/boot/dts/qcom/hamoa*.dtsi to bind them to appropriate SMMU context banks, following the pattern used by the passing USB controllers (a000000.usb, a200000.usb, etc.).
  4. Detail analysis attachment: failed_case_job207888_2_detailed.md
  Case 3: KVM_Driver
  1. Failed case: KVM_Driver
  2. Root cause: KVM driver initialization failed because Gunyah hypervisor is already running at EL2 on the hamoa-evk (X1E80100) platform, preventing KVM from taking control of HYP mode. The kernel message "kvm [1]: HYP mode not available" at boot time indicates EL2 is unavailable to KVM.
  3. Possible fix: This is not a kernel bug or PR-introduced regression. The KVM test suite should skip KVM tests on platforms where Gunyah hypervisor is present, or the test infrastructure should be configured to exclude KVM tests from hamoa-evk CI runs. To enable KVM on this platform, the firmware/boot configuration would need to be changed to boot Linux directly at EL2 without Gunyah, which is a platform configuration decision outside the scope of kernel changes.
  4. Detail analysis attachment: failed_case_job207888_3_detailed.md
  Case 4: ** KVM_EL2_DTB — Test Infrastructure Limitation (Pre-existing Platform Constraint)
  1. Failed case: ** KVM_EL2_DTB — Test Infrastructure Limitation (Pre-existing Platform Constraint)
  2. Root cause: ** KVM cannot initialize on hamoa-evk because the platform boots under the Gunyah hypervisor (EL2 already occupied), preventing KVM from entering HYP mode. Kernel message at boot: kvm [1]: HYP mode not available. This is a pre-existing platform limitation, not a regression introduced by PR lemans: Fix duplicate cdsp_sw cooling device #939.
  3. Possible fix: Exclude KVM tests from the hamoa-evk LAVA test suite, as this platform does not support nested virtualization. The PR (QMI cooling CDSP1 support) is unrelated to KVM and should not be blocked by this failure.
  4. Detail analysis attachment: failed_case_job207888_4_detailed.md
  Case 5: ** KVM_Infra
  1. Failed case: ** KVM_Infra
  2. Root cause: ** KVM driver initialization blocked because Gunyah hypervisor is already running at EL2 on Hamoa EVK platform; KVM requires exclusive EL2 access and cannot coexist with another hypervisor (kernel log shows kvm [1]: HYP mode not available at boot time).
  3. Possible fix: This is expected behavior on Gunyah-enabled platforms. To enable KVM testing: (1) disable Gunyah hypervisor in Hamoa EVK bootloader/firmware configuration and reflash the board, OR (2) exclude KVM tests from Hamoa EVK CI job definitions (add to skip list), OR (3) route KVM tests to a different platform without Gunyah.
  4. Detail analysis attachment: failed_case_job207888_5_detailed.md
  Case 6: 0_qcom-next-ci-premerge-tests
  1. Failed case: 0_qcom-next-ci-premerge-tests
  2. Root cause: LAVA test definition marked as failed because 5 individual test cases within it failed: Probe_Failure_Check (3 probe errors: qcom_qseecom_uefisecapp -EBUSY, qcom-spmi-lpg -EINVAL, regulatory.db -ENOENT), smmu (3 critical masters missing IOMMU group: USB a6f8800, USB a8f8800, Video aa00000), and 3 KVM tests (KVM_Driver, KVM_EL2_DTB, KVM_Infra) all failing because /dev/kvm device node is not present. These failures are pre-existing platform/configuration issues unrelated to the PR's QMI cooling changes for lemans.dtsi.
  3. Possible fix: The test definition failure is a LAVA framework behavior (marking the overall definition as failed when any sub-test fails). The individual failures are not PR-introduced regressions: (1) Probe failures are known benign issues on hamoa-evk (qseecom EBUSY, lpg EINVAL, regulatory.db missing are platform-specific); (2) SMMU failures indicate USB/Video drivers not attaching to IOMMU groups on this platform; (3) KVM failures indicate CONFIG_KVM is enabled but /dev/kvm is not created, suggesting KVM runtime initialization issue on hamoa-evk. None of these are caused by the PR's dt-bindings/driver/dts changes for lemans CDSP1 cooling. Re-run the job or investigate the hamoa-evk platform configuration for KVM/SMMU/probe issues separately.
  4. Detail analysis attachment: failed_case_job207888_6_detailed.md
Job 207889 | SoC monaco-evk

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

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

  Case 1: ** Probe_Failure_Check — WiFi/BT Firmware Missing & ath11k Driver Probe Failure
  1. Failed case: ** Probe_Failure_Check — WiFi/BT Firmware Missing & ath11k Driver Probe Failure
  2. Root cause: ** The ath11k WiFi driver (ath11k_pci) probe failed with error -110 (ETIMEDOUT) because required firmware files are missing from the rootfs (ath11k/WCN6855/hw2.1/nfa765/amss.bin, Bluetooth firmware qca/wcnhpbtfw21.tlv, qca/hpbtfw21.tlv, and regulatory.db). The driver attempted to load firmware, failed with -ENOENT (-2), and subsequently timed out during hardware initialization, resulting in a hard probe failure. This is a pre-existing infrastructure/rootfs issue unrelated to the PR changes (which only modify QMI cooling for CDSP).
  3. Possible fix: Add the missing firmware files to the rootfs image: (1) ath11k/WCN6855/hw2.1/nfa765/amss.bin for WiFi, (2) qca/wcnhpbtfw21.tlv and qca/hpbtfw21.tlv for Bluetooth, and (3) regulatory.db for wireless regulatory database. These files should be included in the linux-firmware package or copied to /lib/firmware/ in the rootfs build recipe. Alternatively, if WiFi/BT are not required for monaco-evk CI validation, suppress this test case or mark firmware load failures as non-critical for this platform.
  4. Detail analysis attachment: failed_case_job207889_1_detailed.md
  Case 2: WiFi_Firmware_Driver — ath11k_pci probe failure
  1. Failed case: WiFi_Firmware_Driver — ath11k_pci probe failure
  2. Root cause: ath11k_pci driver probe failed with -110 (ETIMEDOUT) on monaco-evk because the required WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs (-2 = -ENOENT), causing MHI power-up to time out and the WCN6855 hw2.1 PCIe WiFi device to fail initialization.
  3. Possible fix: Add the missing firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/ath11k/WCN6855/hw2.1/nfa765/), or install the linux-firmware package containing ath11k WCN6855 firmware, then reboot to allow ath11k_pci to probe successfully.
  4. Detail analysis attachment: failed_case_job207889_2_detailed.md
  Case 3: WiFi_OnOff — WiFi driver probe failure
  1. Failed case: WiFi_OnOff — WiFi driver probe failure
  2. Root cause: WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs, causing MHI firmware load to fail with error -2 (ENOENT), which cascades to MHI power-up timeout (-110, ETIMEDOUT) and ath11k_pci probe failure on monaco-evk (WCN6855 hw2.1 PCIe WiFi chip).
  3. Possible fix: Add the missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/). This is a pre-existing platform/image issue unrelated to PR lemans: Fix duplicate cdsp_sw cooling device #939 (which only modifies thermal cooling for CDSP on lemans SoC).
  4. Detail analysis attachment: failed_case_job207889_3_detailed.md
  Case 4: Driver/Module Probe Failure — ath11k_pci WiFi driver
  1. Failed case: Driver/Module Probe Failure — ath11k_pci WiFi driver
  2. Root cause: ath11k_pci driver probe failed with error -110 (ETIMEDOUT) on monaco-evk because the required firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs (error -2 = ENOENT). This is a pre-existing infrastructure issue unrelated to the PR changes (which only modify QMI cooling device tree bindings for lemans platform CDSP1 support).
  3. Possible fix: Add the missing ath11k firmware files for WCN6855 hw2.1 nfa765 variant to the monaco-evk rootfs image. The firmware package should include ath11k/WCN6855/hw2.1/nfa765/amss.bin and related files. This is a test infrastructure fix, not a kernel code fix.
  4. Detail analysis attachment: failed_case_job207889_4_detailed.md
Job 207890 | SoC shikra-iqs-evk

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

Failed test cases in LAVA job 207890 (SoC: shikra-iqs-evk).

  Case 1: GIC
  1. Failed case: GIC
  2. Root cause: Test script bug — the GIC test script incorrectly assumes 8 CPUs and attempts to parse interrupt counters for CPUs 4-7, which do not exist on shikra-iqs-evk (4-core platform). The script's line 75 fails with "integer expected" errors when parsing non-existent CPU columns from /proc/interrupts, causing false test failures for CPUs 4-7.
  3. Possible fix: Update the GIC test script to dynamically detect the number of online CPUs from /sys/devices/system/cpu/online or /proc/cpuinfo before parsing /proc/interrupts, instead of hardcoding an assumption of 8 CPUs. The script should only validate timer interrupt increments for CPUs that actually exist on the target platform.
  4. Detail analysis attachment: failed_case_job207890_1_detailed.md
  Case 2: ** Remoteproc Boot Configuration Issue — modem subsystem not auto-booted
  1. Failed case: ** Remoteproc Boot Configuration Issue — modem subsystem not auto-booted
  2. Root cause: ** Remoteproc0 (modem/MPSS) on shikra-iqs-evk is configured without auto-boot enabled in device tree; the subsystem remains in offline state awaiting manual start or userspace service trigger, while CDSP and LPAICP auto-boot successfully. This is a platform-specific configuration choice, not a kernel regression.
  3. Possible fix: Update the CI test expectation for shikra-iqs-evk to mark remoteproc0 (modem) as expected: offline instead of expected: running, or add a pre-test step to manually start the modem via echo start > /sys/class/remoteproc/remoteproc0/state if modem boot validation is required. Alternatively, if modem auto-boot is desired, add the qcom,auto-boot property to the modem remoteproc node in arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts.
  4. Detail analysis attachment: failed_case_job207890_2_detailed.md
  Case 3: Probe_Failure_Check — Pre-existing Platform Issues
  1. Failed case: Probe_Failure_Check — Pre-existing Platform Issues
  2. Root cause: The test detected multiple probe failures and deferred probe entries on shikra-iqs-evk, all of which are pre-existing platform issues unrelated to the PR. The PR changes only affect Lemans platform (CDSP1 QMI cooling), while this test ran on shikra-iqs-evk. The detected failures are: (1) coresight-etm4x probe failures (error -22) — known DT/HW config mismatch for debug trace components; (2) cpufreq-dt double registration (error -17) — known benign race; (3) regulatory.db firmware missing (error -2) — optional WiFi regulatory database; (4) deferred probe entries for I2C, sound, codec, WiFi — expected dependency ordering, not failures.
  3. Possible fix: Mark this test case as PASS for this PR. The detected probe failures are pre-existing shikra-iqs-evk platform issues that exist in the baseline and are not introduced by this PR. To address the underlying platform issues separately: (1) For coresight-etm4x: review shikra DT ETM node configuration and ensure it matches hardware capabilities; (2) For cpufreq-dt: this is a known upstream race that can be ignored; (3) For regulatory.db: this is benign and can be ignored; (4) For deferred probe entries: these are expected and will resolve once dependencies probe — no action needed unless devices remain deferred after boot completes.
  4. Detail analysis attachment: failed_case_job207890_3_detailed.md
  Case 4: USBHost
  1. Failed case: USBHost
  2. Root cause: No USB devices physically connected to the shikra-iqs-evk board's USB host port during test execution; USB host controller and drivers initialized successfully but no devices were enumerated.
  3. Possible fix: Connect a USB device (e.g., USB flash drive, keyboard, or hub) to the board's USB host port before running the USBHost test; alternatively, mark this test as SKIP when no USB hardware is available in the test environment.
  4. Detail analysis attachment: failed_case_job207890_4_detailed.md
  Case 5: BT_SCAN
  1. Failed case: BT_SCAN
  2. Root cause: Test environment limitation — no discoverable Bluetooth devices present in the LAVA lab environment during the scan window (3 attempts × 15 seconds each), despite Bluetooth hardware and stack functioning correctly (BT_ON_OFF passed, hci0 powered on, discovery started/stopped successfully).
  3. Possible fix: This is not a kernel regression introduced by PR lemans: Fix duplicate cdsp_sw cooling device #939 (which only modifies thermal cooling device tree bindings for CDSP on lemans, unrelated to Bluetooth). The failure is expected in a lab environment without nearby Bluetooth devices. To resolve: (1) place a discoverable Bluetooth device (phone, speaker, or beacon) within range of the shikra-iqs-evk board during test execution, or (2) modify the BT_SCAN test to skip gracefully when no devices are found (treating it as a SKIP rather than FAIL when BT_ON_OFF passes), or (3) suppress BT_SCAN failures in CI when BT_ON_OFF passes, similar to the existing WiFi/BT firmware suppression rules.
  4. Detail analysis attachment: failed_case_job207890_5_detailed.md
  Case 6: ** KVM_Driver
  1. Failed case: ** KVM_Driver
  2. Root cause: ** KVM initialization failed because HYP (EL2) mode is not available on the Shikra IQS EVK platform. The kernel message kvm [1]: HYP mode not available at boot time (3.1s) indicates the bootloader/firmware did not configure the CPU to boot with EL2 accessible to the kernel, which is a prerequisite for ARM64 KVM support.
  3. Possible fix: This is a pre-existing platform/firmware configuration issue, not a PR-introduced regression. To enable KVM on Shikra IQS EVK: (1) Verify the bootloader (ABL/UEFI) is configured to boot the kernel at EL2 or with VHE (Virtualization Host Extensions) enabled; (2) Check if the firmware supports EL2 and is not trapping it for secure world use; (3) If the platform does not support EL2 in non-secure world, KVM cannot be enabled and the test should be marked as N/A for this board.
  4. Detail analysis attachment: failed_case_job207890_6_detailed.md
  Case 7: KVM_EL2_DTB
  1. Failed case: KVM_EL2_DTB
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: This is a pre-existing platform/firmware issue unrelated to PR lemans: Fix duplicate cdsp_sw cooling device #939 (which only modifies QMI cooling for CDSP). The fix requires: (1) Verify the qcom_rng driver's power/clock dependencies are correctly described in the Shikra device tree and that runtime PM is properly sequenced. (2) Check if the RNG hardware block requires explicit power domain or clock enablement before register access. (3) Add error handling in qcom_rng_read to gracefully handle hardware access failures instead of crashing. (4) Investigate whether this is a known Shikra IQS EVK firmware/hardware limitation where the RNG block is not functional.
  4. Detail analysis attachment: failed_case_job207890_7_detailed.md
  Case 8: KVM_Infra
  1. Failed case: KVM_Infra
  2. Root cause: Could not be determined confidently from available logs.
  3. Possible fix: Disable KVM tests (KVM_Driver, KVM_EL2_DTB, KVM_Infra) for the Shikra IQS EVK platform in the LAVA test suite configuration, as this platform does not support KVM. Add platform-specific test exclusion in the LAVA job definition or CI configuration to skip virtualization tests on platforms without EL2 support.
  4. Detail analysis attachment: failed_case_job207890_8_detailed.md
  Case 9: ** Kernel Crash — Synchronous External Abort in qcom_rng driver
  1. Failed case: ** Kernel Crash — Synchronous External Abort in qcom_rng driver
  2. Root cause: ** Pre-existing platform issue on shikra-iqs-evk: the qcom_rng hardware block is not correctly powered/clocked/initialized, causing a synchronous external abort (bus error) when the driver attempts to read hardware registers during the qcom_hwrng test. The crash is unrelated to PR lemans: Fix duplicate cdsp_sw cooling device #939, which modifies only the qmi-cooling thermal driver for the lemans SoC.
  3. Possible fix: This is a board/platform configuration issue, not a PR regression. Recommended actions: (1) Disable the qcom_hwrng test on shikra-iqs-evk until the platform issue is resolved, OR (2) Fix the shikra device tree to add missing clock/regulator/interconnect dependencies for the qcom_rng node, OR (3) Add runtime PM support to the qcom_rng driver if the hardware requires it on this platform. PR lemans: Fix duplicate cdsp_sw cooling device #939 can proceed — this failure is not caused by the PR changes.
  4. Detail analysis attachment: failed_case_job207890_9_detailed.md
  Case 10: Kernel Crash — Hardware fault in qcom_rng driver
  1. Failed case: Kernel Crash — Hardware fault in qcom_rng driver
  2. Root cause: Synchronous external abort (hardware fault) occurred while the qcom_hwrng test was reading from the hardware RNG device at address accessed by qcom_rng_read(). This triggered a cascade of hundreds of EFI runtime service paging faults, followed by a warm reset (PS_HOLD) and ramdump collection (XBLRamDump). The board never recovered from ramdump mode, causing the LAVA test shell to timeout after 2400 seconds.
  3. Possible fix: This is a pre-existing hardware/firmware issue on shikra-iqs-evk, not introduced by PR lemans: Fix duplicate cdsp_sw cooling device #939 (which only modifies QMI cooling for CDSP on lemans platform). The synchronous external abort indicates the RNG hardware block is either not properly initialized, not clocked, or the memory-mapped register access is faulting. Recommended actions: (1) Verify qcom_rng device tree configuration for shikra-iqs-evk includes correct reg address and required clocks/power domains; (2) Check if RNG hardware block requires explicit firmware/secure-world initialization on this SoC; (3) Add error handling in qcom_rng driver to gracefully handle hardware access faults; (4) Re-trigger the CI job to confirm if this is a transient hardware issue or reproducible.
  4. Detail analysis attachment: failed_case_job207890_10_detailed.md
  Case 11: Kernel Crash — Synchronous External Abort in qcom_rng driver
  1. Failed case: Kernel Crash — Synchronous External Abort in qcom_rng driver
  2. Root cause: Hardware access fault in qcom_rng_read() at offset +0xc4 while reading from the QCOM hardware RNG device (0x000632e8e54a9000). The crash occurred during a dd read from /dev/hwrng, triggering a synchronous external abort (ESR 0x96000010) indicating an invalid physical address access or unpowered/unconfigured hardware block. The board subsequently entered EDL/ramdump mode and timed out the LAVA test after 2400 seconds (40 minutes).
  3. Possible fix: Verify that the QCOM RNG hardware block is properly powered, clocked, and mapped in the device tree for shikra-iqs-evk. Check if the RNG device node in arch/arm64/boot/dts/qcom/shikra*.dtsi has correct reg addresses, clocks, and power domain bindings. If the hardware is not present or not functional on this board variant, disable the qcom_rng driver in the defconfig or mark the DT node as status="disabled" for shikra-iqs-evk.
  4. Detail analysis attachment: failed_case_job207890_11_detailed.md
  Case 12: Test Timeout — qcom_hwrng test triggered kernel crash
  1. Failed case: Test Timeout — qcom_hwrng test triggered kernel crash
  2. Root cause: Synchronous external abort (hardware bus error) in qcom_rng_read() at offset +0xc4 when accessing hardware RNG registers during /dev/hwrng read operation; the fault occurred at instruction b940035c (load from [x1 + 0xc]), indicating the mapped MMIO region became inaccessible or was incorrectly mapped, possibly due to power/clock gating or firmware/hardware state issue on shikra-iqs-evk.
  3. Possible fix: This is a pre-existing platform/hardware issue unrelated to the PR (which only modifies QMI cooling for CDSP1). The qcom_rng driver needs defensive checks: (1) verify clock/power state before register access, (2) add error handling for external aborts, (3) investigate why the RNG hardware block became inaccessible on shikra-iqs-evk — check device tree clock/power-domain bindings, firmware version, and whether the RNG block requires explicit power-on sequencing on this SoC.
  4. Detail analysis attachment: failed_case_job207890_12_detailed.md
Job 207891 | SoC purwa-evk

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

Failed test cases in LAVA job 207891 (SoC: purwa-evk).

  Case 1: Probe_Failure_Check — Pre-existing Platform Driver Probe Failures
  1. Failed case: Probe_Failure_Check — Pre-existing Platform Driver Probe Failures
  2. Root cause: The Probe_Failure_Check test detected 5 pre-existing driver probe failures on purwa-evk (iq-x5121-evk) that are unrelated to the PR changes (QMI cooling CDSP1 support for lemans SoC): qcom_qseecom_uefisecapp (-EBUSY), two qcom-pcie instances (-ENODATA), qcom-spmi-lpg (-EINVAL), and regulatory.db firmware (-ENOENT). These failures existed before the PR and are platform-specific hardware/firmware configuration issues on the purwa-evk test board, not regressions introduced by the PR's changes to lemans.dtsi and QMI cooling driver.
  3. Possible fix: Mark this test case as a known pre-existing platform issue for purwa-evk and exclude it from PR validation, or update the Probe_Failure_Check test to maintain a platform-specific allowlist of expected probe failures. The PR changes (QMI cooling CDSP1 for lemans) do not affect purwa-evk and should not be blocked by these unrelated probe failures.
  4. Detail analysis attachment: failed_case_job207891_1_detailed.md
  Case 2: ** smmu
  1. Failed case: ** smmu
  2. Root cause: ** Test validation failure due to missing IOMMU group attachments for 6 devices on purwa-evk: 5 USB PHY devices (a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb) and 1 video codec device (aa00000.video-codec). This is a pre-existing platform device tree configuration issue, not a PR-introduced regression. The SMMU/IOMMU subsystem is functioning correctly (no kernel errors), but these devices lack iommus properties in their device tree nodes or are intentionally not protected.
  3. Possible fix: Update the purwa-evk device tree to add iommus properties to the missing devices if they require IOMMU protection, OR update the test script to exclude USB PHY devices and video codec from the "critical master" check on purwa-evk if they are intentionally unprotected on this platform.
  4. Detail analysis attachment: failed_case_job207891_2_detailed.md
  Case 3: KVM_Driver — /dev/kvm device node unavailable
  1. Failed case: KVM_Driver — /dev/kvm device node unavailable
  2. Root cause: KVM initialization failed at boot with "HYP mode not available" because the Purwa IoT EVK platform does not support ARM EL2 (hypervisor exception level), which is a hardware prerequisite for KVM virtualization on ARM64.
  3. Possible fix: Mark KVM_Driver, KVM_EL2_DTB, and KVM_Infra tests as "skip" for purwa-evk in the LAVA test suite configuration, as this platform lacks the required EL2 hardware support for KVM.
  4. Detail analysis attachment: failed_case_job207891_3_detailed.md
  Case 4: KVM Driver Initialization Failure — /dev/kvm not available
  1. Failed case: KVM Driver Initialization Failure — /dev/kvm not available
  2. Root cause: KVM driver cannot initialize on purwa-evk because the platform firmware does not provide HYP (EL2 hypervisor) mode access to the kernel, as evidenced by "kvm [1]: HYP mode not available" at boot time.
  3. Possible fix: This is a pre-existing platform/firmware limitation, not a regression introduced by PR lemans: Fix duplicate cdsp_sw cooling device #939. The PR only modifies thermal QMI cooling device tree bindings for lemans SoC and does not touch purwa, KVM, or virtualization code. No kernel fix is required. To enable KVM on purwa-evk, the platform firmware (ABL/HYP) must be configured to allow EL2 access, or the test should be marked as expected-fail for this platform.
  4. Detail analysis attachment: failed_case_job207891_4_detailed.md
  Case 5: KVM_Infra — KVM driver initialization failure (HYP mode not available)
  1. Failed case: KVM_Infra — KVM driver initialization failure (HYP mode not available)
  2. Root cause: KVM driver failed to initialize during boot because the purwa-evk platform does not support ARM Virtualization Extensions (HYP/EL2 mode unavailable); kernel log shows kvm [1]: HYP mode not available at boot time, preventing /dev/kvm device node creation.
  3. Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression (PR modifies QMI thermal cooling for CDSP, unrelated to KVM). Mark KVM tests as expected-fail or skip for purwa-evk in the LAVA job definition, or enable virtualization support in the platform firmware/bootloader if the hardware supports it.
  4. Detail analysis attachment: failed_case_job207891_5_detailed.md
  Case 6: 0_qcom-next-ci-premerge-tests
  1. Failed case: 0_qcom-next-ci-premerge-tests
  2. Root cause: KVM virtualization tests failed because HYP (EL2 hypervisor) mode is not available on the purwa-evk platform — the kernel detected at boot that it is not running at EL2 and printed "kvm [1]: HYP mode not available", causing /dev/kvm to never be created and all KVM infrastructure tests to fail.
  3. Possible fix: This is not a kernel regression introduced by PR lemans: Fix duplicate cdsp_sw cooling device #939 (which only modifies thermal QMI cooling device bindings for lemans SoC). The purwa-evk platform either lacks EL2 support in its firmware/bootloader configuration or the kernel was not booted at EL2. To resolve: (1) verify the platform's TrustZone/hypervisor configuration allows EL2 execution, (2) check bootloader settings to ensure the kernel is entered at EL2, or (3) exclude KVM tests from the purwa-evk CI test suite if the platform does not support virtualization.
  4. Detail analysis attachment: failed_case_job207891_6_detailed.md

@qcomlnxci

qcomlnxci commented Aug 28, 2026

Copy link
Copy Markdown

Test jobs on 1c06ae5

@qcomlnxci

qcomlnxci commented Aug 28, 2026

Copy link
Copy Markdown

Test Matrix

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

@qcomlnxci

qcomlnxci commented Aug 29, 2026

Copy link
Copy Markdown

Test jobs on 1c06ae5

@qcomlnxci

qcomlnxci commented Aug 29, 2026

Copy link
Copy Markdown

Test Matrix

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

@sgaud-quic
Salendarsingh Gaud (sgaud-quic) merged commit 8df65d7 into qualcomm-linux:qcom-6.18.y Aug 30, 2026
6 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Komal-Bajaj Komal Bajaj (Komal-Bajaj) Komal-Bajaj approved these changes
@idlethread Amit Kucheria (idlethread) Awaiting requested review from idlethread idlethread was automatically assigned from qualcomm-linux/qualcomm-kernel-maint
@quic-kaushalk Kaushal Kumar (quic-kaushalk) Awaiting requested review from quic-kaushalk quic-kaushalk was automatically assigned from qualcomm-linux/qualcomm-kernel-maint
@aiquny aiquny Awaiting requested review from aiquny aiquny was automatically assigned from qualcomm-linux/qualcomm-kernel-maint

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@dmantre @qlijarvis @gauravkohli1 @qcomlnxci @Komal-Bajaj @sgaud-quic @kcxt