Enable IPCB for Hamoa and Glymur by jiegan0107 · Pull Request #602 · qualcomm-linux/kernel

Jie Gan (jiegan0107) · 2026-05-19T14:01:04Z

Enable IPCB for Hamoa and Glymur in SoC staging DT

CRs-Fixed: 4542084

qswat-orbit-external · 2026-05-19T14:01:17Z

Merge Check Failed: CR Not Eligible for Merge

CR 4542084 is not eligible for merge.

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

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

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

knaveen-qc · 2026-05-20T01:56:57Z

PR #602 — validate-patch

PR:#602

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

Lore link present: Not provided in agent output
Lore link matches PR commits: Not provided in agent output
Upstream patch status: Not provided in agent output
PR present in qcom-next: Not provided in agent output

Verdict: ⚠️ — click to expand
🔍 Patch Validation
PR: qualcomm-linux/kernel #602 — arm64: dts: qcom: add TGU/ETR/Coresight staging overlays (glymur, hamoa, sm8750, kaanapali)
Upstream commit: N/A — all 5 commits carry PENDING: prefix; no lore.kernel.org link present or expected
Verdict:⚠️ PARTIAL (N/A for lore validation; vendor-staging commits assessed on commit-message hygiene only)
Commit 1 of 5 — PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
Commit Message
Check Status Note
Subject matches upstream N/A PENDING: — no upstream to compare
Body preserves rationale ✅ Brief but adequate: mentions IPCB and DDR memory trace
Fixes tag present/correct N/A New feature, no bug fix
Authorship preserved ✅ Single author; Signed-off-by matches From:
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds glymur-staging.dtbo entry correctly
arch/arm64/boot/dts/qcom/glymur-staging.dtso ✅ New file; TGU + ETR + replicator + CTCU nodes look self-consistent
Issues
None for commit-message or diff correctness.
Verdict
Acceptable as a vendor-staging commit; no lore link required for PENDING: prefix.
Final Summary
Lore link present: No — PENDING: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only staging change, not posted upstream
PR present in qcom-next: Not checked — PENDING: vendor-only commit
Commit 2 of 5 — PENDING: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block
Commit Message
Check Status Note
Subject matches upstream N/A PENDING: — no upstream to compare
Body preserves rationale ✅ Lists device types added (ETM, replicator, funnel, TMC ETF)
Fixes tag present/correct N/A New feature
Authorship preserved ✅ From: matches Signed-off-by:
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/glymur-staging.dtso ✅ Large addition (1248 lines); 18 ETEs, 3 NCC clusters, funnels, replicators, TMC ETFs — topology appears internally consistent
Issues
None for commit-message or diff correctness.
Verdict
Acceptable as a vendor-staging commit; no lore link required for PENDING: prefix.
Final Summary
Lore link present: No — PENDING: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only staging change, not posted upstream
PR present in qcom-next: Not checked — PENDING: vendor-only commit
Commit 3 of 5 — PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso
Commit Message
Check Status Note
Subject matches upstream N/A PENDING: — no upstream to compare
Body preserves rationale ✅ Mentions IPCB feature
Fixes tag present/correct N/A New feature
Authorship preserved ✅ From: matches Signed-off-by:
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds hamoa-staging.dtbo entry correctly
arch/arm64/boot/dts/qcom/hamoa-staging.dtso ✅ New file; 3 TGU nodes at 0x10b0e000–0x10b10000, consistent structure
Issues
None for commit-message or diff correctness.
Verdict
Acceptable as a vendor-staging commit; no lore link required for PENDING: prefix.
Final Summary
Lore link present: No — PENDING: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only staging change, not posted upstream
PR present in qcom-next: Not checked — PENDING: vendor-only commit
Commit 4 of 5 — PENDING: arm64: dts: qcom: sm8750: add TGU in staging dtso
Commit Message
Check Status Note
Subject matches upstream N/A PENDING: — no upstream to compare
Body preserves rationale ✅ Mentions IPCB feature
Fixes tag present/correct N/A New feature
Authorship preserved ✅ From: matches Signed-off-by:
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds sm8750-staging.dtbo entry correctly
arch/arm64/boot/dts/qcom/sm8750-staging.dtso ⚠️ New file; 3 TGU nodes at 0x10b0e000–0x10b10000 — identical addresses to hamoa-staging.dtso (commit 3); may be intentional if both boards share the same SoC TGU layout, but worth confirming
Issues
⚠️sm8750-staging.dtso and hamoa-staging.dtso define TGU nodes at the exact same physical addresses (0x10b0e000, 0x10b0f000, 0x10b10000). If hamoa and sm8750 are different SoCs this is suspicious and should be verified against the respective TRM/hardware spec.
Verdict
Acceptable as a vendor-staging commit pending address-range confirmation; no lore link required for PENDING: prefix.
Final Summary
Lore link present: No — PENDING: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only staging change, not posted upstream
PR present in qcom-next: Not checked — PENDING: vendor-only commit
Commit 5 of 5 — PENDING: arm64: dts: qcom: kaanapali: add TGU in staging dtso
Commit Message
Check Status Note
Subject matches upstream N/A PENDING: — no upstream to compare
Body preserves rationale ✅ Mentions IPCB feature
Fixes tag present/correct N/A New feature
Authorship preserved ✅ From: matches Signed-off-by:
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds kaanapali-staging.dtbo entry correctly
arch/arm64/boot/dts/qcom/kaanapali-staging.dtso ✅ New file; 4 TGU nodes at distinct addresses (0x11301000, 0x1130e000–0x11310000), consistent structure
Issues
None for commit-message or diff correctness.
Verdict
Acceptable as a vendor-staging commit; no lore link required for PENDING: prefix.
Final Summary
Lore link present: No — PENDING: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only staging change, not posted upstream
PR present in qcom-next: Not checked — PENDING: vendor-only commit
Overall PR Summary
PR #602 contains 5 commits, all prefixed PENDING:. Lore validation is not applicable by design for this prefix. Commit-message hygiene is clean across all 5 commits. One minor concern is flagged on commit 4 (sm8750 TGU addresses identical to hamoa), which should be verified against hardware documentation before merging.
Commit Prefix Lore Link Verdict
glymur: add TGU and ETR in staging dtso PENDING: None (expected) ✅ N/A
glymur: add Coresight devices for APSS debug block PENDING: None (expected) ✅ N/A
hamoa: add TGU in staging dtso PENDING: None (expected) ✅ N/A
sm8750: add TGU in staging dtso PENDING: None (expected) ⚠️ Address overlap with hamoa
kaanapali: add TGU in staging dtso PENDING: None (expected) ✅ N/A

knaveen-qc · 2026-05-20T01:56:58Z

PR #602 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	All 5 commits clean — 0 errors, 0 warnings, 0 checks
dt-binding-check	⏭️	No changes in `Documentation/devicetree/bindings` — skipped
dtb-check	✅	Log Summary: Test passed — no new DTB errors introduced by PR
sparse-check	⏭️	No C/H file changes — skipped
check-uapi-headers	⏭️	No relevant file changes — skipped
check-patch-compliance	❌	All 5 commits fail: `PENDING:` is not an allowed prefix
tag-check	✅	All 5 commits carry `PENDING:` — valid tag-check prefix
qcom-next-check	N/A	PR targets `qcom-6.18.y`, not `qcom-next`

Detailed report: Full report

Checker analysis — click to expand
🤖 CI Checker Analysis (checker-log-analyzer)
PR:#602 — arm64: dts: qcom: add TGU/ETR/Coresight staging dtso nodes
Source:https://github.com/qualcomm-linux/kernel-config/actions/runs/26135626742
Target branch:qcom-6.18.y (not qcom-next / qcom-next-staging)
Head SHA:02eeba05fc7c3ced8283ae82c9beed288d1a8c84
Base SHA:0136c1ed9c23851783df4ad39ad3556497cc3c2a
Checker Result Summary
checkpatch ✅ All 5 commits clean — 0 errors, 0 warnings, 0 checks
dt-binding-check ⏭️ No changes in Documentation/devicetree/bindings — skipped
dtb-check ✅ Log Summary: Test passed — no new DTB errors introduced by PR
sparse-check ⏭️ No C/H file changes — skipped
check-uapi-headers ⏭️ No relevant file changes — skipped
check-patch-compliance ❌ All 5 commits fail: PENDING: is not an allowed prefix
tag-check ✅ All 5 commits carry PENDING: — valid tag-check prefix
qcom-next-check N/A PR targets qcom-6.18.y, not qcom-next
❌ check-patch-compliance
Root cause: All 5 commits use the PENDING: subject prefix, which is not in the check-patch-compliance allowed list (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:).
Failure details:
Checking commit: PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
Commit summary does not start with a required prefix
Checking commit: PENDING: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block
Commit summary does not start with a required prefix
Checking commit: PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso
Commit summary does not start with a required prefix
Checking commit: PENDING: arm64: dts: qcom: sm8750: add TGU in staging dtso
Commit summary does not start with a required prefix
Checking commit: PENDING: arm64: dts: qcom: kaanapali: add TGU in staging dtso
Commit summary does not start with a required prefix
##[error]Process completed with exit code 1.
Root cause analysis:
PENDING: is a known vendor-internal prefix that check-patch-compliance does not accept. This checker expects patches to have an upstream lore.kernel.org Link: tag and a prefix indicating upstream disposition (FROMLIST:, FROMGIT:, UPSTREAM:, or BACKPORT:). PENDING: patches by definition have no upstream link yet, so this checker will always fail for them — this is a known checker limitation for vendor-only / not-yet-posted patches.
Fix options:
Scenario Action
Patches have been posted to lore.kernel.org Change prefix to FROMLIST: and add Link: <lore-url> to each commit body
Patches are not yet posted upstream Keep PENDING: — check-patch-compliance failure is expected and accepted for this prefix; no patch change needed
If the patches are genuinely not yet posted upstream, this failure is a known false-positive for PENDING: commits and can be waived. If they have been posted, update the prefix and add the Link: tag:
git rebase -i 0136c1ed9c23 # mark each commit as 'edit'# For each commit:
git commit --amend # change PENDING: → FROMLIST: and add Link: <lore-url>
git rebase --continue
Reproduce locally:
bash kernel-checkers/check-patch-compliance.sh \
--kernel-src <path/to/kernel> \
--base 0136c1ed9c23851783df4ad39ad3556497cc3c2a \
--head 02eeba05fc7c3ced8283ae82c9beed288d1a8c84
ℹ️ dtb-check — PASS with pre-existing warnings (informational)
The dtb-check log contains many reg_format warnings in hamoa-camera.dtsi and talos-evk-lvds-auo,g133han01.dtso, but these are pre-existing tree-wide issues not introduced by this PR. The checker's base-vs-head diff found no new errors and reported "Log Summary: Test passed". No action required.
Verdict
1 blocker:check-patch-compliance fails on all 5 commits due to PENDING: prefix.
If these patches are not yet posted upstream → this is a known limitation; the failure can be waived and the PR is otherwise ready to merge (checkpatch ✅, dtb-check ✅, tag-check ✅).
If these patches have been posted to lore → update each commit to FROMLIST: + add Link: <lore-url> before merging.

qcomlnxci · 2026-05-20T04:57:52Z

Test jobs on 02eeba0

qcomlnxci · 2026-05-20T04:57:55Z

Test Matrix

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

knaveen-qc · 2026-05-20T05:21:57Z

LAVA Failed Case Triage Summary

PR: #602

Job 103202 | SoC qcs8300-ride

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

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

Case 1: ** Probe_Failure_Check
Failed case: ** Probe_Failure_Check
Root cause: ** Two pre-existing driver probe/firmware errors on qcs8300-ride-sx triggered the Probe_Failure_Check scanner: (1) Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22 — the qcs8300-ride PHY DT node at MDIO address 0x08 is missing the mandatory firmware-name property required by the Aquantia AQR115C driver, causing a hard -EINVAL probe failure; (2) faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2 — the regulatory.db file is absent from the rootfs, causing cfg80211 to fail its firmware load. Neither failure is introduced by PR Enable IPCB for Hamoa and Glymur #602, which only modifies staging DT overlays for glymur/hamoa/sm8750/kaanapali platforms.
Possible fix: Add the missing firmware-name property to the Aquantia AQR115C PHY node in the qcs8300-ride DTS/DTSO, and ensure regulatory.db is included in the qcs8300-ride-sx rootfs image (or add both signatures to the Probe_Failure_Check allowlist if they are known-benign for this board configuration).
Detail analysis attachment: failed_case_job103202_1_detailed.md

Case 2: ** USBHost
Failed case: ** USBHost
Root cause: ** No physical USB peripheral device is connected to the qcs8300-ride board's USB host port in the LAVA lab; lsusb enumeration returns only the Linux Foundation 2.0 root hub (ID 1d6b:0002), which is the xHCI controller's own virtual hub — the test script correctly identifies this as "Only USB hubs detected, no functional USB devices" and fails.
Possible fix: Attach a functional USB peripheral (e.g., USB storage or HID device) to the qcs8300-ride board's USB host port in the LAVA lab infrastructure, or mark USBHost as a known infra-dependent test and skip it when no USB device is physically present on this board.
Detail analysis attachment: failed_case_job103202_2_detailed.md

