Skip to content

FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and refgen supply for PCIe PHYs - #1327

Merged
Salendarsingh Gaud (sgaud-quic) merged 1 commit into
qualcomm-linux:qcom-6.18.yfrom
ziyuezhang-123:for-6.18/arm64-dts-qcom-monaco-monza-som-add-pcie-phy-supplies
Oct 27, 2026
Merged

Salendarsingh Gaud (sgaud-quic) merged 1 commit into
qualcomm-linux:qcom-6.18.yfrom
ziyuezhang-123:for-6.18/arm64-dts-qcom-monaco-monza-som-add-pcie-phy-supplies

Conversation

@ziyuezhang-123

@ziyuezhang-123 ziyuezhang-123 commented Oct 22, 2026 •

Copy link
Copy Markdown

The QMP PCIe PHYs on QCS8300 require dedicated qref and refgen voltage
supplies for stable operation. Without these supplies, the system may
occasionally crash.

Add vdda-qref-supply and vdda-refgen-supply to the Monaco Monza SoM
board file for both pcie0_phy and pcie1_phy nodes.

This is the monaco-monza-som.dtsi portion of the patch series that was
previously skipped (file was absent at the time of the original PR).
The other files (monaco.dtsi, qcs8300-ride.dts, monaco-evk-common.dtsi)
were already submitted in a prior PR.

Fixes: 5238f4e ("arm64: dts: qcom: Add Monaco Monza SoM")
Link: https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/
Signed-off-by: Ziyue Zhang ziyue.zhang@oss.qualcomm.com

CRs-Fixed:4709512

@qswat-orbit-external

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

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4709512 is not eligible for merge.

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

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

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

2 similar comments
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4709512 is not eligible for merge.

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

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

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

@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4709512 is not eligible for merge.

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

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

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

@qlijarvis

Copy link
Copy Markdown

PR #1327 — validate-patch

PR: #1327

Verdict Issues Detailed Report
❌ 0 Full report

Final Summary

  1. Lore link present: Yes — https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/
  2. Lore link matches PR commits: No — PR contains only 1 of 4 files from the lore patch; missing monaco.dtsi (refgen-supply), monaco-evk.dts, and qcs8300-ride.dts changes
  3. Upstream patch status: ⏳ Decision Pending — posted 2026-09-16, no acceptance signal yet
  4. PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1327 — FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and refgen supply for PCIe PHYs
Upstream commit: https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream ⚠️ PR subject mentions only monaco-monza-som; lore patch is broader (qcs8300)
Body preserves rationale ⚠️ PR body omits mention of monaco.dtsi changes and refgen-supply
Fixes tag present/correct ⚠️ PR has 1 Fixes tag; lore has 4 Fixes tags for all affected boards
Authorship preserved ✅ From: matches lore author (correct for FROMLIST:)
Backport note (if applicable) N/A Not a backport; FROMLIST: prefix is correct

Diff

File Status Notes
arch/arm64/boot/dts/qcom/monaco-monza-som.dtsi ✅ Hunks match lore patch exactly
arch/arm64/boot/dts/qcom/monaco.dtsi ❌ Missing from PR — lore adds refgen-supply to pcie0_phy and pcie1_phy
arch/arm64/boot/dts/qcom/monaco-evk.dts ❌ Missing from PR — lore adds vdda-qref/vdda-refgen to both PHYs
arch/arm64/boot/dts/qcom/qcs8300-ride.dts ❌ Missing from PR — lore adds vdda-qref/vdda-refgen to both PHYs

Issues

  1. Incomplete backport — The lore patch (v2 3/4) modifies 4 files across QCS8300 boards (monaco-evk, monaco-monza-som, qcs8300-ride) plus the shared SoC DTSI (monaco.dtsi). The PR contains only 1 of 4 files (monaco-monza-som.dtsi).

  2. Missing critical SoC-level change — The lore patch adds refgen-supply = <&refgen>; to monaco.dtsi for both pcie0_phy and pcie1_phy nodes. The commit message explicitly states: "add refgen-supply in the SoC DTSI (monaco.dtsi) since refgen is an on-chip regulator shared across boards." This change is absent from the PR.

  3. Commit message mismatch — The PR commit message says "Add vdda-qref-supply and vdda-refgen-supply to the Monaco Monza SoM board file" but does not mention the missing monaco.dtsi changes. The lore commit message correctly describes all changes: "Add vdda-qref-supply and vdda-refgen-supply in the board files (QCS8300-RIDE, Monaco-EVK and Monaco-Monza-SoM), and add refgen-supply in the SoC DTSI (monaco.dtsi)."

  4. Incomplete Fixes tags — The PR has only Fixes: 5238f4e7169f (Monaco Monza SoM). The lore patch has 4 Fixes tags covering all affected boards.

Upstream Patch Status

Commit Community Verdict
arm64: dts: qcom: qcs8300: Add qref and refgen supply for PCIe PHYs ⏳ Decision Pending — posted 2026-09-16; author pinged maintainers 2026-10-13; no Reviewed-by/Acked-by/applied signal yet

qcom-next Presence

Commit Status
FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and refgen supply for PCIe PHYs ✅ Present in qcom-next as reported by integration_presence_report.md

Verdict

Do not merge. This PR is an incomplete subset of the upstream lore patch. The missing monaco.dtsi changes are critical — without refgen-supply in the SoC DTSI, the PHY driver cannot vote for refgen3, which the commit message identifies as a workaround for a hardware issue. The PR should either:

  1. Include all 4 files from the lore patch (monaco-evk.dts, monaco-monza-som.dtsi, monaco.dtsi, qcs8300-ride.dts), or
  2. Split into separate commits — one for monaco.dtsi (SoC-level), one per board file — with updated commit messages and Fixes tags for each.

The current PR cherry-picks only the monaco-monza-som.dtsi changes and omits the shared SoC infrastructure, making it an incomplete and potentially non-functional backport.

Final Summary

  1. Lore link present: Yes — https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/
  2. Lore link matches PR commits: No — PR contains only 1 of 4 files from the lore patch; missing monaco.dtsi (refgen-supply), monaco-evk.dts, and qcs8300-ride.dts changes
  3. Upstream patch status: ⏳ Decision Pending — posted 2026-09-16, no acceptance signal yet
  4. PR present in qcom-next/topics: Yes — integration_presence_report.md confirms all checked lines are present in qcom-next

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

Commit Subject qcom-next topics Final
1/1 [PATCH] FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and present - all checked added lines are present skipped - not checked because qcom-next already contains the change present

Final Status

overall_status: PASS
present_commits: 1/1
partial_commits: 0/1
missing_commits: 0/1
topics_checked_for_commits: 0/1
final_summary: PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

@qlijarvis

Copy link
Copy Markdown

PR #1327 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ❌ 1 warning: Unknown commit id in Fixes tag
dt-binding-check ⏭️ No binding changes
dtb-check ✅ Test passed
sparse-check ⏭️ No C/H file changes
check-uapi-headers ⏭️ No UAPI changes
check-patch-compliance ❌ Content mismatch with upstream link
tag-check ✅ Subject has valid FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1327 - FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and refgen supply for PCIe PHYs
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/39764953678

Checker Result Summary
checkpatch ❌ 1 warning: Unknown commit id in Fixes tag
dt-binding-check ⏭️ No binding changes
dtb-check ✅ Test passed
sparse-check ⏭️ No C/H file changes
check-uapi-headers ⏭️ No UAPI changes
check-patch-compliance ❌ Content mismatch with upstream link
tag-check ✅ Subject has valid FROMLIST: prefix

❌ checkpatch

Root cause: The Fixes: tag references commit 5238f4e7169f which is not reachable in the current tree.

Failure details:

WARNING: Unknown commit id '5238f4e7169f', maybe rebased or not pulled?
#14: 
Fixes: 5238f4e7169f ("arm64: dts: qcom: Add Monaco Monza SoM")

3209ca8f8a3e405627dafe69fd45c10655d1bc2f total: 0 errors, 1 warnings, 0 checks, 16 lines checked

Fix:

The commit referenced in the Fixes: tag (5238f4e7169f) is not present in the current tree. This typically happens when:

  1. The original commit was rebased/rewritten with a different SHA
  2. The commit exists in a different branch that hasn't been merged yet
  3. The SHA is truncated incorrectly

Action required:

# Find the correct commit SHA in the current tree
git log --all --oneline --grep="Add Monaco Monza SoM"

# Update the Fixes tag with the correct full SHA (12+ chars minimum)
git rebase -i f46367083aea   # mark commit as 'edit'
# Edit commit message to use correct Fixes: SHA
git commit --amend
git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git f46367083aeae92dacbf35b714faf4c66cc9b7dd..3209ca8f8a3e405627dafe69fd45c10655d1bc2f