Case 3: ** shmbridge — Suppressed (Known Benign: shmbridge CI noise)
Failed case: ** shmbridge — Suppressed (Known Benign: shmbridge CI noise)
Root cause: ** The shmbridge test script greps the current-boot kernel log for any string matching qcom_scm and flags a failure if any match is found; the kernel command line itself contains qcom_scm.download_mode=1, which is always present on qcs8300-ride-sx and unconditionally triggers the test's error-detection heuristic — this is a known false-positive in the CI environment unrelated to any kernel regression.
Possible fix: No action required — suppress this result per Rule 1 of lava-known-benign-failures.md; the shmbridge test is known CI infrastructure noise and does not indicate a kernel defect on qcs8300-ride or any other platform.
Detail analysis attachment: failed_case_job103202_3_detailed.md

Case 4: ** `0_qcom-next-ci-premerge-tests` — Suppressed (Known Benign: shmbridge CI noise)
Failed case: ** 0_qcom-next-ci-premerge-tests — Suppressed (Known Benign: shmbridge CI noise)
Root cause: ** The LAVA dispatcher marked the overall test definition as failed ("Marking unfinished test run as failed") because result_parse.sh found shmbridge.res containing a FAIL result; the shmbridge test itself failed because its run.sh matched the kernel command line string qcom_scm.download_mode=1 as a qcom_scm-related error in the boot log — a known false-positive pattern on qcs8300-ride that is always suppressed per Rule 1 of the known-benign failure policy.
Possible fix: No action required on the PR; suppress the shmbridge failure per Rule 1 (always suppress). If the shmbridge test script is accessible, fix its qcom_scm error-scan regex to exclude the kernel command line string (qcom_scm.download_mode=) from its error pattern match to prevent future false positives.
Detail analysis attachment: failed_case_job103202_4_detailed.md

Job 103203 | SoC qcs6490-rb3gen2

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

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

Case 1: ** Probe_Failure_Check
Failed case: ** Probe_Failure_Check
Root cause: ** Two pre-existing firmware-load failures in dmesg triggered the check: regulatory.db (ENOENT, cfg80211 regulatory database absent from CI rootfs) and renesas_usb_fw.mem (ENOENT, Renesas USB PCIe controller firmware absent from CI rootfs), both unrelated to the PR's DTS-only changes targeting glymur/hamoa/sm8750/kaanapali platforms.
Possible fix: Add regulatory.db (from wireless-regdb) and renesas_usb_fw.mem (from linux-firmware) to the CI rootfs image used for qcs6490-rb3gen2 LAVA jobs, or add suppression rules for these two known-benign firmware-absent probe failures in the Probe_Failure_Check test script.
Detail analysis attachment: failed_case_job103203_1_detailed.md

Case 2: ** Driver Probe Failure — xhci-pci-renesas firmware missing
Failed case: ** Driver Probe Failure — xhci-pci-renesas firmware missing
Root cause: ** The Renesas USB 3.0 xHCI PCIe host controller (PCI ID 1912:0014, slot 0001:04:00.0) present on the qcs6490-rb3gen2 board failed to probe because the required firmware file renesas_usb_fw.mem is absent from the rootfs image (-ENOENT, errno -2), leaving no functional USB host controller and causing the USBHost test to report "No USB devices found."
Possible fix: Add the Renesas xHCI firmware file (renesas_usb_fw.mem) to the rootfs image used for qcs6490-rb3gen2 CI runs (typically under /lib/firmware/), or suppress the xhci-pci-renesas driver probe on this board if the Renesas PCIe USB card is not a required test peripheral, by adding a kernel config or DT quirk to skip it.
Detail analysis attachment: failed_case_job103203_2_detailed.md

Case 3: ** shmbridge — Suppressed (Known Benign: CI Infrastructure Noise)
Failed case: ** shmbridge — Suppressed (Known Benign: CI Infrastructure Noise)
Root cause: ** The shmbridge test script performs a broad grep for any qcom_scm-related string in the current-boot kernel log and flags the pre-existing informational message qcom_scm firmware:scm: qseecom: untested machine, skipping as an error; this is a known false-positive in the CI environment on qcs6490-rb3gen2 and does not indicate any kernel regression.
Possible fix: No action required — suppress this result per Rule 1 of lava-known-benign-failures.md; the shmbridge test is known CI noise and must not be treated as a PR-introduced failure.
Detail analysis attachment: failed_case_job103203_3_detailed.md

Case 4: ** `0_qcom-next-ci-premerge-tests`
Failed case: ** 0_qcom-next-ci-premerge-tests
Root cause: ** Three sub-tests within the qcom-next-ci-premerge-tests suite reported RESULT=FAIL on the qcs6490-rb3gen2 board: (1) Probe_Failure_Check — triggered by two benign kernel probe errors (faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2 and xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2); (2) shmbridge — triggered by the qcom_scm firmware:scm: qseecom: untested machine, skipping message being matched as a qcom_scm-related error in the kernel log; (3) USBHost — no USB devices found on the board. These failures caused LAVA to mark the overall test run as failed ("Marking unfinished test run as failed") because the test runner exited with sub-test failures outstanding. The PR itself (5 patches adding DTS overlays for glymur/hamoa/sm8750/kaanapali staging — TGU/ETR/Coresight nodes) does not touch qcs6490, qcom_scm, USB host, or regulatory firmware paths, so these failures are pre-existing and PR-unrelated.
Possible fix: These are pre-existing, board-environment failures unrelated to the PR; add Probe_Failure_Check, shmbridge, and USBHost to the known-benign suppression list for qcs6490-rb3gen2 in the CI test runner configuration, or re-trigger the job to confirm reproducibility before blocking the PR.
Detail analysis attachment: failed_case_job103203_4_detailed.md

Job 103204 | SoC lemans-evk

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

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

Case 1: ** Probe_Failure_Check
Failed case: ** Probe_Failure_Check
Root cause: ** The test scanner found 3 Direct firmware load ... failed with error -2 dmesg entries (Bluetooth qca/wcnhpbtfw21.tlv, qca/hpbtfw21.tlv, and regulatory.db) and flagged them as probe failures; however, all three are known-benign false positives — BT_ON_OFF=PASS and WiFi_OnOff=PASS confirm both subsystems loaded their firmware and functioned correctly at runtime, and no deferred probes were outstanding.
Possible fix: Suppress this Probe_Failure_Check result as a known-benign false positive per lava-known-benign-failures Rules 2 & 3; update the Probe_Failure_Check test script to cross-reference BT_ON_OFF and WiFi_OnOff functional test results before flagging firmware-load dmesg lines as failures, or add qca/wcnhpbtfw21.tlv, qca/hpbtfw21.tlv, and regulatory.db to the test's firmware-load allowlist for lemans-evk (iq-9075-evk).
Detail analysis attachment: failed_case_job103204_1_detailed.md

Case 2: ** smmu
Failed case: ** smmu
Root cause: ** The smmu test script's critical-master IOMMU attachment check fails because two devices — aa00000.video-codec (Video codec) and interconnect-lpass-ag-noc (Audio LPASS interconnect) — are not attached to any IOMMU group on the lemans-evk (SA8775P/IQ-9075-EVK) board; no SMMU fault or kernel error is present, and the failure is pre-existing and unrelated to this PR's DTS changes (which only affect glymur/hamoa/sm8750/kaanapali platforms).
Possible fix: Update the smmu test script's critical-master list to exclude aa00000.video-codec and interconnect-lpass-ag-noc for the lemans-evk platform (or mark them as non-critical/optional), as these devices are known to not have IOMMU group attachments on SA8775P; alternatively, add the missing iommus property to the aa00000.video-codec and interconnect-lpass-ag-noc DT nodes in the SA8775P/lemans DTS if IOMMU protection is required.
Detail analysis attachment: failed_case_job103204_2_detailed.md

Case 3: ** USBHost
Failed case: ** USBHost
Root cause: ** The USBHost test script requires at least one non-hub USB peripheral to be physically connected to the lemans-evk board's USB host port; at test time only two Genesys Logic hubs (ID 05e3:0610 USB 2.0, ID 05e3:0625 USB 3.1) were enumerated on buses 1 and 2, with no functional USB device present — the xhci-hcd controller and hub chain are fully operational.
Possible fix: Attach a functional USB peripheral device (e.g. USB mass-storage stick or USB-to-serial adapter) to the lemans-evk board's USB host port in the LAVA lab setup so the USBHost test can detect a non-hub device; this is a lab infrastructure gap unrelated to the PR under test.
Detail analysis attachment: failed_case_job103204_3_detailed.md

Case 4: ** suppressed (known benign: shmbridge)
Failed case: ** suppressed (known benign: shmbridge)
Root cause: ** The shmbridge test script scanned the kernel log for any string matching qcom_scm and incorrectly flagged the benign boot-time message qcom_scm firmware:scm: qseecom: untested machine, skipping (and/or the kernel command-line parameter qcom_scm.download_mode=1) as a "qcom_scm-related error", triggering a false FAIL; per Rule 1 of the known-benign-failure suppressions, all shmbridge failures are unconditionally suppressed as CI infrastructure noise.
Possible fix: No action required — suppress this result per Rule 1; the shmbridge test is a known false-positive in this CI environment and does not indicate any kernel regression introduced by PR Enable IPCB for Hamoa and Glymur #602.
Detail analysis attachment: failed_case_job103204_4_detailed.md

Case 5: ** WiFi_Firmware_Driver — Suppressed (Known Benign: WiFi Firmware False Positive — WiFi ON/OFF Passed)
Failed case: ** WiFi_Firmware_Driver — Suppressed (Known Benign: WiFi Firmware False Positive — WiFi ON/OFF Passed)
Root cause: ** The WiFi_Firmware_Driver test probed ath12k module load state before the driver had fully initialised on the lemans-evk (IQ-9075) board; the paired functional test WiFi_OnOff passed, confirming WiFi firmware loaded and operated correctly at runtime — this is a known false positive per suppression Rule 2.
Possible fix: No fix required; suppress this result per the known-benign Rule 2 policy. If the test harness is generating noise, update the WiFi_Firmware_Driver test script to wait for driver initialisation to complete before checking module load state.
Detail analysis attachment: failed_case_job103204_5_detailed.md

Case 6: ** `0_qcom-next-ci-premerge-tests`
Failed case: ** 0_qcom-next-ci-premerge-tests
Root cause: ** The LAVA dispatcher marked the overall test action as failed ("Marking unfinished test run as failed") because the test runner exited with genuine sub-test failures: smmu (two critical masters — aa00000.video-codec and interconnect-lpass-ag-noc — missing IOMMU group attachment on lemans-evk/sa8795p), USBHost (only USB hubs detected, no functional USB devices), and Probe_Failure_Check (BT firmware files qca/wcnhpbtfw21.tlv and qca/hpbtfw21.tlv failed to load with error -2); all three are pre-existing platform issues on this board unrelated to the PR (which only modifies DTS for glymur, hamoa, sm8750, and kaanapali targets).
Possible fix: Re-trigger the CI job to confirm reproducibility; the three genuine sub-failures (smmu, USBHost, Probe_Failure_Check) are pre-existing on lemans-evk and should be baselined or suppressed in the test plan — specifically, add aa00000.video-codec and interconnect-lpass-ag-noc to the SMMU test's known-missing-iommu allowlist, investigate USB hub-only topology on this board, and add BT firmware files (qca/wcnhpbtfw21.tlv, qca/hpbtfw21.tlv) to the rootfs or suppress the Probe_Failure_Check entries for known-missing firmware.
Detail analysis attachment: failed_case_job103204_6_detailed.md

Job 103205 | SoC qcs9100-ride

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

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

Case 1: ** cdsp_remoteproc — Remoteproc Boot Failure (PAS/SCM authentication error)
Failed case: ** cdsp_remoteproc — Remoteproc Boot Failure (PAS/SCM authentication error)
Root cause: ** On qcs9100-ride (sa8775p "Lemans Ride Rev3"), qcom_scm logs qseecom: untested machine, skipping at boot (line 1399), leaving the PAS SCM interface uninitialized; every subsequent qcom_q6v5_pas call to qcom_scm_pas_init_image() returns -EINVAL (-22), preventing cdsp0 and cdsp1 from booting (state remains offline).
Possible fix: Add qcs9100 (sa8775p) to the qseecom tested-machine list in the qcom_scm driver (or ensure the correct SCM/PAS path is used for this SoC) so that pas_init_image succeeds and the CDSP subsystems can boot; this failure is pre-existing and not introduced by this PR.
Detail analysis attachment: failed_case_job103205_1_detailed.md

Case 2: ** Remoteproc Boot Failure — PAS/SCM Authentication Error
Failed case: ** Remoteproc Boot Failure — PAS/SCM Authentication Error
Root cause: ** All five sa8775p DSP subsystems (adsp, cdsp0, cdsp1, gpdsp0, gpdsp1) fail to boot on qcs9100-ride because qcom_q6v5_pas returns error -22 (EINVAL) during PAS firmware initialization; the root cause is qcom_scm firmware:scm: qseecom: untested machine, skipping at boot, which disables the qseecom-based SCM PAS authentication path for this SoC, causing every subsequent qcom_scm_pas_init_image() call to return -EINVAL.
Possible fix: Add sa8775p/qcs9100 to the qseecom machine allowlist in drivers/firmware/qcom/qcom_scm.c (or the equivalent qseecom init table) so that PAS authentication is enabled for this SoC; this failure is pre-existing and not introduced by this PR, so the PR can be merged independently while the SCM fix is tracked separately.
Detail analysis attachment: failed_case_job103205_2_detailed.md

Case 3: ** gpdsp_remoteproc — Remoteproc Boot Failure (PAS/SCM firmware init error -22)
Failed case: ** gpdsp_remoteproc — Remoteproc Boot Failure (PAS/SCM firmware init error -22)
Root cause: ** Both gpdsp0 (20c00000.remoteproc) and gpdsp1 (21c00000.remoteproc) fail to boot because qcom_q6v5_pas returns -22 (EINVAL) at the pas_init_image SCM call during firmware authentication/initialization of qcom/sa8775p/gpdsp0.mbn and gpdsp1.mbn; the SCM layer logs qseecom: untested machine, skipping for the qcs9100-ride SoC, indicating incomplete secure-side PAS support in this kernel build, and the same EINVAL pattern affects all DSPs (cdsp0, cdsp1, adsp) — this is a pre-existing platform issue not introduced by the PR.
Possible fix: This failure is pre-existing and unrelated to the PR (which only adds Coresight/TGU DT overlays for glymur/hamoa/sm8750/kaanapali); no action required on the PR — the gpdsp boot failure on qcs9100-ride should be tracked separately as a platform bring-up issue requiring alignment of the kernel's qseecom/PAS machine-ID support with the sa8775p/qcs9100 secure firmware.
Detail analysis attachment: failed_case_job103205_3_detailed.md

Case 4: ** Remoteproc Boot Failure — PAS/SCM firmware initialization error
Failed case: ** Remoteproc Boot Failure — PAS/SCM firmware initialization error
Root cause: ** All five sa8775p remoteproc subsystems (gpdsp0, gpdsp1, cdsp0, cdsp1, adsp) fail to boot because qcom_q6v5_pas returns error -22 (EINVAL) from pas_init_image; the SCM driver logs qcom_scm firmware:scm: qseecom: untested machine, skipping at boot, indicating the qseecom/PAS authentication path is not initialized for this qcs9100/sa8775p SoC variant in the kernel under test, causing every PAS firmware-load SCM call to be rejected with EINVAL.
Possible fix: This is a pre-existing platform issue unrelated to PR Enable IPCB for Hamoa and Glymur #602; add the qcs9100/sa8775p SoC to the qcom_scm qseecom tested-machine list (or ensure the correct SCM firmware-load path is selected for sa8775p in drivers/firmware/qcom/qcom_scm.c), then re-run the LAVA job to confirm all five remoteproc subsystems reach running state.
Detail analysis attachment: failed_case_job103205_4_detailed.md

Case 5: ** Probe_Failure_Check
Failed case: ** Probe_Failure_Check
Root cause: ** Two pre-existing probe/firmware errors on qcs9100-ride-sx triggered the test: (1) regulatory.db firmware file absent from rootfs (faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2), and (2) Aquantia AQR115C PHY at MDIO address stmmac-0:08 fails probe because the DT node lacks a valid firmware-name property (Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22). Neither failure is introduced by this PR.
Possible fix: Add regulatory.db to the qcs9100-ride-sx rootfs firmware package, and add or correct the firmware-name DT property in the stmmac-0:08 PHY node in the qcs9100-ride-sx (sa8775p-ride) DT; both are pre-existing platform issues unrelated to this PR's DT overlay additions for glymur/hamoa/sm8750/kaanapali.
Detail analysis attachment: failed_case_job103205_5_detailed.md

Case 6: ** smmu
Failed case: ** smmu
Root cause: ** The smmu test script on qcs9100-ride detected two critical DMA masters — aa00000.video-codec (video codec) and interconnect-lpass-ag-noc (audio LPASS interconnect) — not attached to any IOMMU group; aa00000.video-codec failed firmware initialization (error -22) so its IOMMU attach never completed, and interconnect-lpass-ag-noc has no iommus property in the qcs9100 DT, causing the test's critical-master coverage check to fail.
Possible fix: Verify whether aa00000.video-codec and interconnect-lpass-ag-noc are expected to be IOMMU-protected on qcs9100-ride; if so, fix the video-codec firmware path/PIL auth issue so the driver probes fully and attaches to its IOMMU group, and add the missing iommus property for interconnect-lpass-ag-noc in the qcs9100 DT — or update the smmu test's critical-master list to exclude masters that are intentionally unprotected on this platform.
Detail analysis attachment: failed_case_job103205_6_detailed.md

Case 7: ** USBHost
Failed case: ** USBHost
Root cause: ** The USBHost test script enumerated only the three USB root hubs (Bus 001–003, all 1d6b:xxxx Linux Foundation virtual devices) and found no external/peripheral USB device attached to the qcs9100-ride board's host port, causing the test to evaluate the result as FAIL with + true (no real device matched the expected condition).
Possible fix: Verify that a physical USB peripheral (e.g. USB storage or HID device) is connected to the qcs9100-ride board's USB host port in the LAVA lab; if the board has no USB device wired in the test fixture, this is a lab infrastructure gap — file a lab infra ticket to attach a USB device to the board, or mark USBHost as expected-skip for boards without a connected USB peripheral.
Detail analysis attachment: failed_case_job103205_7_detailed.md

Case 8: shmbridge
Failed case: shmbridge
Root cause: Could not be determined confidently from available logs.
Possible fix: No action required — this failure is suppressed as known CI noise; no kernel change or re-trigger is needed for this case.
Detail analysis attachment: failed_case_job103205_8_detailed.md

Case 9: ** 0_qcom-next-ci-premerge-tests
Failed case: ** 0_qcom-next-ci-premerge-tests
Root cause: ** All five sa8775p DSP remoteprocs (gpdsp0, gpdsp1, cdsp0, cdsp1, adsp) failed to boot at kernel init with error -22 initializing firmware qcom/sa8775p/*.mbn, leaving 0/5 subsystems running and causing cascading failures in remoteproc, smmu, shmbridge, and Probe_Failure_Check sub-tests; LAVA then marked the parent test definition as failed via "Marking unfinished test run as failed".
Possible fix: Re-trigger the CI job to confirm reproducibility; if the failure recurs, investigate the rootfs/firmware image deployed to the qcs9100-ride board — the qcom_q6v5_pas PIL driver is rejecting all DSP firmware blobs with -EINVAL, which indicates a firmware-image/kernel-version mismatch or a missing/corrupt .mbn file in the rootfs image (qcom-multimedia-image-qcs9100-ride-sx.rootfs.qcomflash.tar.gz). This failure is pre-existing and unrelated to PR Enable IPCB for Hamoa and Glymur #602.
Detail analysis attachment: failed_case_job103205_9_detailed.md

Job 103206 | SoC monaco-evk

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

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

Case 1: ** Probe_Failure_Check
Failed case: ** Probe_Failure_Check
Root cause: ** The Probe_Failure_Check test failed because its probe_failures.log scanner matched two early-boot Bluetooth firmware load errors (Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2 and qca/hpbtfw21.tlv failed with error -2) that are a known false positive on monaco-evk: the QCA WCN Bluetooth driver attempts to load a vendor-specific firmware file (wcnhpbtfw21.tlv) at early boot before the firmware partition is accessible, falls back gracefully, and Bluetooth operates correctly — confirmed by BT_ON_OFF RESULT=PASS and BT_FW_KMD_Service RESULT=PASS later in the same job.
Possible fix: Suppress these two BT firmware load error strings (qca/wcnhpbtfw21.tlv and qca/hpbtfw21.tlv with error -2) in the Probe_Failure_Check test's dmesg filter for monaco-evk, as they are pre-existing benign early-boot fallback messages that do not indicate a functional regression; no kernel or PR change is required.
Detail analysis attachment: failed_case_job103206_1_detailed.md

Case 2: ** WiFi_OnOff
Failed case: ** WiFi_OnOff
Root cause: ** On monaco-evk, both PCIe controllers (1c00000.pci and 1c10000.pci) report Phy link never came up at boot, preventing ath11k_pci from enumerating the WCN6855 WiFi device over PCIe; additionally, no ath11k WiFi firmware is present in the deployed firmware image (initramfs-firmware-qcs8300-ride-image-qcom-armv8a.cpio.gz is a QCS8300/RB3Gen2 image, not monaco-evk), so even if PCIe were functional the driver could not load firmware.
Possible fix: This is a pre-existing infrastructure/board configuration issue unrelated to the PR (which only adds Coresight/TGU DT overlays for glymur/hamoa/sm8750/kaanapali); verify the monaco-evk PCIe PHY bring-up (power/clock/reset sequencing in DT or board bring-up) and ensure the correct monaco-evk firmware image is deployed in the LAVA job definition.
Detail analysis attachment: failed_case_job103206_2_detailed.md

Case 3: ** `0_qcom-next-ci-premerge-tests`
Failed case: ** 0_qcom-next-ci-premerge-tests
Root cause: ** The LAVA test definition wrapper 0_qcom-next-ci-premerge-tests was marked failed by the LAVA dispatcher ("Marking unfinished test run as failed") because two genuine sub-tests failed: (1) WiFi_OnOff — the firmware ramdisk deployed is initramfs-firmware-qcs8300-ride-image (QCS8300/RB3Gen2 firmware) rather than a monaco-evk-specific firmware image, so no ath11k WiFi firmware blobs are present under /lib/firmware and no WiFi interface appears after retries (WiFi stack present, but no usable WiFi interface was found after retries); (2) Probe_Failure_Check — the test scans kernel logs for firmware-related errors and flags early-boot BT firmware load failures (bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2) that are benign because BT is functionally operational (BT_ON_OFF and BT_FW_KMD_Service both PASSED). Neither failure is introduced by PR Enable IPCB for Hamoa and Glymur #602, which only adds staging DT overlays for unrelated platforms (glymur, hamoa, sm8750, kaanapali).
Possible fix: Update the LAVA job definition for monaco-evk to use the correct monaco-specific firmware ramdisk image (not initramfs-firmware-qcs8300-ride-image) so that ath11k WiFi firmware blobs are present; additionally, add a suppression rule for Probe_Failure_Check failures caused solely by BT firmware load errors when BT_ON_OFF and BT_FW_KMD_Service pass.
Detail analysis attachment: failed_case_job103206_3_detailed.md

Job 103207 | SoC x1e80100

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

Failed test cases in LAVA job 103207 (SoC: x1e80100).

Case 1: ** Build Load Failure — Fastboot boot failure
Failed case: ** Build Load Failure — Fastboot boot failure
Root cause: ** Result: Build Load Failure. The fastboot boot command at stage 3.4 successfully transferred boot.img (234912 KB, OKAY in ~0.66s) to the x1e80100-CRD board but the device's UEFI/ABL firmware (BOOT.MXF.2.4-00541-HAMOA-1) rejected it at the boot-image load/authentication step with the error FAILED (remote: 'Failed to load/authenticate boot image: Load Error'), repeated identically across all 3 retry attempts — indicating the boot image format or header version is incompatible with what the x1e80100 ABL expects (the image was built with mkbootimg --header_version 2, while the x1e80100 UEFI-based boot flow may require a higher header version or a different image format).
Possible fix: Verify that the mkbootimg invocation in the LAVA job definition uses the correct --header_version for the x1e80100-CRD board (the x1e80100 platform typically requires header version 3 or higher); update the boot image build step accordingly and re-trigger the CI job.
Detail analysis attachment: failed_case_job103207_1_detailed.md

Case 2: ** Build Load Failure — Fastboot boot image authentication failure
Failed case: ** Build Load Failure — Fastboot boot image authentication failure
Root cause: ** Result: Build Load Failure; at stage 3.4 boot-fastboot, the x1e80100-crd ABL (BOOT.MXF.2.4-00541-HAMOA-1) rejected the boot image on all 3 attempts with the remote error "Failed to load/authenticate boot image: Load Error" — the image transfer succeeded (234912 KB OKAY) but the bootloader's image validation/authentication step failed, likely due to a boot image header version or format mismatch (mkbootimg --header_version 2) incompatible with this ABL version.
Possible fix: Re-trigger the CI job to rule out a transient ABL state; if the failure recurs, update the mkbootimg invocation in the LAVA postprocess script for x1e80100-crd to use the correct --header_version expected by ABL BOOT.MXF.2.4-00541-HAMOA-1 (check if v3/v4 is required), or update the ABL firmware on the board to a version compatible with header_version 2 images.
Detail analysis attachment: failed_case_job103207_2_detailed.md

Case 3: ** Build Load Failure — Fastboot boot failure
Failed case: ** Build Load Failure — Fastboot boot failure
Root cause: ** Result: Build Load Failure. The LAVA fastboot-boot action failed at the boot stage (not deploy/flash) on all 3 retry attempts because the x1e80100-crd board's ABL/secure-boot firmware rejected the boot.img with the remote error FAILED (remote: 'Failed to load/authenticate boot image: Load Error'), preventing the kernel from ever loading; the final job result carries error_type: Infrastructure.
Possible fix: Re-trigger the CI job; if the failure recurs, verify that the boot.img artifact built from this PR is correctly signed/packaged for the x1e80100-crd secure-boot policy — check whether the signing key or image format expected by the board's ABL has changed, and confirm the boot image passes fastboot boot on a known-good baseline build.
Detail analysis attachment: failed_case_job103207_3_detailed.md

Job 103208 | SoC qcs615-ride

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

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

Case 1: ** Probe_Failure_Check
Failed case: ** Probe_Failure_Check
Root cause: ** The cfg80211 wireless regulatory driver fails to load regulatory.db firmware at boot (faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2, ENOENT) because the file is absent from /lib/firmware/ in the qcs615-ride test rootfs; the Probe_Failure_Check test catches this dmesg line and reports FAIL.
Possible fix: Add regulatory.db to the test rootfs image used for qcs615-ride LAVA jobs (place it under /lib/firmware/regulatory.db), or suppress this known-benign firmware-absent message in the Probe_Failure_Check test script since cfg80211 gracefully falls back to compiled-in regulatory data and WiFi functionality is unaffected (WiFi_Firmware_Driver and WiFi_OnOff both PASS).
Detail analysis attachment: failed_case_job103208_1_detailed.md

Case 2: ** smmu
Failed case: ** smmu
Root cause: ** The SMMU test script on qcs615-ride asserts that video sub-devices aa00000.video-codec:video-decoder and aa00000.video-codec:video-encoder each appear as independently IOMMU-group-attached devices in sysfs, but on qcs615 the Venus video-codec driver registers these as virtual child devices that do not receive their own IOMMU group entries — only the parent aa00000.video-codec is attached to group 7 — causing two [FAIL] Critical master is missing iommu_group attachment assertions and a final WARN=0, FAIL=2 result.
Possible fix: Update the SMMU test script to recognize that aa00000.video-codec (parent) being attached to an IOMMU group is sufficient for qcs615-ride, and exempt the virtual child sub-device names (video-decoder, video-encoder) from the per-device IOMMU group attachment check on this platform; alternatively add a platform-specific allowlist entry for qcs615 video-codec child devices.
Detail analysis attachment: failed_case_job103208_2_detailed.md

Case 3: ** USBHost
Failed case: ** USBHost
Root cause: ** The USBHost test failed because lsusb enumerated only the xHCI root hub (Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub) with no functional USB peripheral attached; the xHCI controller at 0x0a800000 probed correctly with one USB 2.0 port but no external USB device was plugged into the qcs615-ride board's USB host port at test execution time.
Possible fix: Verify that a USB peripheral device (e.g. USB mass-storage stick or HID device) is physically connected to the qcs615-ride board's USB host port in the LAVA lab setup before re-triggering the job; if the board has no accessible USB host port in this lab configuration, mark USBHost as a known infrastructure skip for qcs615-ride.
Detail analysis attachment: failed_case_job103208_3_detailed.md

Case 4: ** shmbridge — Suppressed (Known Benign: shmbridge CI noise)
Failed case: ** shmbridge — Suppressed (Known Benign: shmbridge CI noise)
Root cause: ** The shmbridge test script incorrectly flags the benign kernel log message qcom_scm firmware:scm: qseecom: untested machine, skipping as a "qcom_scm-related error," triggering a false FAIL; this is a known CI infrastructure false positive on qcs615-ride and all other Qualcomm platforms, unconditionally suppressed per Rule 1 of the known-benign-failures policy.
Possible fix: No action required — suppress this result per Rule 1 (shmbridge always-suppress); the failure is not PR-introduced and does not indicate any kernel regression.
Detail analysis attachment: failed_case_job103208_4_detailed.md

Case 5: ** `0_qcom-next-ci-premerge-tests`
Failed case: ** 0_qcom-next-ci-premerge-tests
Root cause: ** The LAVA test shell marked the overall 0_qcom-next-ci-premerge-tests definition as failed because sub-tests within the suite reported FAIL: shmbridge (false positive — test script matched the benign kernel cmdline string qcom_scm.download_mode=1 as a qcom_scm error), USBHost (no USB device attached to the qcs615-ride board in this LAVA setup), and Probe_Failure_Check (regulatory.db firmware load failure, a known benign infra issue); none of these failures are caused by the PR's DTS-only changes targeting glymur/hamoa/sm8750/kaanapali platforms.
Possible fix: Suppress the known false-positive sub-test failures in the qcom-linux-testkit: fix the shmbridge test to exclude kernel cmdline matches from its qcom_scm error scan, mark USBHost as SKIP when no USB device is present on the board, and suppress the regulatory.db firmware load failure in Probe_Failure_Check; then re-trigger the CI job to confirm the PR is clean.
Detail analysis attachment: failed_case_job103208_5_detailed.md

Rahul Joshi (rahujosh) · 2026-05-20T11:57:41Z

PR #602 — validate-patch

PR:#602

Verdict	Issues	Detailed Report
⚠️ PARTIAL	1	Full report

Final Summary

Lore link present: No — all 5 commits use the PENDING: prefix; no lore.kernel.org link is expected or required for any of them.
Lore link matches PR commits: N/A — no lore link to compare against for any commit.
Upstream patch status: N/A — all commits are vendor-only staging DT overlays, not posted upstream.
PR present in qcom-next: Partially — Commit 1 (glymur: add TGU and ETR) is already present in qcom-next as ef11d92a47a0; Commits 2–5 are not yet in qcom-next.

Verdict: ⚠️ PARTIAL — click to expand
🔍 Patch Validation — PR #602
PR: qualcomm-linux/kernel #602 — "PENDING: arm64: dts: qcom: add TGU/ETR/Coresight staging overlays (glymur, hamoa, sm8750, kaanapali)"
Upstream commit: N/A — all 5 commits carry the PENDING: prefix; no lore.kernel.org links are present or expected.
Verdict:⚠️ PARTIAL (see per-commit notes; structurally sound but Commit 1 is a duplicate of an already-merged qcom-next entry)
Commit 1 of 5 — PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
Author: Jie Gan <jie.gan@oss.qualcomm.com>
Files changed:arch/arm64/boot/dts/qcom/Makefile, arch/arm64/boot/dts/qcom/glymur-staging.dtso (new file, 201 lines)
Commit Message
Check Status Note
Subject matches upstream N/A PENDING: — no upstream to compare
Body preserves rationale ✅ Brief but adequate: describes TGU (IPCB) and ETR (DDR trace) purpose
Fixes tag present/correct N/A Not a bug-fix commit
Authorship preserved ✅ Single author; From: matches Signed-off-by:
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds glymur-staging.dtbo entry cleanly
arch/arm64/boot/dts/qcom/glymur-staging.dtso ✅ New file; adds CTCU, replicators, ETR TMCs, and TGU nodes under &soc
Issues
⚠️Duplicate in qcom-next: This exact commit is already present in origin/qcom-next as ef11d92a47a0. Merging it again will create a duplicate commit. The PR should either drop this commit or rebase on top of qcom-next so it is a no-op.
Per-Commit Verdict
PENDING: vendor-only commit — lore validation not applicable. Content is correct, but the commit already landed in qcom-next (ef11d92a47a0); it must be dropped or the branch rebased before merging.
Commit 2 of 5 — PENDING: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block
Author: Jie Gan <jie.gan@oss.qualcomm.com>
Files changed:arch/arm64/boot/dts/qcom/glymur-staging.dtso (+1248 lines)
Commit Message
Check Status Note
Subject matches upstream N/A PENDING: — no upstream
Body preserves rationale ✅ Lists device types added (ETM, replicator, funnel, TMC ETF)
Fixes tag present/correct N/A Not a bug-fix commit
Authorship preserved ✅ From: matches Signed-off-by:
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/glymur-staging.dtso ✅ Adds 18 ETE nodes under &{/}, APSS funnel, NCC cluster funnels/ETFs/replicators for 3 clusters (cpu0–17), and tn@11200000 port extension
Issues
None identified for this commit.
Per-Commit Verdict
PENDING: vendor-only commit — lore validation not applicable. Content is self-consistent and well-structured. Not yet in qcom-next.
Commit 3 of 5 — PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso
Author: Jie Gan <jie.gan@oss.qualcomm.com>
Files changed:arch/arm64/boot/dts/qcom/Makefile, arch/arm64/boot/dts/qcom/hamoa-staging.dtso (new file, 35 lines)
Commit Message
Check Status Note
Subject matches upstream N/A PENDING: — no upstream
Body preserves rationale ✅ Describes TGU addition for IPCB feature
Fixes tag present/correct N/A Not a bug-fix commit
Authorship preserved ✅ From: matches Signed-off-by:
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds hamoa-staging.dtbo entry cleanly
arch/arm64/boot/dts/qcom/hamoa-staging.dtso ✅ New file; 3 TGU nodes at 0x10b0e000, 0x10b0f000, 0x10b10000
Issues
None identified.
Per-Commit Verdict
PENDING: vendor-only commit — lore validation not applicable. Content is correct. Not yet in qcom-next.
Commit 4 of 5 — PENDING: arm64: dts: qcom: sm8750: add TGU in staging dtso
Author: Jie Gan <jie.gan@oss.qualcomm.com>
Files changed:arch/arm64/boot/dts/qcom/Makefile, arch/arm64/boot/dts/qcom/sm8750-staging.dtso (new file, 35 lines)
Commit Message
Check Status Note
Subject matches upstream N/A PENDING: — no upstream
Body preserves rationale ✅ Describes TGU addition for IPCB feature
Fixes tag present/correct N/A Not a bug-fix commit
Authorship preserved ✅ From: matches Signed-off-by:
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds sm8750-staging.dtbo entry cleanly
arch/arm64/boot/dts/qcom/sm8750-staging.dtso ✅ New file; 3 TGU nodes at 0x10b0e000, 0x10b0f000, 0x10b10000 — same addresses as hamoa; intentional if both boards share the same SoC TGU layout
Issues
⚠️Address overlap with hamoa:sm8750-staging.dtso and hamoa-staging.dtso define TGU nodes at identical addresses (0x10b0e000, 0x10b0f000, 0x10b10000). This is only correct if both boards are based on the same SoC with the same TGU register map. Worth a reviewer double-check to confirm this is intentional and not a copy-paste error.
Per-Commit Verdict
PENDING: vendor-only commit — lore validation not applicable. Content is structurally correct. Address overlap with hamoa warrants a reviewer sanity-check. Not yet in qcom-next.
Commit 5 of 5 — PENDING: arm64: dts: qcom: kaanapali: add TGU in staging dtso
Author: Jie Gan <jie.gan@oss.qualcomm.com>
Files changed:arch/arm64/boot/dts/qcom/Makefile, arch/arm64/boot/dts/qcom/kaanapali-staging.dtso (new file, 43 lines)
Commit Message
Check Status Note
Subject matches upstream N/A PENDING: — no upstream
Body preserves rationale ✅ Describes TGU addition for IPCB feature
Fixes tag present/correct N/A Not a bug-fix commit
Authorship preserved ✅ From: matches Signed-off-by:
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds kaanapali-staging.dtbo entry cleanly
arch/arm64/boot/dts/qcom/kaanapali-staging.dtso ✅ New file; 4 TGU nodes at 0x11301000, 0x1130e000, 0x1130f000, 0x11310000 — distinct addresses from hamoa/sm8750, consistent with a different SoC
Issues
None identified.
Per-Commit Verdict
PENDING: vendor-only commit — lore validation not applicable. Content is correct. Not yet in qcom-next.
Final Summary
Lore link present: No — all 5 commits use the PENDING: prefix; no lore.kernel.org link is expected or required for any of them.
Lore link matches PR commits: N/A — no lore link to compare against for any commit.
Upstream patch status: N/A — all commits are vendor-only staging DT overlays, not posted upstream.
PR present in qcom-next: Partially — Commit 1 (glymur: add TGU and ETR) is already present in qcom-next as ef11d92a47a0; Commits 2–5 are not yet in qcom-next.

Rahul Joshi (rahujosh) · 2026-05-20T11:57:43Z

PR #602 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	All 5 commits clean — 0 errors, 0 warnings
dt-binding-check	⏭️	Skipped — no changes in `Documentation/devicetree/bindings`
dtb-check	✅	Test passed — pre-existing tree warnings filtered; no new errors introduced
sparse-check	⏭️	Skipped — no C/H file changes
check-uapi-headers	⏭️	Skipped — no C/H file changes
check-patch-compliance	❌	All 5 commits fail — `PENDING:` is not an accepted prefix
tag-check	✅	All 5 commits carry `PENDING:` — valid tag for `qcom-6.18.y` branch
qcom-next-check	N/A	`PENDING:` commits are not expected in qcom-next

Detailed report: Full report

Checker analysis — click to expand
🤖 CI Checker Analysis (checker-log-analyzer)
PR:#602 — PENDING: arm64: dts: qcom: add TGU/ETR/Coresight staging DTS nodes (5 commits)
Source:https://github.com/qualcomm-linux/kernel-config/actions/runs/26135626742
Target branch:qcom-6.18.y (tag-check is mandatory — not qcom-next / qcom-next-staging)
Checker Result Summary
checkpatch ✅ All 5 commits clean — 0 errors, 0 warnings
dt-binding-check ⏭️ Skipped — no changes in Documentation/devicetree/bindings
dtb-check ✅ Test passed — pre-existing tree warnings filtered; no new errors introduced
sparse-check ⏭️ Skipped — no C/H file changes
check-uapi-headers ⏭️ Skipped — no C/H file changes
check-patch-compliance ❌ All 5 commits fail — PENDING: is not an accepted prefix
tag-check ✅ All 5 commits carry PENDING: — valid tag for qcom-6.18.y branch
qcom-next-check N/A PENDING: commits are not expected in qcom-next
❌ check-patch-compliance
Root cause: All 5 commits use the PENDING: prefix, which is not in the allowed set (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:) that check-patch-compliance enforces.
Failure details:
Checking commit: PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
Commit summary does not start with a required prefix
Checking commit: PENDING: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block
Commit summary does not start with a required prefix
Checking commit: PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso
Commit summary does not start with a required prefix
Checking commit: PENDING: arm64: dts: qcom: sm8750: add TGU in staging dtso
Commit summary does not start with a required prefix
Checking commit: PENDING: arm64: dts: qcom: kaanapali: add TGU in staging dtso
Commit summary does not start with a required prefix
##[error]Process completed with exit code 1.
Assessment: This is a known checker limitation — PENDING: is a valid vendor-internal prefix used in the tree for work-in-progress patches not yet posted upstream, but check-patch-compliance only accepts upstream-linkable prefixes. Since these are staging DTS overlays (.dtso) that are genuinely not yet posted to the mailing list, PENDING: is the correct prefix. No patch change is needed unless the patches have since been posted upstream.
Fix (if patches have been posted to lore):
# For each commit, if the patch is now on lore.kernel.org:
git rebase -i <base_sha># mark each commit as 'edit'
git commit --amend -m "FROMLIST: arm64: dts: qcom: <original subject>"# Add: Link: https://lore.kernel.org/r/<message-id>
git rebase --continue
Fix (if patches remain vendor-only / not posted):
No action required — PENDING: is the correct prefix for unposted work-in-progress. The check-patch-compliance failure is a known false positive for PENDING: commits.
Reproduce locally:
./scripts/check-patch-compliance.sh --git <base_sha>..<head_sha>
Verdict
1 checker failure, 0 patch defects. The sole failure (check-patch-compliance) is a known checker limitation — PENDING: is a legitimate vendor-internal prefix that the compliance checker does not accept. All other checkers pass or are correctly skipped (DTS-only PR). The PR is ready to merge from a code-quality standpoint; the check-patch-compliance failure requires no patch change unless these patches have been posted upstream (in which case switch to FROMLIST: + add Link: trailers).

Rahul Joshi (rahujosh) · 2026-05-22T05:23:33Z

PR #602 — validate-patch

PR:#602

Verdict	Issues	Detailed Report
❌ FAIL	1	Full report

Final Summary

Lore link present: No — all commits use PENDING: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only change, not posted upstream
PR present in qcom-next: Not checked — PENDING: vendor-only commits and kernel-tree lookup was out of allowed scope

Verdict: ❌ FAIL — click to expand
🔍 Patch Validation
PR:#602 (title unavailable from local artifact; network fetch blocked)
Upstream commit: N/A (no lore.kernel.org link found in pr.patch)
Verdict: ❌ FAIL
Commit 1/5 — PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
Commit Message
Check Status Note
Subject matches upstream ❌ No lore/upstream link, so upstream subject match cannot be validated.
Body preserves rationale ⚠️ Message is internally coherent, but no upstream baseline exists.
Fixes tag present/correct ⚠️ No Fixes: tag present; correctness vs upstream cannot be checked.
Authorship preserved ⚠️ From: and Signed-off-by: are present, but no lore author to compare against.
Backport note (if applicable) N/A Not marked as backport.
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ⚠️ Cannot validate faithfulness without lore source patch.
arch/arm64/boot/dts/qcom/glymur-staging.dtso ⚠️ Cannot validate faithfulness without lore source patch.
Upstream Patch Status
Commit Community Verdict
PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso N/A — vendor-only PENDING: commit; no lore thread provided.
qcom-next Presence
Commit Status
PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso Not checked — blocked by scope constraint (no kernel tree lookup/checkout).
Issues
No lore link (Link: / Patch-mainline: / lore URL) present for this commit, so validate-patch comparison cannot be performed.
Per-Commit Verdict
Cannot be upstream-validated in current form; treat as vendor-only PENDING:.
Commit 2/5 — PENDING: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block
Commit Message
Check Status Note
Subject matches upstream ❌ No lore/upstream link, so upstream subject match cannot be validated.
Body preserves rationale ⚠️ Message is internally coherent, but no upstream baseline exists.
Fixes tag present/correct ⚠️ No Fixes: tag present; correctness vs upstream cannot be checked.
Authorship preserved ⚠️ From: and Signed-off-by: are present, but no lore author to compare against.
Backport note (if applicable) N/A Not marked as backport.
Diff
File Status Notes
arch/arm64/boot/dts/qcom/glymur-staging.dtso ⚠️ Cannot validate faithfulness without lore source patch.
Upstream Patch Status
Commit Community Verdict
PENDING: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block N/A — vendor-only PENDING: commit; no lore thread provided.
qcom-next Presence
Commit Status
PENDING: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block Not checked — blocked by scope constraint (no kernel tree lookup/checkout).
Issues
No lore link (Link: / Patch-mainline: / lore URL) present for this commit, so validate-patch comparison cannot be performed.
Per-Commit Verdict
Cannot be upstream-validated in current form; treat as vendor-only PENDING:.
Commit 3/5 — PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso
Commit Message
Check Status Note
Subject matches upstream ❌ No lore/upstream link, so upstream subject match cannot be validated.
Body preserves rationale ⚠️ Message is internally coherent, but no upstream baseline exists.
Fixes tag present/correct ⚠️ No Fixes: tag present; correctness vs upstream cannot be checked.
Authorship preserved ⚠️ From: and Signed-off-by: are present, but no lore author to compare against.
Backport note (if applicable) N/A Not marked as backport.
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ⚠️ Cannot validate faithfulness without lore source patch.
arch/arm64/boot/dts/qcom/hamoa-staging.dtso ⚠️ Cannot validate faithfulness without lore source patch.
Upstream Patch Status
Commit Community Verdict
PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso N/A — vendor-only PENDING: commit; no lore thread provided.
qcom-next Presence
Commit Status
PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso Not checked — blocked by scope constraint (no kernel tree lookup/checkout).
Issues
No lore link (Link: / Patch-mainline: / lore URL) present for this commit, so validate-patch comparison cannot be performed.
Per-Commit Verdict
Cannot be upstream-validated in current form; treat as vendor-only PENDING:.
Commit 4/5 — PENDING: arm64: dts: qcom: sm8750: add TGU in staging dtso
Commit Message
Check Status Note
Subject matches upstream ❌ No lore/upstream link, so upstream subject match cannot be validated.
Body preserves rationale ⚠️ Message is internally coherent, but no upstream baseline exists.
Fixes tag present/correct ⚠️ No Fixes: tag present; correctness vs upstream cannot be checked.
Authorship preserved ⚠️ From: and Signed-off-by: are present, but no lore author to compare against.
Backport note (if applicable) N/A Not marked as backport.
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ⚠️ Cannot validate faithfulness without lore source patch.
arch/arm64/boot/dts/qcom/sm8750-staging.dtso ⚠️ Cannot validate faithfulness without lore source patch.
Upstream Patch Status
Commit Community Verdict
PENDING: arm64: dts: qcom: sm8750: add TGU in staging dtso N/A — vendor-only PENDING: commit; no lore thread provided.
qcom-next Presence
Commit Status
PENDING: arm64: dts: qcom: sm8750: add TGU in staging dtso Not checked — blocked by scope constraint (no kernel tree lookup/checkout).
Issues
No lore link (Link: / Patch-mainline: / lore URL) present for this commit, so validate-patch comparison cannot be performed.
Per-Commit Verdict
Cannot be upstream-validated in current form; treat as vendor-only PENDING:.
Commit 5/5 — PENDING: arm64: dts: qcom: kaanapali: add TGU in staging dtso
Commit Message
Check Status Note
Subject matches upstream ❌ No lore/upstream link, so upstream subject match cannot be validated.
Body preserves rationale ⚠️ Message is internally coherent, but no upstream baseline exists.
Fixes tag present/correct ⚠️ No Fixes: tag present; correctness vs upstream cannot be checked.
Authorship preserved ⚠️ From: and Signed-off-by: are present, but no lore author to compare against.
Backport note (if applicable) N/A Not marked as backport.
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ⚠️ Cannot validate faithfulness without lore source patch.
arch/arm64/boot/dts/qcom/kaanapali-staging.dtso ⚠️ Cannot validate faithfulness without lore source patch.
Upstream Patch Status
Commit Community Verdict
PENDING: arm64: dts: qcom: kaanapali: add TGU in staging dtso N/A — vendor-only PENDING: commit; no lore thread provided.
qcom-next Presence
Commit Status
PENDING: arm64: dts: qcom: kaanapali: add TGU in staging dtso Not checked — blocked by scope constraint (no kernel tree lookup/checkout).
Issues
No lore link (Link: / Patch-mainline: / lore URL) present for this commit, so validate-patch comparison cannot be performed.
Per-Commit Verdict
Cannot be upstream-validated in current form; treat as vendor-only PENDING:.
Verdict
Do not merge as upstream-aligned commits in current form; either keep as explicit vendor-only PENDING: work or add lore links and upstream provenance so diff/author validation can be performed.
Final Summary
Lore link present: No — all commits use PENDING: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only change, not posted upstream
PR present in qcom-next: Not checked — PENDING: vendor-only commits and kernel-tree lookup was out of allowed scope

Rahul Joshi (rahujosh) · 2026-05-22T05:23:35Z

PR #602 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	All 5 commits: `0 errors, 0 warnings, 0 checks`; checker passed.
dt-binding-check	⏭️	Skipped: `No changes in Documentation/devicetree/bindings`.
dtb-check	✅	`Log Summary: Test passed` for changed staging DTBs.
sparse-check	⏭️	Skipped: `Skipping sparse check as nothing changed...`.
check-uapi-headers	⏭️	Skipped: `Skipping uapi check as nothing changed...`.
check-patch-compliance	❌	All 5 commits failed prefix policy (`PENDING:` rejected by this checker).
tag-check	✅	Target branch is `qcom-6.18.y` (not `qcom-next*`); all commit subjects have valid tag-check prefix (`PENDING:`).
qcom-next-check	⏭️	Not applicable for this run/target (`base_branch: qcom-6.18.y`).

Detailed report: Full report

Checker analysis — click to expand
🤖 CI Checker Analysis (checker-log-analyzer)
PR:#602 (5-commit PENDING DTS staging series)
Source:https://github.com/qualcomm-linux/kernel-config/actions/runs/26135626742
Checker Result Summary
checkpatch ✅ All 5 commits: 0 errors, 0 warnings, 0 checks; checker passed.
dt-binding-check ⏭️ Skipped: No changes in Documentation/devicetree/bindings.
dtb-check ✅ Log Summary: Test passed for changed staging DTBs.
sparse-check ⏭️ Skipped: Skipping sparse check as nothing changed....
check-uapi-headers ⏭️ Skipped: Skipping uapi check as nothing changed....
check-patch-compliance ❌ All 5 commits failed prefix policy (PENDING: rejected by this checker).
tag-check ✅ Target branch is qcom-6.18.y (not qcom-next*); all commit subjects have valid tag-check prefix (PENDING:).
qcom-next-check ⏭️ Not applicable for this run/target (base_branch: qcom-6.18.y).
❌ check-patch-compliance
Root cause:check-patch-compliance accepts only upstream-linkable prefixes, and every commit uses PENDING:.
Failure details:
Checking commit: PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
Commit summary does not start with a required prefix
...
Checking commit: PENDING: arm64: dts: qcom: kaanapali: add TGU in staging dtso
Commit summary does not start with a required prefix
##[error]Process completed with exit code 1.
Fix:
For each commit, change subject to an allowed compliance prefix: FROMLIST:, FROMGIT:, UPSTREAM:, or BACKPORT:.
If using FROMLIST:, add valid Link: <lore URL> in the commit message.
If these commits are intentionally vendor-only and must stay PENDING:, this checker will continue failing (known limitation); you need policy/checker exception rather than code changes.
Reproduce locally:
bash ../kernel-checkers/check-patch-compliance.sh --kernel-src <kernel-tree> --base 0136c1ed9c23851783df4ad39ad3556497cc3c2a --head 02eeba05fc7c3ced8283ae82c9beed288d1a8c84
Verdict
1 blocker to fix before merge: check-patch-compliance prefix policy failure on all 5 commits.

qlijarvis · 2026-05-25T10:46:39Z

PR #602 — validate-patch

PR:#602

Verdict	Issues	Detailed Report
N/A	0	Full report

Final Summary

Lore link present: No — QCLINUX: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only changes, not posted upstream
PR present in qcom-next: Not checked — QCLINUX: vendor-only commits

Verdict: N/A — click to expand
🔍 Patch Validation
PR:#602
Upstream commit: N/A (vendor-only commits)
Verdict: ⏭️ SKIP — Validation not applicable
Summary
This PR contains 3 commits, all with the QCLINUX: prefix:
QCLINUX: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
QCLINUX: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block
QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso
Commit Message
Check Status Note
Subject matches upstream N/A Vendor-only commits
Body preserves rationale N/A Vendor-only commits
Fixes tag present/correct N/A Vendor-only commits
Authorship preserved N/A Vendor-only commits
Backport note (if applicable) N/A Vendor-only commits
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ⏭️ Vendor-only: adds glymur-staging.dtbo and hamoa-staging.dtbo
arch/arm64/boot/dts/qcom/glymur-staging.dtso ⏭️ Vendor-only: new staging overlay with TGU, ETR, and Coresight devices
arch/arm64/boot/dts/qcom/hamoa-staging.dtso ⏭️ Vendor-only: new staging overlay with TGU devices
Verdict
Validation skipped — All commits use the QCLINUX: prefix, indicating vendor-specific changes not intended for upstream submission. No lore.kernel.org link is expected or required for these commits. The changes add staging device tree overlays for Glymur and Hamoa platforms with debug/trace infrastructure (TGU, ETR, Coresight ETM/funnel/replicator devices).
Final Summary
Lore link present: No — QCLINUX: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only changes, not posted upstream
PR present in qcom-next: Not checked — QCLINUX: vendor-only commits
Notes
Commit 1/3: Adds TGU (Trace Generation Unit) and ETR (Embedded Trace Router) devices to glymur-staging.dtso for IPCB feature and DDR memory trace support
Commit 2/3: Adds extensive Coresight debug infrastructure (18 ETE devices, replicators, funnels, TMC ETF) for APSS debug block
Commit 3/3: Adds TGU devices to hamoa-staging.dtso for IPCB feature support
All commits are properly signed off by Jie Gan jie.gan@oss.qualcomm.com and follow the vendor-only commit pattern for staging device tree overlays.

qlijarvis · 2026-05-25T10:46:40Z

PR #602 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	All 3 commits passed
dt-binding-check	⏭️	No binding changes
dtb-check	✅	Test passed (pre-existing warnings filtered)
sparse-check	⏭️	No C/H file changes
check-uapi-headers	⏭️	No UAPI changes
check-patch-compliance	❌	`QCLINUX:` prefix not accepted (known limitation)
tag-check	❌	`QCLINUX:` is valid but fails compliance checker

Detailed report: Full report

Checker analysis — click to expand
🤖 CI Checker Analysis (checker-log-analyzer)
PR:#602 - QCLINUX: arm64: dts: qcom: glymur/hamoa: add TGU and Coresight devices
Source:https://github.com/qualcomm-linux/kernel-config/actions/runs/26388800084
Target branch:qcom-6.18.y
Checker Result Summary
checkpatch ✅ All 3 commits passed
dt-binding-check ⏭️ No binding changes
dtb-check ✅ Test passed (pre-existing warnings filtered)
sparse-check ⏭️ No C/H file changes
check-uapi-headers ⏭️ No UAPI changes
check-patch-compliance ❌ QCLINUX: prefix not accepted (known limitation)
tag-check ❌ QCLINUX: is valid but fails compliance checker
❌ check-patch-compliance
Root cause: All three commits use the QCLINUX: prefix, which is not in the checker's allowed list (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:).
Failure details:
Checking commit: QCLINUX: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
Commit summary does not start with a required prefix
Checking commit: QCLINUX: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block
Commit summary does not start with a required prefix
Checking commit: QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso
Commit summary does not start with a required prefix
Analysis:
This is a known checker limitation. The check-patch-compliance script only accepts upstream-linkable prefixes (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:). Vendor-only prefixes like QCLINUX: and PENDING: always fail this check, even though they are valid and widely used in the tree for vendor-specific changes.
Context:
All three commits add vendor-specific staging device tree overlays (glymur-staging.dtso, hamoa-staging.dtso)
These are TGU (Trace Generation Unit) and Coresight debug devices for internal development
No upstream equivalent exists for staging overlays
The QCLINUX: prefix is the correct choice for vendor-only changes
Fix options:
Option 1 (Recommended): Accept the checker failure as a known limitation
The QCLINUX: prefix is correct for vendor-only staging changes
No patch modification needed
Document in PR that this is expected for vendor-only commits
Option 2: Change prefix to FROMLIST: and add fake Link: tags
Not recommended — misrepresents the patch origin
Would require posting these staging overlays upstream (not appropriate)
Option 3: Remove the prefix entirely
Violates the tag-check requirement for qcom-6.18.y branch
Would fail both checkers
❌ tag-check (manual check)
Root cause: The target branch is qcom-6.18.y, which requires all commits to have a subject-line prefix. While QCLINUX: is a valid prefix, it triggers the check-patch-compliance failure above.
Analysis:
The skill's tag-check (Step 2.7) verifies that every commit targeting a branch other than qcom-next or qcom-next-staging starts with a valid prefix. All three commits do have the QCLINUX: prefix, so they satisfy the tag-check requirement.
However, the check-patch-compliance checker does not accept QCLINUX: as a valid prefix, creating a conflict:
tag-check requirement: ✅ PASS — QCLINUX: is a valid prefix
check-patch-compliance: ❌ FAIL — QCLINUX: not in allowed list
Verdict:
From a policy perspective, the commits are correctly tagged with QCLINUX: for vendor-only changes. The checker failure is a tool limitation, not a patch defect.
Verdict
Recommendation: Merge as-is with documented checker limitation.
Rationale:
All code quality checks passed (checkpatch, dtb-check)
The check-patch-compliance failure is a known limitation for vendor-only commits
The QCLINUX: prefix is the correct choice for staging device tree overlays
No upstream equivalent exists or is planned for these changes
The commits are properly signed off and follow kernel coding style
Alternative: If the CI gate is blocking merge, consider:
Documenting this as a known exception in the PR description
Requesting a CI policy update to allow QCLINUX: prefix for staging files
Adding a checker bypass for *-staging.dtso files

qlijarvis · 2026-05-25T13:40:45Z

PR #602 — validate-patch

PR:#602

Verdict	Issues	Detailed Report
✅	0	Full report

Final Summary

Lore link present: No — QCLINUX: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only change, not posted upstream
PR present in qcom-next: Not checked — QCLINUX: vendor-only commit

Verdict: ✅ — click to expand
🔍 Patch Validation
PR:#602 - QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso
Upstream commit: N/A (vendor-only commit)
Verdict: ✅ PASS (vendor-only; validation not applicable)
Commit Message
Check Status Note
Subject matches upstream N/A QCLINUX: vendor-only commit
Body preserves rationale ✅ Clear description of TGU/IPCB feature addition
Fixes tag present/correct N/A Not a fix; new feature addition
Authorship preserved ✅ Jie Gan authored and signed off
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds hamoa-staging.dtbo build target; also fixes whitespace on kodiak line (space→tab)
Issues
None. The commit is well-formed for a vendor-only change.
Verdict
Merge as-is. This is a vendor-only commit adding a new staging dtbo for hamoa TGU/IPCB support. The QCLINUX: prefix correctly indicates no upstream equivalent exists. Commit message is clear, authorship is correct, and the diff adds the expected Makefile entry.
Final Summary
Lore link present: No — QCLINUX: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only change, not posted upstream
PR present in qcom-next: Not checked — QCLINUX: vendor-only commit

qlijarvis · 2026-05-25T13:40:46Z

PR #602 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	No binding changes
dtb-check	❌	Build failure: missing source file
sparse-check	⏭️	No C/H changes
check-uapi-headers	⏭️	No UAPI changes
check-patch-compliance	❌	`QCLINUX:` prefix not accepted
tag-check	✅	Valid prefix present

Detailed report: Full report

Checker analysis — click to expand
🤖 CI Checker Analysis (checker-log-analyzer)
PR:#602 - QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso
Source:https://github.com/qualcomm-linux/kernel-config/actions/runs/26400023421
Target branch:qcom-6.18.y
Checker Result Summary
checkpatch ✅ No style issues
dt-binding-check ⏭️ No binding changes
dtb-check ❌ Build failure: missing source file
sparse-check ⏭️ No C/H changes
check-uapi-headers ⏭️ No UAPI changes
check-patch-compliance ❌ QCLINUX: prefix not accepted
tag-check ✅ Valid prefix present
❌ dtb-check
Root cause: The Makefile references hamoa-staging.dtbo but the corresponding source file hamoa-staging.dtso does not exist in the tree.
Failure details:
make[4]: *** No rule to make target 'arch/arm64/boot/dts/qcom/hamoa-staging.dtbo', needed by 'arch/arm64/boot/dts/qcom/dtbs-list'. Stop.
The patch adds hamoa-staging.dtbo to the Makefile but does not include the actual hamoa-staging.dtso source file that would be compiled into the .dtbo overlay.
Fix:
Create the missing arch/arm64/boot/dts/qcom/hamoa-staging.dtso file with the TGU device nodes
Ensure the file is added to the commit:
git add arch/arm64/boot/dts/qcom/hamoa-staging.dtso
git commit --amend --no-edit
Reproduce locally:
make -j$(nproc) O=out defconfig
make -j$(nproc) O=out arch/arm64/boot/dts/qcom/hamoa-staging.dtbo
❌ check-patch-compliance
Root cause: The commit uses the QCLINUX: prefix, which is not in the checker's allowed list of upstream-linkable prefixes.
Failure details:
Checking commit: QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso
Commit summary does not start with a required prefix
Known limitation: The check-patch-compliance checker only accepts upstream-linkable prefixes (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:). Vendor-only commits with QCLINUX: will always fail this check, even though QCLINUX: is a valid prefix for vendor-specific changes.
Fix: This is a known checker limitation for vendor-only commits. No patch change is needed — the QCLINUX: prefix is correct for vendor-specific work. The failure can be acknowledged and ignored.
Alternative (if upstream posting is planned): If this change will be posted upstream, change the prefix to FROMLIST: and add a Link: tag pointing to the lore.kernel.org URL once posted.
Verdict
2 blockers must be fixed before merge:
Critical: Add the missing hamoa-staging.dtso source file — the Makefile references a file that doesn't exist, causing the build to fail.
Acknowledged:check-patch-compliance failure is a known limitation for QCLINUX: prefixed commits and can be ignored if this is vendor-only work.
The primary issue is the missing .dtso file. Once that is added, the PR should be ready to merge (with the understanding that check-patch-compliance will continue to fail for vendor-only QCLINUX: commits).

Jie Gan (jiegan0107) · 2026-05-26T00:51:12Z

failed checker:
Checking commit: QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso
Commit summary does not start with a required prefix

This is an intended overlay dtso file with QCLINUX prefix.

qlijarvis · 2026-05-26T01:44:40Z

🔨 Build Failure Analysis — PR #602

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

#	Error	File:Line	PR-introduced?	Root Cause
1	No rule to make target 'arch/arm64/boot/dts/qcom/hamoa-staging.dtbo'	arch/arm64/boot/dts/qcom/Makefile:527	Yes	PR adds Makefile entry for `hamoa-staging.dtbo` but the source file `hamoa-staging.dtso` does not exist in the kernel tree

Verdict

The single build error is directly introduced by this PR. The PR adds a Makefile entry for a non-existent device tree overlay source file.

📎 Detailed analysis:Full report

qlijarvis · 2026-05-26T01:49:50Z

🔨 Build Failure Analysis — PR #602

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

#	Error	File:Line	PR-introduced?	Root Cause
1	No rule to make target 'hamoa-staging.dtbo'	arch/arm64/boot/dts/qcom/Makefile:527	✅ Yes	Makefile references non-existent source file hamoa-staging.dtso

Verdict

1 of 1 errors is introduced by this PR. The build failure is entirely caused by the PR changes.

📎 Detailed analysis:Full report

Jie Gan (jiegan0107) · 2026-05-26T22:40:15Z

Fix compilation issue

fixed

qlijarvis · 2026-05-26T23:10:00Z

PR #602 — validate-patch

PR:#602

Verdict	Issues	Detailed Report
✅	0	Full report

Final Summary

Lore link present: No — QCLINUX: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only change, not posted upstream
PR present in qcom-next: Not checked — QCLINUX: vendor-only commit; qcom-next check not applicable for staging-only device tree overlays

Verdict: ✅ — click to expand
🔍 Patch Validation
PR:#602 - QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso
Upstream commit: N/A (vendor-only commit)
Verdict: ✅ PASS (vendor-only)
Step 1 — Parse PR and Check for Lore Link
Analysis:
PR number: 602
Commit subject:QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso
Prefix:QCLINUX:
Files changed:
arch/arm64/boot/dts/qcom/Makefile (adds hamoa-staging.dtbo build target)
arch/arm64/boot/dts/qcom/hamoa-staging.dtso (new file with 3 TGU device nodes)
Lore link search:
Scanned commit message for lore.kernel.org URLs — none found.
Verdict for Step 1:
According to the skill's known prefix patterns table, QCLINUX: means "Vendor-only, no upstream equivalent" with "No link expected — skip validation".
This is a vendor-specific staging overlay adding TGU (Trace Generation Unit) devices for IPCB (Inter-Processor Communication Bridge) feature support. The commit is correctly prefixed as QCLINUX: and does not require a lore.kernel.org link.
Commit Message
Check Status Note
Subject matches upstream N/A Vendor-only commit; no upstream to compare
Body preserves rationale ✅ Clear description: "Add TGU devices for supporting IPCB feature in staging dtso file"
Fixes tag present/correct N/A Not a fix; new feature addition
Authorship preserved ✅ Author: Jie Gan jie.gan@oss.qualcomm.com; Signed-off-by present
Backport note (if applicable) N/A Not a backport
Co-developed-by used correctly ✅ Not used (single author)
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds hamoa-staging.dtbo build target; consistent with existing pattern
arch/arm64/boot/dts/qcom/hamoa-staging.dtso ✅ New staging overlay with 3 TGU device nodes at 0x10b0e000, 0x10b0f000, 0x10b10000; proper SPDX header, valid DTS syntax
Diff content review:
SPDX license:BSD-3-Clause — appropriate for Qualcomm DTS contributions
Copyright: Qualcomm Technologies, Inc. — correct
DTS structure: Valid overlay syntax (/dts-v1/; /plugin/;)
Device nodes: Three TGU instances with:
Compatible strings: "qcom,tgu", "arm,primecell" — follows ARM CoreSight conventions
Register addresses: Non-overlapping, 4KB regions each
Clock references: <&aoss_qmp> with apb_pclk name — standard for AMBA devices
Makefile change: Adds build target after kodiak-staging.dtbo — follows existing pattern
Issues
None. This is a well-formed vendor-specific staging overlay for internal feature enablement.
Verdict
✅ PASS (vendor-only) — This commit is correctly marked as QCLINUX: vendor-only and does not require upstream validation. The patch is well-formed, follows DTS conventions, and clearly documents its purpose (TGU device support for IPCB feature). Safe to merge.
Final Summary
Lore link present: No — QCLINUX: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only change, not posted upstream
PR present in qcom-next: Not checked — QCLINUX: vendor-only commit; qcom-next check not applicable for staging-only device tree overlays
Additional Context
What is this patch doing?
Adds three Trace Generation Unit (TGU) hardware blocks to the Hamoa SoC staging device tree overlay. TGUs are part of ARM CoreSight debug/trace infrastructure and are being enabled here to support the IPCB (Inter-Processor Communication Bridge) feature.
Why is it vendor-only?
Staging overlays (*-staging.dtso) are Qualcomm's mechanism for enabling hardware features that are:
Under active development
Not yet ready for upstream submission
Specific to internal/vendor builds
May have dependencies on out-of-tree drivers
These overlays are intentionally kept separate from mainline device trees and are not intended for upstream submission.

qlijarvis · 2026-05-26T23:10:02Z

PR #602 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	0 errors, 0 warnings, 0 checks
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	❌	`QCLINUX:` prefix not accepted
tag-check	✅	`QCLINUX:` is valid for qcom-6.18.y

Detailed report: Full report

Checker analysis — click to expand
🤖 CI Checker Analysis (checker-log-analyzer)
PR:#602 - QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso
Source:https://github.com/qualcomm-linux/kernel-config/actions/runs/26479314306
Target branch:qcom-6.18.y
Checker Result Summary
checkpatch ✅ 0 errors, 0 warnings, 0 checks
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 ❌ QCLINUX: prefix not accepted
tag-check ✅ QCLINUX: is valid for qcom-6.18.y
❌ check-patch-compliance
Root cause: The commit uses QCLINUX: prefix, which is not in the allowed list for check-patch-compliance.
Failure details:
Checking commit: QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso
Commit summary does not start with a required prefix
Analysis:
This is a known limitation of the check-patch-compliance checker. The checker only accepts these prefixes:
FROMLIST: (posted to mailing list)
FROMGIT: (from maintainer tree)
UPSTREAM: (merged into mainline)
BACKPORT: (backported with modifications)
The QCLINUX: prefix is used for vendor-only changes with no upstream equivalent. While this prefix is valid for the repository's tagging policy (and passes tag-check), the check-patch-compliance checker will always fail for vendor-only commits because it enforces upstream-linkable prefixes only.
Options:
Accept the failure — This is expected behavior for vendor-only commits. The QCLINUX: prefix correctly indicates this is a Qualcomm-specific change (TGU device addition in staging dtso) with no upstream equivalent.
Change to FROMLIST: + add Link — Only if this patch has been posted upstream to a mailing list. If not posted, this would be incorrect.
Change to PENDING: + add Link — If the patch is work-in-progress and will be posted upstream. Note: PENDING: also fails check-patch-compliance (same limitation).
Recommendation: Accept the failure. This is a staging-specific device tree overlay for Hamoa platform, which is vendor-specific infrastructure. The QCLINUX: prefix is appropriate and the failure is a known checker limitation for vendor-only commits.
Reproduce locally:
cd kernel
git log --oneline -1 2ca9bc940e341d4c0f3adaf30f259c87c95342ef
# Verify prefix is QCLINUX:
Verdict
Ready to merge — The check-patch-compliance failure is a known limitation for vendor-only commits using the QCLINUX: prefix. All other checkers passed or skipped appropriately. The patch is clean (0 checkpatch warnings), builds successfully (dtb-check passed), and correctly uses the QCLINUX: prefix for vendor-specific staging content.

qcomlnxci · 2026-06-01T10:39:44Z

Test jobs on 2ca9bc9

qcomlnxci · 2026-06-01T10:39:46Z

Test Matrix

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

qlijarvis · 2026-06-06T07:28:29Z

PR #602 — validate-patch

PR:#602

Verdict	Issues	Detailed Report
✅	5	Full report

Final Summary

Commit 1 (hamoa):

Lore link present: No — QCLINUX: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only change, not posted upstream
PR present in qcom-next: Not checked — QCLINUX: vendor-only commit

Commit 2 (glymur):

Lore link present: No — QCLINUX: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only change, not posted upstream
PR present in qcom-next: Not checked — QCLINUX: vendor-only commit

Verdict: ✅ — click to expand
🔍 Patch Validation
PR:#602 - Add TGU and ETR devices in staging dtso files for hamoa and glymur
Upstream commit: N/A (vendor-only QCLINUX: commits)
Verdict: ✅ PASS
Commit 1: QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso
Commit Message
Check Status Note
Subject matches upstream N/A Vendor-only commit (QCLINUX: prefix)
Body preserves rationale ✅ Clear description: "Add TGU devices for supporting IPCB feature in staging dtso file"
Fixes tag present/correct N/A New feature addition, no Fixes tag needed
Authorship preserved ✅ Author: Jie Gan jie.gan@oss.qualcomm.com
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds hamoa-staging.dtbo build target
arch/arm64/boot/dts/qcom/hamoa-staging.dtso ✅ New staging overlay with 3 TGU devices
Commit 2: QCLINUX: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
Commit Message
Check Status Note
Subject matches upstream N/A Vendor-only commit (QCLINUX: prefix)
Body preserves rationale ✅ Clear description: "Add TGU devices for supporting IPCB feature in staging dtso file and add ETR devices for supporting DDR memory trace"
Fixes tag present/correct N/A New feature addition, no Fixes tag needed
Authorship preserved ✅ Author: Jie Gan jie.gan@oss.qualcomm.com
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds glymur-staging.dtbo build target
arch/arm64/boot/dts/qcom/glymur-staging.dtso ✅ New staging overlay with CTCU, replicators, TMC/ETR, and 4 TGU devices
Issues
None. Both commits are well-formed vendor-only changes with:
Proper QCLINUX: prefix indicating vendor-specific content
Clear commit messages explaining the purpose (IPCB support via TGU, DDR memory trace via ETR)
Correct Signed-off-by trailers
Appropriate use of staging dtso files for non-upstream hardware enablement
Valid device tree syntax (SPDX headers, /dts-v1/, /plugin/, proper node structure)
Verdict
Merge as-is. Both commits are properly formatted vendor-only device tree additions for staging overlays.
Final Summary
Commit 1 (hamoa):
Lore link present: No — QCLINUX: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only change, not posted upstream
PR present in qcom-next: Not checked — QCLINUX: vendor-only commit
Commit 2 (glymur):
Lore link present: No — QCLINUX: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only change, not posted upstream
PR present in qcom-next: Not checked — QCLINUX: vendor-only commit

qlijarvis · 2026-06-06T07:28:31Z

PR #602 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	Both commits passed with 0 errors, 0 warnings
dt-binding-check	⏭️	Skipped - no changes in Documentation/devicetree/bindings
dtb-check	✅	Test passed
sparse-check	⏭️	Skipped - no C code changes
check-uapi-headers	⏭️	Skipped - no UAPI header changes
check-patch-compliance	❌	FAILED - commits missing required prefix
tag-check	N/A	Not applicable for qcom-6.18.y branch
qcom-next-check	N/A	Not applicable for qcom-6.18.y branch

Detailed report: Full report

Checker analysis — click to expand
🤖 CI Checker Analysis (checker-log-analyzer)
PR:#602 - Add TGU and ETR devices in staging dtso files for hamoa and glymur
Source:https://github.com/qualcomm-linux/kernel-config/actions/runs/27055700691
Checker Result Summary
checkpatch ✅ Both commits passed with 0 errors, 0 warnings
dt-binding-check ⏭️ Skipped - no changes in Documentation/devicetree/bindings
dtb-check ✅ Test passed
sparse-check ⏭️ Skipped - no C code changes
check-uapi-headers ⏭️ Skipped - no UAPI header changes
check-patch-compliance ❌ FAILED - commits missing required prefix
tag-check N/A Not applicable for qcom-6.18.y branch
qcom-next-check N/A Not applicable for qcom-6.18.y branch
❌ check-patch-compliance
Root cause: Both commits use QCLINUX: prefix which is not a recognized upstream compliance prefix.
Failure details:
2026-06-06T07:18:41.5588772Z Checking commit: QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso
2026-06-06T07:18:41.5603473Z Commit summary does not start with a required prefix
2026-06-06T07:18:41.5652037Z Checking commit: QCLINUX: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
2026-06-06T07:18:41.5667322Z Commit summary does not start with a required prefix
2026-06-06T07:18:41.5682284Z ##[error]Process completed with exit code 1.
Affected commits:
204b4fc0bb91 - "QCLINUX: arm64: dts: qcom: hamoa: add TGU in staging dtso"
a2d40763d79d - "QCLINUX: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso"
Fix: The check-patch-compliance checker requires commit subjects to start with one of the following prefixes to indicate the upstream status:
UPSTREAM: - for patches already merged in mainline
BACKPORT: - for backported patches from a newer kernel version
FROMGIT: - for patches pulled from a maintainer's git tree
FROMLIST: - for patches posted to a mailing list but not yet merged
Since these are new staging device tree overlays specific to Qualcomm's internal tree (adding TGU and ETR devices for hamoa and glymur platforms), they should either:
If these are original Qualcomm-specific patches that won't go upstream: Remove the QCLINUX: prefix entirely and use a standard kernel subject format:
arm64: dts: qcom: hamoa: add TGU in staging dtso
arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
If these patches are intended for upstream submission: Use FROMLIST: prefix and include a Link: tag to the mailing list posting:
FROMLIST: arm64: dts: qcom: hamoa: add TGU in staging dtso
Reproduce locally:
cd /path/to/kernel
git fetch origin qcom-6.18.y
git checkout qcom-6.18.y
git fetch origin pull/602/head:pr-602
git merge pr-602 --no-commit
# Clone kernel-checkers
git clone https://github.com/qualcomm-linux/kernel-checkers.git ../kernel-checkers
# Run the checker
bash ../kernel-checkers/check-patch-compliance.sh --kernel-src . \
--base 997c1ece634c8c755c970af6895dba3a6c5e204a \
--head a2d40763d79d290abad1473eeafe105ef7a0af73
Verdict
1 blocker to fix: Both commits must be rebased to remove the QCLINUX: prefix or replace it with an appropriate upstream compliance prefix (UPSTREAM:, BACKPORT:, FROMGIT:, or FROMLIST:). All other checkers passed or were appropriately skipped.

Add TGU devices for supporting IPCB feature in staging dtso file. Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>

Add TGU devices for supporting IPCB feature in staging dtso file and add ETR devices for supporting DDR memory trace. Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>

qlijarvis · 2026-06-08T03:52:22Z

PR #602 — validate-patch

PR:#602

Verdict	Issues	Detailed Report
✅	0	Full report

Final Summary

Commit 1/2 (hamoa):

Lore link present: No — PENDING: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-staging change, not posted upstream
PR present in qcom-next: Not checked — PENDING: vendor-staging commit

Commit 2/2 (glymur):

Lore link present: No — PENDING: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-staging change, not posted upstream
PR present in qcom-next: Not checked — PENDING: vendor-staging commit

Verdict: ✅ — click to expand
🔍 Patch Validation
PR:#602 - Add TGU and ETR devices in staging dtso files for hamoa and glymur
Upstream commit: N/A (PENDING: prefix indicates not yet upstream)
Verdict: ✅ PASS (for vendor-staging commits)
Commit 1/2: PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso
Commit Message
Check Status Note
Subject matches upstream N/A PENDING: prefix; not upstream yet
Body preserves rationale ✅ Clear description of TGU devices for IPCB feature
Fixes tag present/correct N/A New feature, no Fixes tag needed
Authorship preserved ✅ Author: Jie Gan jie.gan@oss.qualcomm.com
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds hamoa-staging.dtbo build target
arch/arm64/boot/dts/qcom/hamoa-staging.dtso ✅ New staging overlay with 3 TGU devices
Technical Review
File structure: Proper DTSO overlay format with /dts-v1/; /plugin/; directives
License: BSD-3-Clause SPDX identifier present
Device nodes: Three TGU devices at addresses 0x10b0e000, 0x10b0f000, 0x10b10000
Compatible strings: Uses "qcom,tgu", "arm,primecell" pattern
Clocks: References &aoss_qmp with apb_pclk clock-name
Makefile: Clean addition with blank line separator
Commit 2/2: PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
Commit Message
Check Status Note
Subject matches upstream N/A PENDING: prefix; not upstream yet
Body preserves rationale ✅ Clear description of TGU (IPCB) and ETR (DDR trace)
Fixes tag present/correct N/A New feature, no Fixes tag needed
Authorship preserved ✅ Author: Jie Gan jie.gan@oss.qualcomm.com
Backport note (if applicable) N/A Not a backport
Diff
File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds glymur-staging.dtbo build target
arch/arm64/boot/dts/qcom/glymur-staging.dtso ✅ New staging overlay with CTCU, replicators, TMC/ETR, TGU devices
Technical Review
File structure: Proper DTSO overlay format with /dts-v1/; /plugin/; directives
License: BSD-3-Clause SPDX identifier present
Device nodes added:
1 CTCU device (0x10001000) with CoreSight topology connections
2 Replicators (0x10046000, 0x1004e000) for trace routing
2 TMC/ETR devices (0x10048000, 0x1004f000) with IOMMU and scatter-gather
4 TGU devices (0x11c02000, 0x11c0e000, 0x11c0f000, 0x11c10000)
1 Replicator extension (0x11c06000) adding out-port
CoreSight topology: Proper endpoint connections between components
IOMMU: ETR devices correctly reference &apps_smmu with stream IDs
Makefile: Clean addition with blank line separator
Issues
None. Both commits are well-formed vendor-staging patches.
Verdict
Merge as-is. Both commits are properly formatted vendor-staging patches (PENDING: prefix) adding device tree overlays for internal development. They follow kernel DT conventions, include proper licensing, and have clear commit messages explaining the purpose.
Final Summary
Commit 1/2 (hamoa):
Lore link present: No — PENDING: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-staging change, not posted upstream
PR present in qcom-next: Not checked — PENDING: vendor-staging commit
Commit 2/2 (glymur):
Lore link present: No — PENDING: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-staging change, not posted upstream
PR present in qcom-next: Not checked — PENDING: vendor-staging commit
Notes
PENDING: prefix: Both commits use the PENDING: prefix convention, indicating they are internal/staging changes not intended for immediate upstream submission
Staging overlays: Both files are -staging.dtso overlays, a common pattern for vendor-specific or experimental device enablement
No upstream validation needed: These are vendor-internal staging changes; no lore.kernel.org comparison or upstream status check is applicable
Technical quality: Device tree syntax, compatible strings, clock references, and CoreSight topology connections are all correctly structured

qlijarvis · 2026-06-08T03:52:23Z

PR #602 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues detected
dt-binding-check	⏭️	Skipped - no binding changes
dtb-check	✅	DTB validation passed
sparse-check	⏭️	Skipped - no C code changes
check-uapi-headers	⏭️	Skipped - no UAPI changes
check-patch-compliance	❌	FAILED - Invalid commit prefix
tag-check	N/A	Not applicable for qcom-6.18.y
qcom-next-check	N/A	Not applicable for qcom-6.18.y

Detailed report: Full report

Checker analysis — click to expand
🤖 CI Checker Analysis (checker-log-analyzer)
PR:#602 - Add TGU and ETR devices in staging dtso files for hamoa and glymur
Source:https://github.com/qualcomm-linux/kernel-config/actions/runs/27114270483
Checker Result Summary
checkpatch ✅ No style issues detected
dt-binding-check ⏭️ Skipped - no binding changes
dtb-check ✅ DTB validation passed
sparse-check ⏭️ Skipped - no C code changes
check-uapi-headers ⏭️ Skipped - no UAPI changes
check-patch-compliance ❌ FAILED - Invalid commit prefix
tag-check N/A Not applicable for qcom-6.18.y
qcom-next-check N/A Not applicable for qcom-6.18.y
❌ check-patch-compliance
Root cause: Both commits use "PENDING:" prefix which is not a valid commit subject prefix for Qualcomm Linux kernel.
Failure details:
Checking commit: PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso
Commit summary does not start with a required prefix
Checking commit: PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
Commit summary does not start with a required prefix
Fix: Update commit messages to use valid prefixes. For staging device tree overlays that are Qualcomm-specific and not intended for upstream submission, remove the "PENDING:" prefix entirely. The commits should be formatted as:
Commit 1:
arm64: dts: qcom: hamoa: add TGU in staging dtso
Add TGU devices for supporting IPCB feature in staging dtso file.
Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
Commit 2:
arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
Add TGU devices for supporting IPCB feature in staging dtso file and add
ETR devices for supporting DDR memory trace.
Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
Alternative: If these changes are based on upstream patches, use appropriate prefixes:
UPSTREAM: - for patches already merged in mainline
FROMLIST: - for patches posted to mailing lists but not yet merged
BACKPORT: - for patches backported from newer kernel versions
Reproduce locally:
git clone https://github.com/qualcomm-linux/kernel-checkers.git
cd kernel-checkers
./check-patch-compliance.sh --kernel-src /path/to/kernel --base <base_sha> --head <head_sha>
Verdict
1 blocker to fix: Remove "PENDING:" prefix from both commit messages. All other checkers passed successfully. Once the commit messages are updated (via git rebase -i and git commit --amend), force-push the branch to re-trigger CI.

qcomlnxci · 2026-06-08T05:01:34Z

Test jobs on 3be3604

qcomlnxci · 2026-06-08T05:01:37Z

Test Matrix

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

Jie Gan (jiegan0107) · 2026-06-08T06:43:46Z

This is qli-2.0 GA Critical Fix

Jie Gan (jiegan0107) requested review from a team, jingyiwang42, Nicolas Dechesne (ndechesne) and yijiyang May 19, 2026 14:01

Jie Gan (jiegan0107)force-pushed the qcom-6.18.y branch from 26afe68 to 02eeba0Compare May 20, 2026 01:25

Tingwei Zhang (quic-tingweiz) previously approved these changes May 20, 2026
View reviewed changes

Jie Gan (jiegan0107) dismissed Tingwei Zhang (quic-tingweiz)’s stale review via 0aa2de2May 25, 2026 07:24

Jie Gan (jiegan0107)force-pushed the qcom-6.18.y branch from 02eeba0 to 0aa2de2Compare May 25, 2026 07:24

qcomlnxci requested a review from a teamMay 25, 2026 07:26

Jie Gan (jiegan0107) requested a review from Tingwei Zhang (quic-tingweiz)May 25, 2026 07:26

Jie Gan (jiegan0107)force-pushed the qcom-6.18.y branch from 0aa2de2 to 77c712cCompare May 25, 2026 12:14

Jie Gan (jiegan0107) changed the title ~~Enable IPCB for multiple QCOM platforms~~Enable IPCB for HamoaMay 25, 2026

Tingwei Zhang (quic-tingweiz) previously approved these changes May 26, 2026
View reviewed changes

Jie Gan (jiegan0107)force-pushed the qcom-6.18.y branch from 77c712c to 2ca9bc9Compare May 26, 2026 22:39

Jie Gan (jiegan0107) requested a review from Salendarsingh Gaud (sgaud-quic)May 26, 2026 22:40

qcomlnxci requested a review from a teamMay 26, 2026 22:41

Tingwei Zhang (quic-tingweiz) previously approved these changes May 27, 2026
View reviewed changes

Jie Gan (jiegan0107) dismissed Tingwei Zhang (quic-tingweiz)’s stale review via a2d4076June 6, 2026 07:01

Jie Gan (jiegan0107)force-pushed the qcom-6.18.y branch from 2ca9bc9 to a2d4076Compare June 6, 2026 07:01

Jie Gan (jiegan0107) changed the title ~~Enable IPCB for Hamoa~~Enable IPCB for Hamoa and GlymurJun 6, 2026

qcomlnxci requested a review from a teamJune 6, 2026 07:03

Jie Gan (jiegan0107)force-pushed the qcom-6.18.y branch from a2d4076 to 3527ec4Compare June 6, 2026 07:35

Jie Gan (jiegan0107) added 2 commits June 8, 2026 11:23

PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso
650509a
Add TGU devices for supporting IPCB feature in staging dtso file. Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>

PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso
3be3604
Add TGU devices for supporting IPCB feature in staging dtso file and add ETR devices for supporting DDR memory trace. Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>

Jie Gan (jiegan0107)force-pushed the qcom-6.18.y branch from 3527ec4 to 3be3604Compare June 8, 2026 03:23

Shiraz Hashim (shashim-quic) approved these changes Jun 8, 2026
View reviewed changes

Tingwei Zhang (quic-tingweiz) approved these changes Jun 8, 2026
View reviewed changes

Shiraz Hashim (shashim-quic) added this to the qli-2.0 GA pull-request freeze milestone Jun 8, 2026

Shiraz Hashim (shashim-quic) approved these changes Jun 8, 2026
View reviewed changes

Salendarsingh Gaud (sgaud-quic) approved these changes Jun 8, 2026
View reviewed changes

Salendarsingh Gaud (sgaud-quic) merged commit 902605e into qualcomm-linux:qcom-6.18.yJun 8, 2026
6 of 8 checks passed

Uh oh!

Conversation

Jie Gan (jiegan0107) commented May 19, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qswat-orbit-externalBot commented May 19, 2026

Uh oh!

knaveen-qc commented May 20, 2026

PR #602 — validate-patch

Final Summary

🔍 Patch Validation

Commit 1 of 5 — PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso

Commit Message

Diff

Issues

Verdict

Final Summary

Commit 2 of 5 — PENDING: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block

Commit Message

Diff

Issues

Verdict

Final Summary

Commit 3 of 5 — PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso

Commit Message

Diff

Issues

Verdict

Final Summary

Commit 4 of 5 — PENDING: arm64: dts: qcom: sm8750: add TGU in staging dtso

Commit Message

Diff

Issues

Verdict

Final Summary

Commit 5 of 5 — PENDING: arm64: dts: qcom: kaanapali: add TGU in staging dtso

Commit Message

Diff

Issues

Verdict

Final Summary

Overall PR Summary

Uh oh!

knaveen-qc commented May 20, 2026

PR #602 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ check-patch-compliance

ℹ️ dtb-check — PASS with pre-existing warnings (informational)

Verdict

Uh oh!

qcomlnxci commented May 20, 2026

Test jobs on 02eeba0

Uh oh!

qcomlnxci commented May 20, 2026

Test Matrix

Uh oh!

knaveen-qc commented May 20, 2026

LAVA Failed Case Triage Summary

Uh oh!

Rahul Joshi (rahujosh) commented May 20, 2026

PR #602 — validate-patch

Final Summary

🔍 Patch Validation — PR #602

Commit 1 of 5 — PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso

Commit Message

Diff

Issues

Per-Commit Verdict

Commit 2 of 5 — PENDING: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block

Commit Message

Diff

Issues

Per-Commit Verdict

Commit 3 of 5 — PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso

Commit Message

Diff

Issues

Per-Commit Verdict

Commit 4 of 5 — PENDING: arm64: dts: qcom: sm8750: add TGU in staging dtso

Commit Message

Jie Gan (jiegan0107) commented May 19, 2026•
edited
Loading

Commit 1 of 5 — `PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso`

Commit 2 of 5 — `PENDING: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block`

Commit 3 of 5 — `PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso`

Commit 4 of 5 — `PENDING: arm64: dts: qcom: sm8750: add TGU in staging dtso`

Commit 5 of 5 — `PENDING: arm64: dts: qcom: kaanapali: add TGU in staging dtso`

Commit 1 of 5 — `PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso`

Commit 2 of 5 — `PENDING: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block`

Commit 3 of 5 — `PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso`

Commit 4 of 5 — `PENDING: arm64: dts: qcom: sm8750: add TGU in staging dtso`

Commit 5 of 5 — `PENDING: arm64: dts: qcom: kaanapali: add TGU in staging dtso`

Commit 1/5 — `PENDING: arm64: dts: qcom: glymur: add TGU and ETR in staging dtso`

Commit 2/5 — `PENDING: arm64: dts: qcom: glymur: add Coresight devices for APSS debug block`

Commit 3/5 — `PENDING: arm64: dts: qcom: hamoa: add TGU in staging dtso`

Commit 4/5 — `PENDING: arm64: dts: qcom: sm8750: add TGU in staging dtso`

Commit 5/5 — `PENDING: arm64: dts: qcom: kaanapali: add TGU in staging dtso`