❌ check-patch-compliance

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

Failure details:

Checking commit: FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and refgen supply for PCIe PHYs
Change is different from the one mentioned in Link

Fix:

The checker detected that the patch content doesn't match the upstream version at:
https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/

Possible causes:

  1. Context-only difference — surrounding lines changed due to other patches (not a real issue)
  2. Legitimate adaptation — patch was modified for the target tree (needs documentation in commit message)
  3. Missing/extra hunks — incomplete backport or additional changes bundled together

Action required:

# Fetch the upstream patch and compare
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/ -o /tmp/upstream

# Compare the actual code changes (ignoring context)
git format-patch -1 3209ca8f8a3e --stdout | awk '/^diff/,/^--$/' | grep -E '^[+-][^+-]' > /tmp/pr-changes.txt
awk '/^diff/,/^--$/' /tmp/upstream/*.mbx | grep -E '^[+-][^+-]' > /tmp/upstream-changes.txt
diff /tmp/pr-changes.txt /tmp/upstream-changes.txt

If the difference is legitimate (e.g., adapted for a different base), add a note to the commit message:

[Adapted for <branch>: <brief explanation of what changed and why>]

If the difference is unintentional, fetch and apply the correct upstream version:

git reset --hard f46367083aea
b4 am -o - https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/ | git am

Verdict

2 blockers must be fixed before merge:

  1. checkpatch: Fix the Fixes: tag to reference a valid commit SHA that exists in the target tree
  2. check-patch-compliance: Investigate and resolve the content mismatch with the upstream patch — either document the adaptation or re-apply the correct upstream version

Both issues are straightforward to fix but are mandatory for merge compliance.

@qcomlnxci

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_Basic_Validation ⚠️ skip ✅ Pass ✅ Pass ⚠️ skip ◻️ ⚠️ skip ❌ Fail ⚠️ skip ⚠️ skip
Freq_Scaling ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ❌ Fail ✅ Pass ✅ Pass ✅ Pass
GIC ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ❌ Fail ✅ 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 ◻️ ✅ Pass ❌ Fail ❌ Fail ❌ Fail
KVM_EL2_DTB ❌ Fail ✅ Pass ✅ Pass ❌ Fail ◻️ ✅ Pass ❌ Fail ❌ Fail ❌ Fail
KVM_Infra ❌ Fail ✅ Pass ✅ Pass ❌ Fail ◻️ ✅ Pass ❌ Fail ❌ Fail ❌ Fail
OpenCV ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass
PCIe ✅ Pass ✅ Pass ✅ Pass ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ❌ Fail
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 ◻️ ⚠️ skip ❌ Fail ✅ Pass ❌ Fail
WiFi_Firmware_Driver ✅ Pass ✅ Pass ❌ Fail ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass
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 ◻️ ❌ Fail ✅ 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 ◻️
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

@sgaud-quic

Copy link
Copy Markdown
Contributor

ziyuezhang-123 please fix kernel checker :

❌ checkpatch
Root cause: The Fixes: tag references commit 5238f4e7169f which is not reachable in the current tree.

@ziyuezhang-123
ziyuezhang-123 force-pushed the for-6.18/arm64-dts-qcom-monaco-monza-som-add-pcie-phy-supplies branch from 3209ca8 to cfc4852 Compare October 26, 2026 09:19
@qcomlnxci
qcomlnxci requested a review from a team October 26, 2026 09:21
…ply for PCIe PHYs

The QMP PCIe PHYs on QCS8300 require dedicated qref and refgen voltage
supplies for stable operation. Without these supplies, the system may
occasionally crash.

Add vdda-qref-supply and vdda-refgen-supply to the Monaco Monza SoM
board file for both pcie0_phy and pcie1_phy nodes.

Fixes: 8f398ed ("UPSTREAM: arm64: dts: qcom: Add Monaco Monza SoM")
Link: https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/
Signed-off-by: Ziyue Zhang <ziyue.zhang@oss.qualcomm.com>
@ziyuezhang-123
ziyuezhang-123 force-pushed the for-6.18/arm64-dts-qcom-monaco-monza-som-add-pcie-phy-supplies branch from cfc4852 to ce211e5 Compare October 26, 2026 09:50
@ziyuezhang-123

Copy link
Copy Markdown
Author

Salendarsingh Gaud (@sgaud-quic) Fixed in the latest push. The Fixes: tag has been updated from the unreachable commit 5238f4e7169f to 8f398ed3e896 ("UPSTREAM: arm64: dts: qcom: Add Monaco Monza SoM"), which is the correct reachable commit in this tree.

@qlijarvis

Copy link
Copy Markdown

PR #1327 — validate-patch

PR: #1327

Verdict Issues Detailed Report
❌ 2 Full report

Final Summary

  1. Lore link present: Yes — https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/
  2. Lore link matches PR commits: No — PR applies only 1 of 4 files from the lore patch; commit message rewritten to hide multi-file scope; 3 of 4 Fixes tags missing
  3. Upstream patch status: ⏳ Decision Pending — posted Sep 16, 2026; author pinged maintainers Oct 13, 2026; no merge/NAK signal yet
  4. PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1327 — FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and refgen supply for PCIe PHYs
Upstream commit: https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream ❌ PR subject mentions only monaco-monza-som; lore subject is qcs8300: Add qref and refgen supply (covers 4 files)
Body preserves rationale ⚠️ PR body is rewritten and omits key details: missing mention of monaco.dtsi refgen-supply, missing explanation of refgen3 workaround, missing 3 of 4 Fixes tags
Fixes tag present/correct ❌ PR has 1 Fixes tag; lore has 4 Fixes tags (one per board/file)
Authorship preserved ✅ From: matches lore author (correct for FROMLIST:)
Backport note (if applicable) N/A Not a backport; FROMLIST: prefix is correct

Diff

File Status Notes
arch/arm64/boot/dts/qcom/monaco-monza-som.dtsi ✅ Hunks match lore patch exactly (4 lines added: 2 supplies × 2 PHYs)
arch/arm64/boot/dts/qcom/monaco-evk.dts ❌ Missing from PR — lore patch adds same 2 supplies to monaco-evk board
arch/arm64/boot/dts/qcom/monaco.dtsi ❌ Missing from PR — lore patch adds refgen-supply to SoC DTSI for both PHYs
arch/arm64/boot/dts/qcom/qcs8300-ride.dts ❌ Missing from PR — lore patch adds same 2 supplies to qcs8300-ride board

Issues

Critical: Incomplete backport
The lore patch (v2 3/4) modifies 4 files to add qref/refgen supplies across three boards (monaco-evk, monaco-monza-som, qcs8300-ride) and the shared SoC DTSI (monaco.dtsi). The PR applies only 1 of 4 files (monaco-monza-som.dtsi), leaving the other boards and the SoC-level refgen-supply missing.

Commit message divergence

  • Subject mismatch: PR subject monaco-monza-som: Add qref and refgen supply implies a single-board change; lore subject qcs8300: Add qref and refgen supply correctly reflects the multi-board scope.
  • Body rewritten: PR body omits critical context from lore:
    • No mention of monaco.dtsi refgen-supply addition
    • No explanation of refgen3 workaround for hardware issue
    • Missing 3 of 4 Fixes tags (only kept the monaco-monza-som tag)
  • Fixes tags incomplete: Lore has 4 Fixes tags (one per board/file); PR has only 1.

Authorship
✅ Correct for FROMLIST: — From: matches lore author; original author's Signed-off-by: is present.

Upstream Patch Status

Commit Community Verdict
[PATCH v2 3/4] arm64: dts: qcom: qcs8300: Add qref and refgen supply for PCIe PHYs ⏳ Decision Pending — posted Sep 16, 2026; author pinged maintainers Oct 13, 2026; no ACK/NAK/merge signal yet

qcom-next Presence

Commit Status
FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and refgen supply for PCIe PHYs ✅ Present in qcom-next — all checked added lines are present (per integration_presence_report.md)

Note: The integration presence check only validates the lines present in the PR (monaco-monza-som.dtsi). It does not check whether the missing files (monaco-evk.dts, monaco.dtsi, qcs8300-ride.dts) are present in qcom-next, because those files are not part of this PR.

Verdict

Do not merge. This PR is an incomplete backport of a multi-file lore patch. The PR applies only 1 of 4 files from the upstream patch, leaving three boards/files without the required supply additions. The commit message has been rewritten to hide the multi-file scope, and 3 of 4 Fixes tags are missing.

Required corrections:

  1. Split into 4 separate commits (one per file, matching the lore patch structure), or apply all 4 files in a single commit with the correct multi-file subject and body.
  2. Restore the original lore commit message — subject should be qcs8300: Add qref and refgen supply for PCIe PHYs (not monaco-monza-som:), body must mention all 4 files and the refgen3 workaround, and all 4 Fixes tags must be present.
  3. Verify the other 3 files are either already in qcom-next or submitted in separate PRs. If they are missing, they must be added.

Final Summary

  1. Lore link present: Yes — https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/
  2. Lore link matches PR commits: No — PR applies only 1 of 4 files from the lore patch; commit message rewritten to hide multi-file scope; 3 of 4 Fixes tags missing
  3. Upstream patch status: ⏳ Decision Pending — posted Sep 16, 2026; author pinged maintainers Oct 13, 2026; no merge/NAK signal yet
  4. PR present in qcom-next/topics: Partial — integration check reports the monaco-monza-som.dtsi lines are present in qcom-next, but does not verify the 3 missing files (monaco-evk.dts, monaco.dtsi, qcs8300-ride.dts) because they are not part of this PR

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

Commit Subject qcom-next topics Final
1/1 [PATCH] FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and present - all checked added lines are present skipped - not checked because qcom-next already contains the change present

Final Status

overall_status: PASS
present_commits: 1/1
partial_commits: 0/1
missing_commits: 0/1
topics_checked_for_commits: 0/1
final_summary: PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

@qlijarvis

Copy link
Copy Markdown

PR #1327 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ❌ Fixes tag format issue
dt-binding-check ⏭️ No binding changes
dtb-check ✅ Test passed
sparse-check ⏭️ No C/H changes
check-uapi-headers ⏭️ No UAPI changes
check-patch-compliance ❌ Content mismatch with lore link
tag-check ✅ Valid FROMLIST: prefix present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1327 - FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and refgen supply for PCIe PHYs
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/40298861139

Checker Result Summary
checkpatch ❌ Fixes tag format issue
dt-binding-check ⏭️ No binding changes
dtb-check ✅ Test passed
sparse-check ⏭️ No C/H changes
check-uapi-headers ⏭️ No UAPI changes
check-patch-compliance ❌ Content mismatch with lore link
tag-check ✅ Valid FROMLIST: prefix present

❌ checkpatch

Root cause: Fixes tag does not include the required prefix from the original commit subject.

Failure details:

WARNING: Please use correct Fixes: style 'Fixes: <12+ chars of sha1> ("<title line>")' - ie: 'Fixes: 8f398ed3e896 ("UPSTREAM: arm64: dts: qcom: Add Monaco Monza SoM")'
#14: 
Fixes: 8f398ed3e896 ("arm64: dts: qcom: Add Monaco Monza SoM")

cfc48522feb8de142121a3eee90e814ba80f324c total: 0 errors, 1 warnings, 0 checks, 16 lines checked

The Fixes tag references commit 8f398ed3e896 whose actual subject line is "UPSTREAM: arm64: dts: qcom: Add Monaco Monza SoM" (includes the UPSTREAM: prefix), but the Fixes tag omits the prefix.

Fix:

git rebase -i 8eea647b71f0d9cf21f064fe71d2c68f5fb4ae39   # mark commit as 'edit'
# Edit the commit message to update the Fixes line:
# Change:
#   Fixes: 8f398ed3e896 ("arm64: dts: qcom: Add Monaco Monza SoM")
# To:
#   Fixes: 8f398ed3e896 ("UPSTREAM: arm64: dts: qcom: Add Monaco Monza SoM")
git commit --amend
git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 8eea647b71f0d9cf21f064fe71d2c68f5fb4ae39..HEAD

❌ check-patch-compliance

Root cause: The patch content in the PR differs from the upstream patch referenced in the Link trailer.

Failure details:

Checking commit: FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and refgen supply for PCIe PHYs
Change is different from the one mentioned in Link

The checker fetched the upstream patch from the lore link:

Link: https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/

and found that the PR patch content does not match the upstream version exactly.

Fix:

  1. Fetch the upstream patch to compare:

    b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/ -o /tmp/upstream
  2. Compare the differences between the PR patch and upstream:

    git format-patch -1 cfc48522feb8 --stdout > /tmp/pr.patch
    diff -u /tmp/upstream/*.mbx /tmp/pr.patch
  3. Determine the nature of the mismatch:

    • Context-only shift (line numbers changed but code is identical) → Not a real issue; may be acceptable
    • Legitimate adaptation (e.g., different base tree structure) → Document the reason in commit message
    • Missing hunk → Add the missing changes
    • Extra hunk → Remove or attribute separately
  4. If the patch needs to match upstream exactly, cherry-pick from the upstream mbox:

    git am /tmp/upstream/*.mbx
  5. If the patch is intentionally different (e.g., backport adaptation), document the differences in the commit message body before the Link trailer:

    [ Upstream commit <sha> ]
    
    Adapted for qcom-6.18.y: <explain differences>
    
    Link: https://lore.kernel.org/all/...
    

Reproduce locally:

cd /path/to/kernel
bash ../kernel-checkers/check-patch-compliance.sh --kernel-src . --base 8eea647b71f0d9cf21f064fe71d2c68f5fb4ae39 --head HEAD

Verdict

2 blockers must be fixed before merge:

  1. checkpatch: Update Fixes tag to include the UPSTREAM: prefix in the referenced commit subject
  2. check-patch-compliance: Resolve content mismatch with upstream lore patch — either align the patch exactly with upstream or document the adaptation reason in the commit message

Both issues are in the commit metadata (Fixes tag format and content alignment with upstream). The code changes themselves are valid (dtb-check passed).

@qlijarvis

Copy link
Copy Markdown

PR #1327 — validate-patch

PR: #1327

Verdict Issues Detailed Report
❌ 8 Full report

Final Summary

  1. Lore link present: Yes — https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/
  2. Lore link matches PR commits: No — PR contains only 1 of 4 files from the upstream patch; missing monaco.dtsi (SoC-level refgen-supply), monaco-evk.dts, and qcs8300-ride.dts
  3. Upstream patch status: ⏳ Decision Pending — posted 2026-09-16, author pinged maintainers 2026-10-13, no ACK/NAK/merge confirmation visible in thread
  4. PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1327 - FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and refgen supply for PCIe PHYs
Upstream commit: https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream ⚠️ PR subject mentions only monaco-monza-som; upstream patch modifies 4 files across QCS8300 platform
Body preserves rationale ⚠️ PR body omits critical context: upstream patch adds supplies to 3 board files + SoC DTSI; PR commit message doesn't explain why only monaco-monza-som is included
Fixes tag present/correct ✅ Fixes tag present and references correct commit
Authorship preserved ✅ Author matches lore patch (FROMLIST: allows submitter to differ)
Backport note (if applicable) N/A FROMLIST: prefix used correctly

Diff

File Status Notes
arch/arm64/boot/dts/qcom/monaco-monza-som.dtsi ✅ Hunks match lore patch exactly
arch/arm64/boot/dts/qcom/monaco-evk.dts ❌ Missing - present in lore patch, absent from PR
arch/arm64/boot/dts/qcom/monaco.dtsi ❌ Missing - present in lore patch (refgen-supply for SoC), absent from PR
arch/arm64/boot/dts/qcom/qcs8300-ride.dts ❌ Missing - present in lore patch, absent from PR

Issues

Critical: Incomplete backport

The PR links to lore patch v2 3/4 which modifies 4 files to add qref/refgen supplies across the QCS8300 platform:

  • monaco-evk.dts (board file)
  • monaco-monza-som.dtsi (board file) ← only this file is in the PR
  • monaco.dtsi (SoC DTSI - adds refgen-supply to pcie0_phy and pcie1_phy nodes)
  • qcs8300-ride.dts (board file)

The PR contains only the monaco-monza-som.dtsi changes (1 of 4 files). The upstream commit message explicitly states:

"Add vdda-qref-supply and vdda-refgen-supply in the board files (QCS8300-RIDE, Monaco-EVK and Monaco-Monza-SoM), and add refgen-supply in the SoC DTSI (monaco.dtsi) since refgen is an on-chip regulator shared across boards."

Missing critical SoC-level change:
The monaco.dtsi change adds refgen-supply = <&refgen>; to the PHY nodes at the SoC level. Without this, the board-level vdda-refgen-supply properties may not function correctly, as the upstream commit message notes this is a workaround for a hardware issue where "QREF actually depends on refgen3 rather than refgen2 as documented."

Fixes tags mismatch:
The PR Fixes tag references only 8f398ed3e896 ("UPSTREAM: arm64: dts: qcom: Add Monaco Monza SoM"). The upstream patch has 4 Fixes tags covering all affected board files:

  • Fixes: 33967eadb215 ("arm64: dts: qcom: qcs8300-ride: enable pcie0 interface")
  • Fixes: cdb613a84527 ("arm64: dts: qcom: qcs8300-ride: enable pcie1 interface")
  • Fixes: 41e2424651f7 ("arm64: dts: qcom: monaco-evk: Enable PCIe0 and PCIe1.")
  • Fixes: 5238f4e7169f ("arm64: dts: qcom: Add Monaco Monza SoM")

Verdict

Do not merge. This PR is an incomplete backport of the upstream patch. The missing files (monaco.dtsi, monaco-evk.dts, qcs8300-ride.dts) are essential for the fix to work correctly across the QCS8300 platform. The SoC-level refgen-supply in monaco.dtsi is particularly critical as it implements the hardware workaround described in the upstream commit message.

Required action: Either:

  1. Split the upstream patch correctly - if only monaco-monza-som needs the fix in this tree, create a new commit with a commit message explaining why this is a partial backport and why the other files are not needed, OR
  2. Include all 4 files - backport the complete upstream patch with all board files and the SoC DTSI change

Final Summary

  1. Lore link present: Yes — https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/
  2. Lore link matches PR commits: No — PR contains only 1 of 4 files from the upstream patch; missing monaco.dtsi (SoC-level refgen-supply), monaco-evk.dts, and qcs8300-ride.dts
  3. Upstream patch status: ⏳ Decision Pending — posted 2026-09-16, author pinged maintainers 2026-10-13, no ACK/NAK/merge confirmation visible in thread
  4. PR present in qcom-next/topics: Yes — integration_presence_report.md shows all checked lines are present in qcom-next (commit c7896917e523)

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

Commit Subject qcom-next topics Final
1/1 [PATCH] FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and present - all checked added lines are present skipped - not checked because qcom-next already contains the change present

Final Status

overall_status: PASS
present_commits: 1/1
partial_commits: 0/1
missing_commits: 0/1
topics_checked_for_commits: 0/1
final_summary: PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

@qlijarvis

Copy link
Copy Markdown

PR #1327 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ✅ No style issues
dt-binding-check ⏭️ Skipped (no binding changes)
dtb-check ✅ No DTB validation errors
sparse-check ⏭️ Skipped (no C/H changes)
check-uapi-headers ⏭️ Skipped (no UAPI changes)
check-patch-compliance ❌ Content mismatch with upstream link
tag-check ✅ Valid FROMLIST: prefix present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1327 - FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and refgen supply for PCIe PHYs
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/40303034038

Checker Result Summary
checkpatch ✅ No style issues
dt-binding-check ⏭️ Skipped (no binding changes)
dtb-check ✅ No DTB validation errors
sparse-check ⏭️ Skipped (no C/H changes)
check-uapi-headers ⏭️ Skipped (no UAPI changes)
check-patch-compliance ❌ Content mismatch with upstream link
tag-check ✅ Valid FROMLIST: prefix present

❌ check-patch-compliance

Root cause: The patch content differs from the upstream version referenced in the Link: trailer.

Failure details:

Checking commit: FROMLIST: arm64: dts: qcom: monaco-monza-som: Add qref and refgen supply for PCIe PHYs
Change is different from the one mentioned in Link

Analysis:

The checker detected that the patch in this PR differs from the upstream patch at:
https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/

This can occur for several reasons:

  1. Context-only differences — surrounding lines changed but the actual modification is identical (common false positive)
  2. Legitimate adaptation — patch was modified for the target tree (e.g., different base, additional changes)
  3. Missing/extra hunks — incomplete backport or additional fixes bundled together
  4. Wrong link — the Link: trailer points to a different version of the patch

Fix:

  1. Verify the difference is real:

    # Fetch the upstream patch
    b4 am --single-message -C -l -3 \
      https://lore.kernel.org/all/20260916102023.2054761-4-ziyue.zhang@oss.qualcomm.com/ \
      -o /tmp/upstream
    
    # Compare the actual code changes (ignoring context)
    git format-patch -1 ce211e5bd0fd --stdout | \
      awk '/^diff/,/^--$/' | grep -E '^[+-][^+-]' > /tmp/pr.diff
    
    awk '/^diff/,/^--$/' /tmp/upstream/*.mbx | \
      grep -E '^[+-][^+-]' > /tmp/upstream.diff
    
    diff /tmp/pr.diff /tmp/upstream.diff
  2. If the difference is real:

    • Option A: If this is an intentional adaptation, document it in the commit message:
      [ upstream commit description ]
      
      (cherry picked from https://lore.kernel.org/...)
      [ Adapted for qcom-6.18.y: <explain what changed and why> ]
      
    • Option B: If the upstream patch is correct, update the PR to match it exactly
    • Option C: If the Link is wrong, update it to point to the correct upstream version
  3. If the difference is context-only (false positive):

    • This is a known checker limitation when surrounding code differs between trees
    • The patch is acceptable as-is; note this in the PR review

Reproduce locally:

cd /path/to/kernel
bash ../kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base 8eea647b71f0d9cf21f064fe71d2c68f5fb4ae39 \
  --head ce211e5bd0fdc422136f67c5493c88a88f52035c

Verdict

1 blocker to address before merge:

The check-patch-compliance content mismatch must be investigated. If the difference is intentional (adaptation for the target tree), document it in the commit message. If it's a mistake, either fix the patch to match upstream or update the Link: trailer to point to the correct version.

All other checkers passed or correctly skipped. The patch has proper FROMLIST: prefix, clean checkpatch style, and no DTB validation errors.

@qcomlnxci

Copy link
Copy Markdown

Test Matrix

Test Case kbdev-hamoa-iot-evk-multimedia kbdev-lemans-evk-multimedia kbdev-monaco-evk-multimedia kbdev-purwa-iot-evk-multimedia kbdev-qcs615-ride-multimedia kbdev-qcs6490-rb3gen2-multimedia kbdev-qcs8300-ride-multimedia kbdev-qcs9100-ride-r3-multimedia kbdev-shikra-iqs-evk-multimedia
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 ❌ Fail ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ❌ Fail
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 ✅ Pass ❌ Fail ❌ Fail ❌ Fail
KVM_EL2_DTB ❌ Fail ✅ Pass ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ❌ Fail
KVM_Infra ❌ Fail ✅ Pass ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ❌ Fail
OpenCV ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
PCIe ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ❌ Fail
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 ⚠️ skip ❌ Fail ✅ Pass ❌ 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 ❌ Fail ✅ 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

@qcomlnxci

Copy link
Copy Markdown

Test Matrix

Test Case kbdev-hamoa-iot-evk-multimedia kbdev-lemans-evk-multimedia kbdev-monaco-evk-multimedia kbdev-purwa-iot-evk-multimedia kbdev-qcs615-ride-multimedia kbdev-qcs6490-rb3gen2-multimedia kbdev-qcs8300-ride-multimedia kbdev-qcs9100-ride-r3-multimedia kbdev-shikra-iqs-evk-multimedia
Audio_Card_Registration ✅ Pass ◻️ ✅ Pass ✅ Pass ⚠️ skip ✅ 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 ◻️ ❌ Fail ✅ 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_Basic_Validation ⚠️ skip ◻️ ✅ Pass ⚠️ skip ⚠️ skip ⚠️ skip ❌ Fail ⚠️ skip ⚠️ skip
Freq_Scaling ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ❌ Fail ✅ Pass ✅ Pass ✅ Pass
GIC ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ❌ Fail ✅ 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 ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ❌ Fail
KVM_EL2_DTB ❌ Fail ◻️ ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ❌ Fail
KVM_Infra ❌ Fail ◻️ ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ❌ Fail
OpenCV ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
PCIe ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ❌ Fail
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 ⚠️ skip ✅ Pass ✅ Pass ❌ Fail
WiFi_Firmware_Driver ✅ Pass ◻️ ❌ Fail ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
WiFi_OnOff ✅ Pass ◻️ ❌ Fail ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⚠️ skip
adsp_remoteproc ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⚠️ skip
cdsp_remoteproc ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ❌ Fail ✅ Pass ✅ Pass ✅ Pass
gpdsp_remoteproc ⚠️ skip ◻️ ✅ Pass ⚠️ skip ⚠️ 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 ◻️
rngtest ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
shmbridge ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
smmu ❌ Fail ◻️ ✅ Pass ❌ Fail ❌ Fail ✅ Pass ✅ Pass ❌ Fail ✅ Pass
watchdog ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
wpss_remoteproc ✅ Pass ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass

@sgaud-quic

Copy link
Copy Markdown
Contributor

ziyuezhang-123 please get approval on the latest pushed commit

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants