FROMLIST: Add Coresight nodes for Shikra by jiegan0107 · Pull Request #824 · qualcomm-linux/kernel

Jie Gan (jiegan0107) · 2026-07-14T08:47:47Z

Add DT nodes for the CoreSight debug and trace subsystem on Qualcomm Shikra SoC.

CRs-Fixed: 4607858

qlijarvis · 2026-07-14T09:35:05Z

PR #824 — validate-patch

PR: #824

Verdict	Issues	Detailed Report
⚠️	2	Full report

Final Summary

Lore link present: Yes — both commits have correctly formatted Link: tags pointing to lore.kernel.org
Lore link matches PR commits: ⏭️ Cannot verify — network restrictions prevent fetching lore patches for comparison
Upstream patch status: ⏭️ Cannot verify — network restrictions prevent fetching lore threads to check acceptance/rejection signals
PR present in qcom-next:
- Commit 1/2: No — qcom,shikra-ctcu not found in qcom-next
- Commit 2/2: Partial — Different version found as 5f9f6b52570d with significantly different stats (+111 insertions, +98 deletions difference)

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #824 — Add CTCU device and coresight nodes for shikra
Commits: 2 commits (both FROMLIST)

Commit 1/2: FROMLIST: dt-bindings: arm: add CTCU device for shikra

Upstream commit: https://lore.kernel.org/all/20260714-add-coresight-nodes-for-shikra-v1-1-b1cf85962455@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL — Cannot verify diff faithfulness (network restricted); commit message structure correct

Commit Message

Check Status Note

Subject matches upstream ⏭️ Skipped Cannot fetch lore patch (network restricted)

Body preserves rationale ✅ Pass Clear description of CTCU fallback to SA8775p

Fixes tag present/correct N/A Not a fix commit

Authorship preserved ⏭️ Skipped FROMLIST: lore author in Signed-off-by (cannot verify From: without lore fetch)

Backport note (if applicable) N/A Not a backport

Link tag present ✅ Pass Link: tag present and correctly formatted

Diff

File Status Notes

Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml ⏭️ Skipped Cannot compare to lore patch (network restricted)

Upstream Patch Status

⏭️ Skipped — Cannot fetch lore thread to determine acceptance status (network restricted)

qcom-next Presence

⚠️ Not in qcom-next — Searched by file path and subject; qcom,shikra-ctcu not present in origin/qcom-next:Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml

Issues

Network restriction: Cannot fetch lore patch to verify diff faithfulness or upstream acceptance status

qcom-next absence: Commit not found in qcom-next; may not have landed yet

Verdict

Cannot fully validate due to network restrictions. Commit message structure is correct (FROMLIST prefix, Link tag, Signed-off-by present). Manual verification required: fetch lore patch and compare diff when network access is available.

Commit 2/2: FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes

Upstream commit: https://lore.kernel.org/all/20260714-add-coresight-nodes-for-shikra-v1-2-b1cf85962455@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL — qcom-next version differs; cannot verify lore faithfulness (network restricted)

Commit Message

Check Status Note

Subject matches upstream ⏭️ Skipped Cannot fetch lore patch (network restricted)

Body preserves rationale ✅ Pass Clear description of CoreSight subsystem addition

Fixes tag present/correct N/A Not a fix commit

Authorship preserved ⏭️ Skipped FROMLIST: lore author in Signed-off-by (cannot verify From: without lore fetch)

Backport note (if applicable) N/A Not a backport

Link tag present ✅ Pass Link: tag present and correctly formatted

Diff

File Status Notes

arch/arm64/boot/dts/qcom/shikra.dtsi ⚠️ Warning PR: +1499/-200 lines; qcom-next 5f9f6b52570d: +1388/-102 lines — stats differ significantly

Upstream Patch Status

⏭️ Skipped — Cannot fetch lore thread to determine acceptance status (network restricted)

qcom-next Presence

⚠️ Different version in qcom-next — Found as 5f9f6b52570d but:

qcom-next commit lacks FROMLIST: prefix and Link: tag

qcom-next commit date: Fri May 8 21:56:00 2026 vs PR: Tue, 14 Jul 2026 16:22:37

qcom-next stats: +1388/-102 vs PR: +1499/-200 — 209 more insertions, 98 more deletions in PR

This suggests the PR contains a newer or different revision than what landed in qcom-next.

Issues

Network restriction: Cannot fetch lore patch to verify diff faithfulness or upstream acceptance status

qcom-next divergence: PR commit differs significantly from qcom-next version:

Different line counts (+111 insertions, +98 deletions)

Different commit metadata (date, prefix, Link tag)

Possible causes:

PR is a newer lore revision (v2, v3, etc.) not yet in qcom-next

PR includes additional changes beyond the qcom-next commit

qcom-next commit was an earlier version before FROMLIST prefix was added

Verdict

Review required. The PR commit has significantly more changes than the qcom-next version. Without lore access, cannot determine if:

The extra changes are legitimate updates from a newer lore revision, or

The PR incorrectly bundles unrelated changes

Recommendation: Manually verify the lore link when network access is available to confirm the PR matches the posted patch series.

Final Summary

Lore link present: Yes — both commits have correctly formatted Link: tags pointing to lore.kernel.org

Lore link matches PR commits: ⏭️ Cannot verify — network restrictions prevent fetching lore patches for comparison

Upstream patch status: ⏭️ Cannot verify — network restrictions prevent fetching lore threads to check acceptance/rejection signals

PR present in qcom-next:

Commit 1/2: No — qcom,shikra-ctcu not found in qcom-next

Commit 2/2: Partial — Different version found as 5f9f6b52570d with significantly different stats (+111 insertions, +98 deletions difference)

Overall Assessment

⚠️ PARTIAL VALIDATION — Commit message structure is correct for both commits (FROMLIST prefix, Link tags, Signed-off-by present), but:

Network restrictions prevent full validation of diff faithfulness and upstream acceptance status

Commit 2/2 divergence from qcom-next version requires investigation:

PR has 209 more insertions and 98 more deletions than qcom-next 5f9f6b52570d

This could indicate a newer lore revision or unintended bundled changes

Action required: When network access is available:

Fetch both lore patches using b4 am <message-id>

Compare PR diffs against lore diffs using interdiff or filterdiff

Verify upstream acceptance status by scanning lore threads for merge/NAK signals

Investigate why commit 2/2 differs from qcom-next version — check if lore has multiple revisions (v1, v2, etc.)

qlijarvis · 2026-07-14T09:35:06Z

PR #824 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	✅	Schema validation passed
dtb-check	❌	Pre-existing iommus validation error exposed
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	Content mismatch with upstream link
tag-check	✅	Both commits have FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #824 - Add coresight nodes for shikra
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/29320312734

Checker Result Summary

checkpatch ✅ No style issues

dt-binding-check ✅ Schema validation passed

dtb-check ❌ Pre-existing iommus validation error exposed

sparse-check ⏭️ Skipped (no C/H changes)

check-uapi-headers ⏭️ Skipped (no UAPI changes)

check-patch-compliance ❌ Content mismatch with upstream link

tag-check ✅ Both commits have FROMLIST: prefix

❌ dtb-check

Root cause: Pre-existing video-codec@5a00000 node in shikra.dtsi has an iommus property with insufficient cells for the qcom,shikra-iris binding.

Failure details:
shikra-cqm-evk.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[43, 1920, 32]] is too short
shikra-cqm-evk-imx577-camera.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[43, 1920, 32]] is too short
shikra-cqs-evk.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[43, 1920, 32]] is too short
shikra-cqs-evk-imx577-camera.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[43, 1920, 32]] is too short
shikra-iqs-evk.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[42, 1920, 32]] is too short
shikra-iqs-evk-imx577-camera.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[42, 1920, 32]] is too short
Analysis: This PR adds coresight nodes to shikra.dtsi but does not modify the video-codec@5a00000 node. The error is flagged as "new" by the checker because:

The checker subtracts base_dtbs_errors.log from head_dtbs_errors.log

This error was not present in the base build, likely because these specific shikra DTB variants were not built or validated at the base commit

The video-codec@5a00000 node is pre-existing in shikra.dtsi and has an iommus property that doesn't meet the cell count requirements of the qcom,shikra-iris binding

Fix: The iommus property in the video-codec@5a00000 node needs additional cells. Check the qcom,shikra-iris binding schema to determine the required cell count and update the iommus property accordingly in shikra.dtsi.

Reproduce locally:
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb
❌ check-patch-compliance

Root cause: The second commit's content differs from the upstream patch referenced in the Link: tag.

Failure details:
Checking commit: FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes
Change is different from the one mentioned in Link
Analysis: The commit references:
Link: https://lore.kernel.org/all/20260714-add-coresight-nodes-for-shikra-v1-2-b1cf85962455@oss.qualcomm.com/
The checker fetched the upstream patch using b4 am and found that the diff content doesn't match. This could be due to:

Context line differences (false positive)

Additional changes not in the upstream version

Missing hunks from the upstream version

The upstream patch was updated after the Link was added

Fix:
# Fetch the upstream patch
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260714-add-coresight-nodes-for-shikra-v1-2-b1cf85962455@oss.qualcomm.com/ -o /tmp/upstream

# Compare the actual changes (+ and - lines only)
git format-patch -1 bbb3559721cf --stdout > /tmp/pr-patch.txt
diff <(awk '/^diff/,/^--$/' /tmp/pr-patch.txt | grep -E '^[+-][^+-]') \
     <(awk '/^diff/,/^--$/' /tmp/upstream/*.mbx | grep -E '^[+-][^+-]')
If the differences are:

Context-only shifts: Document this as an acceptable adaptation

Legitimate adaptations: Add a note in the commit message explaining the changes

Missing hunks: Cherry-pick the missing changes

Extra hunks: Consider splitting into a separate commit or removing if not needed

Reproduce locally:
cd /path/to/kernel
bash ../kernel-checkers/check-patch-compliance.sh --kernel-src . \
  --base 48143db58c4c --head bbb3559721cf
Verdict

2 blockers to fix before merge:

dtb-check (pre-existing): The video-codec@5a00000 iommus validation error is a pre-existing issue in shikra.dtsi that's now being exposed by this PR's DTB builds. While not introduced by this PR, it blocks CI. Options:

Fix the video-codec@5a00000 iommus property in this PR

Request maintainer approval to merge despite pre-existing tree issue

File a separate issue/PR to fix the video-codec node

check-patch-compliance (content mismatch): The second commit's diff doesn't match the upstream lore link. Investigate and either:

Update the commit to match upstream exactly

Document the intentional differences in the commit message

Update the Link: tag if the upstream patch was revised

Jie Gan (jiegan0107) · 2026-07-14T09:37:05Z

check-patch-compliance | ❌ | Content mismatch with upstream link -- | -- | --

The content of the lore link has issue. It shows the patch diff twice, but the content is correct in received message.

qcomlnxci · 2026-07-14T12:54:13Z

Test jobs on bbb3559

qcomlnxci · 2026-07-14T12:54:13Z

Test Matrix

Test Case	hamoa-iot-evk	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3
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	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
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	❌ Fail	❌ 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	◻️	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️	✅ Pass
WiFi_OnOff	◻️	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️	✅ Pass
adsp_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
cdsp_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
gpdsp_remoteproc	◻️	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	◻️	✅ Pass
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	◻️	✅ Pass
rngtest	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
shmbridge	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
smmu	◻️	❌ Fail	✅ Pass	❌ Fail	✅ Pass	◻️	❌ Fail
watchdog	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
wpss_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass

qcomlnxci · 2026-07-14T19:36:19Z

Test jobs on bbb3559

qcomlnxci · 2026-07-14T19:36:20Z

Test Matrix

Test Case	hamoa-iot-evk	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3
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	⚠️ skip	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
Ethernet	⚠️ skip	⚠️ skip	⚠️ skip	◻️	⚠️ skip	⚠️ skip	⚠️ skip
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	◻️	❌ Fail	✅ Pass	✅ Pass
GIC	✅ Pass	✅ Pass	✅ Pass	◻️	❌ Fail	✅ Pass	✅ Pass
IPA	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
Interrupts	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
OpenCV	✅ Pass	✅ Pass	✅ 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	✅ Pass	❌ Fail	❌ Fail	◻️	❌ Fail	❌ Fail	❌ Fail
WiFi_Firmware_Driver	❌ Fail	✅ Pass	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	❌ Fail	✅ Pass	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
gpdsp_remoteproc	⚠️ skip	✅ Pass	✅ Pass	◻️	⚠️ skip	✅ Pass	✅ Pass
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	✅ Pass
rngtest	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
shmbridge	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	❌ Fail	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail
watchdog	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass

Shiraz Hashim (shashim-quic)

https://lore.kernel.org/all/CAL_JsqLqbSrQKnnj2=57d-hFFeQ4xsDigLzmD-LHfufm=Mpp-Q@mail.gmail.com/

Please attend to NAK and resubmit.

Salendarsingh Gaud (sgaud-quic) · 2026-07-17T13:45:24Z

PR #824 — validate-patch

PR: #824

Verdict	Issues	Detailed Report
❌	2	Full report

Final Summary

Lore link present: Yes — both commits include lore.kernel.org links.
Lore link matches PR commits: Partial — commit 1 links stale v1; commit 2 includes v2 content but has extra non-lore diff churn.
Upstream patch status: In review — fetched mboxes show no applied/queued/merged, Reviewed-by/Acked-by, or NAK signal; v1 is superseded by v2.
PR present in qcom-next/topics: Fail - 1/2 commit(s) are missing from both qcom-next and topics

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: Add CoreSight nodes for Qualcomm Shikra SoC #824
Upstream commit: https://lore.kernel.org/all/20260714-add-coresight-nodes-for-shikra-v1-1-b1cf85962455@oss.qualcomm.com/ and https://lore.kernel.org/all/20260715-add-coresight-nodes-for-shikra-v2-2-ebd485e39a51@oss.qualcomm.com/
Verdict: ❌ FAIL

Commit Message

Check Status Note

Subject matches upstream ✅ Both subjects match the lore subjects with expected FROMLIST: prefix.

Body preserves rationale ✅ Rationale is preserved for both commits.

Fixes tag present/correct ✅ No Fixes tag expected for this feature series.

Authorship preserved ✅ FROMLIST: rule satisfied: lore author Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com> is present.

Backport note (if applicable) N/A Not a backport.

Diff

File Status Notes

Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml ✅ Same compatible addition; only target-tree context differs.

arch/arm64/boot/dts/qcom/shikra.dtsi ❌ CoreSight additions align with v2, but PR diff includes large remove/re-add blocks for existing nodes absent from lore.

Issues

Commit 1 links the v1 lore posting even though the local evidence contains a v2 series. The v2 cover says Changes in v2: remove MMIO for the ETM devices; update lore links to the current v2 revision where applicable.

Commit 2 is not a faithful diff representation of the v2 lore patch: lore v2 is 1295 insertions(+), while the PR commit is 1473 insertions(+), 178 deletions(-) and includes remove/re-add churn for existing sram, apps_smmu, wifi, interrupt-controller, mailbox, watchdog, and timer nodes.

Verdict

Do not merge as-is. Regenerate or split the DTS change so the PR patch is a faithful v2 lore import, and resolve the qcom-next/topics presence failure.

Final Summary

Lore link present: Yes — both commits include lore.kernel.org links.

Lore link matches PR commits: Partial — commit 1 links stale v1; commit 2 includes v2 content but has extra non-lore diff churn.

Upstream patch status: In review — fetched mboxes show no applied/queued/merged, Reviewed-by/Acked-by, or NAK signal; v1 is superseded by v2.

PR present in qcom-next/topics: Fail — integration report says 0/2 present, commit 1 missing, commit 2 partial only.

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: a5cf3debd8c3c660711ad586ad4bb84e9ca42635
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final

1/2 [PATCH 1/2] FROMLIST: dt-bindings: arm: add CTCU device for shikra missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing

2/2 [PATCH 2/2] FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial

Final Status

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

Salendarsingh Gaud (sgaud-quic) · 2026-07-17T13:45:25Z

PR #824 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	Commit 2 has `From:` / `Signed-off-by:` email mismatch.
dt-binding-check	❌	Modified CTCU binding rejects existing `qcom,hamoa-ctcu` users during `dtbs_check`.
dtb-check	❌	New Shikra DTB schema failures: `video-codec@5a00000` `iommus` list is too short.
sparse-check	⏭️	Skipped: no relevant C/H changes.
check-uapi-headers	⏭️	Skipped: no UAPI-relevant changes.
check-patch-compliance	❌	Commit 2 differs from linked lore patch and has author mismatch.
tag-check	✅	Target is not `qcom-next`/`qcom-next-staging`; both commits have valid `FROMLIST:` prefix.
qcom-next-check	✅	Both commits use `FROMLIST:`.

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: FROMLIST CTCU binding + Shikra CoreSight nodes (#824)
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/29465335551
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ❌ Commit 2 has From: / Signed-off-by: email mismatch.

dt-binding-check ❌ Modified CTCU binding rejects existing qcom,hamoa-ctcu users during dtbs_check.

dtb-check ❌ New Shikra DTB schema failures: video-codec@5a00000 iommus list is too short.

sparse-check ⏭️ Skipped: no relevant C/H changes.

check-uapi-headers ⏭️ Skipped: no UAPI-relevant changes.

check-patch-compliance ❌ Commit 2 differs from linked lore patch and has author mismatch.

tag-check ✅ Target is not qcom-next/qcom-next-staging; both commits have valid FROMLIST: prefix.

qcom-next-check ✅ Both commits use FROMLIST:.

❌ checkpatch

Root cause: Commit 44dda89cbc15 author email does not match its Signed-off-by.

Failure details:
Commit 44dda89cbc15 ("FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes")
WARNING: From:/Signed-off-by: email address mismatch:
'From: Jie Gan <jiegan@qti.qualcomm.com>' !=
'Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>'
Fix: Amend commit 2 so the author and sign-off use the same intended identity, preferably:
Jie Gan <jie.gan@oss.qualcomm.com>
Reproduce locally:
./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES --git a19888edbd0a4a46d624c9abe66d5f5ef4042abb..44dda89cbc158dc69b38869233b824736caf5e14
❌ dt-binding-check

Root cause: The changed qcom,coresight-ctcu.yaml adds qcom,shikra-ctcu but still does not allow existing qcom,hamoa-ctcu, so dtbs_check fails for Hamoa/Purwa DTBs.

Failure details:
hamoa-iot-evk.dtb: ctcu@10001000 (qcom,hamoa-ctcu): compatible: 'oneOf' conditional failed
['qcom,hamoa-ctcu', 'qcom,sa8775p-ctcu'] is too long
'qcom,hamoa-ctcu' is not one of ['qcom,qcs8300-ctcu', 'qcom,shikra-ctcu']
'qcom,hamoa-ctcu' is not one of ['qcom,sa8775p-ctcu']
from schema $id: http://devicetree.org/schemas/arm/qcom,coresight-ctcu.yaml#
Fix: Update Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml to also model the existing Hamoa fallback, for example by adding qcom,hamoa-ctcu to the first enum if it is compatible with qcom,sa8775p-ctcu.

Reproduce locally:
make -j$(nproc) O=out dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml
❌ dtb-check

Root cause: The Shikra DTB validation found new qcom,shikra-iris video-codec iommus entries with too few items after base/head subtraction.

Failure details:
Log Summary: Test failed
shikra-cqm-evk.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[47, 1920, 32]] is too short
shikra-cqm-evk-imx577-camera.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[47, 1920, 32]] is too short
shikra-cqs-evk.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[47, 1920, 32]] is too short
shikra-iqs-evk.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[46, 1920, 32]] is too short
Fix: Fix the Shikra video-codec@5a00000 node to satisfy the qcom,shikra-iris binding, likely by adding the missing iommus entries or correcting the binding if a single IOMMU stream is valid for this hardware.

Reproduce locally:
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb
❌ check-patch-compliance

Root cause: Commit 2 does not match the linked lore patch and its commit author differs from the original lore author.

Failure details:
Checking commit: FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes
Change is different from the one mentioned in Link
Author mismatch:
  Original author: Jie Gan <jie.gan@oss.qualcomm.com>
  Commit author : Jie Gan <jiegan@qti.qualcomm.com>
Fix: Amend commit 2 author to Jie Gan <jie.gan@oss.qualcomm.com>, then either make the patch content match the linked lore patch or repost the adapted version and update the Link: trailer.

Reproduce locally:
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260715-add-coresight-nodes-for-shikra-v2-2-ebd485e39a51@oss.qualcomm.com/ -o /tmp/out
Verdict

Not ready to merge. Fix the commit 2 author/sign-off mismatch, resolve the lore content mismatch, update the CTCU binding for existing Hamoa users, and fix the Shikra Iris iommus DTB schema failures.

Jie Gan (jiegan0107) · 2026-07-19T02:02:47Z

https://lore.kernel.org/all/CAL_JsqLqbSrQKnnj2=57d-hFFeQ4xsDigLzmD-LHfufm=Mpp-Q@mail.gmail.com/

Please attend to NAK and resubmit.

Shiraz Hashim (@shashim-quic), This is the comment for V1. I have updated the patch series to V2 to address the comment. The Link for the patch 1 is incorrect, I fixed it. Please help to review again.

qlijarvis · 2026-07-19T02:48:48Z

PR #824 — validate-patch

PR: #824

Verdict	Issues	Detailed Report
❌	0	Full report

Final Summary

Lore link present: Yes — both commits have valid Link: tags pointing to lore.kernel.org v2 patch series
Lore link matches PR commits: Partial — Patch 1/2 matches exactly; Patch 2/2 has authorship mismatch (From: field differs: PR uses jiegan@qti.qualcomm.com, lore uses jie.gan@oss.qualcomm.com). Diff content is semantically identical with expected context offsets due to tree state.
Upstream patch status: ⏳ Decision Pending — Posted to lore.kernel.org on 2026-07-15 as v2 series. No maintainer replies (applied/queued/NAK) found in the fetched mbox threads. Patch is under review; no definitive community decision yet.
PR present in qcom-next/topics: Fail - 1/2 commit(s) are missing from both qcom-next and topics

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: Add CoreSight nodes for Qualcomm Shikra SoC
Upstream commits:

Patch 1/2: https://lore.kernel.org/all/20260715-add-coresight-nodes-for-shikra-v2-1-ebd485e39a51@oss.qualcomm.com/

Patch 2/2: https://lore.kernel.org/all/20260715-add-coresight-nodes-for-shikra-v2-2-ebd485e39a51@oss.qualcomm.com/
Verdict: ❌ FAIL

Commit Message

Check Status Note

Subject matches upstream ✅ Patch 1: identical; Patch 2: identical

Body preserves rationale ✅ Both patches preserve the upstream commit body

Fixes tag present/correct N/A No Fixes tags in upstream patches

Authorship preserved ❌ Patch 2/2: Author mismatch — PR has From: Jie Gan <jiegan@qti.qualcomm.com> but lore patch has From: Jie Gan <jie.gan@oss.qualcomm.com>. For FROMLIST: commits, the lore author's Signed-off-by: must be present (it is: Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>), but the From: field should ideally match to avoid confusion.

Backport note (if applicable) N/A Not a backport — FROMLIST: prefix is correct

Diff

File Status Notes

Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml ⚠️ Context mismatch — lore patch inserts qcom,shikra-ctcu in alphabetical order after qcom,qcs8300-ctcu and before qcom,sm8750-ctcu. PR patch inserts it after qcom,qcs8300-ctcu but the surrounding context differs (PR has no qcom,glymur-ctcu, qcom,kaanapali-ctcu, qcom,sm8750-ctcu, qcom,x1e80100-ctcu entries visible in the hunk). The semantic change is identical (adds qcom,shikra-ctcu in the correct position), but the tree state differs.

arch/arm64/boot/dts/qcom/shikra.dtsi ⚠️ Context offset — lore patch applies at line 113, PR patch applies at line 171 (58-line offset). This indicates the PR is based on a tree with additional commits not present in the lore patch's baseline. The code content is identical (same coresight nodes, same structure), but the insertion point differs due to tree state.

Issues

Patch 2/2 authorship inconsistency — The PR commit has From: Jie Gan <jiegan@qti.qualcomm.com> (internal Qualcomm email) while the lore patch has From: Jie Gan <jie.gan@oss.qualcomm.com> (public email). For FROMLIST: commits, this is technically acceptable (the lore author's Signed-off-by: is present), but it creates confusion and breaks the chain of authorship. The submitter should preserve the original From: field or use git commit --amend --author="Jie Gan <jie.gan@oss.qualcomm.com>" to match the lore patch exactly.

Tree state divergence — Both patches show context offsets indicating the PR is based on a tree with additional changes not present in the lore patch's baseline. This is expected for vendor integration branches, but reviewers should verify that the semantic changes are identical (they are).

Verdict

Do not merge without correction. The authorship mismatch in patch 2/2 violates the principle that FROMLIST: commits should faithfully represent the upstream posting. While the lore author's Signed-off-by: is present (which satisfies the minimum requirement), the From: field should match the lore patch to maintain clear attribution.

Required fix:
# For patch 2/2 (commit eeb2027af77eb2ead0529dc5d7c486a60b620c1c)
git commit --amend --author="Jie Gan <jie.gan@oss.qualcomm.com>"
The diff content is semantically correct — both patches add the same code in the correct logical positions, with context offsets due to tree state differences (acceptable for vendor integration).

Final Summary

Lore link present: Yes — both commits have valid Link: tags pointing to lore.kernel.org v2 patch series

Lore link matches PR commits: Partial — Patch 1/2 matches exactly; Patch 2/2 has authorship mismatch (From: field differs: PR uses jiegan@qti.qualcomm.com, lore uses jie.gan@oss.qualcomm.com). Diff content is semantically identical with expected context offsets due to tree state.

Upstream patch status: ⏳ Decision Pending — Posted to lore.kernel.org on 2026-07-15 as v2 series. No maintainer replies (applied/queued/NAK) found in the fetched mbox threads. Patch is under review; no definitive community decision yet.

PR present in qcom-next/topics: Fail — Per integration_presence_report.md: Patch 1/2 is missing from both qcom-next and topics (no subject, patch-id, or full tree-content match found). Patch 2/2 shows partial presence (subject or partial tree evidence found, but full change not verified). Overall status: FAIL — 1/2 commits missing, 1/2 partial.

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: a5cf3debd8c3c660711ad586ad4bb84e9ca42635
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final

1/2 [PATCH 1/2] FROMLIST: dt-bindings: arm: add CTCU device for shikra missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing

2/2 [PATCH 2/2] FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial

Final Status

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

qlijarvis · 2026-07-19T02:48:49Z

PR #824 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	1 warning: From/Signed-off-by email mismatch
dt-binding-check	✅	Passed (pre-existing hamoa-ctcu errors unrelated to PR)
dtb-check	❌	Pre-existing video-codec iommus error (not introduced by PR)
sparse-check	⏭️	Skipped (no C/H files changed)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	2 issues: content mismatch + author mismatch
tag-check	✅	Both commits have valid FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #824 - FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/29669757376
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ❌ 1 warning: From/Signed-off-by email mismatch

dt-binding-check ✅ Passed (pre-existing hamoa-ctcu errors unrelated to PR)

dtb-check ❌ Pre-existing video-codec iommus error (not introduced by PR)

sparse-check ⏭️ Skipped (no C/H files changed)

check-uapi-headers ⏭️ Skipped (no UAPI changes)

check-patch-compliance ❌ 2 issues: content mismatch + author mismatch

tag-check ✅ Both commits have valid FROMLIST: prefix

❌ checkpatch

Root cause: Email address mismatch between From: and Signed-off-by: in commit eeb2027.

Failure details:
WARNING: From:/Signed-off-by: email address mismatch: 
  'From: Jie Gan <jiegan@qti.qualcomm.com>' != 
  'Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>'
Fix: The commit author uses jiegan@qti.qualcomm.com but the Signed-off-by: uses jie.gan@oss.qualcomm.com. These must match. Update the commit author to match the Signed-off-by:
git rebase -i a19888edbd0a  # mark eeb2027af77e as 'edit'
git commit --amend --author="Jie Gan <jie.gan@oss.qualcomm.com>" --no-edit
git rebase --continue
Reproduce locally:
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git a19888edbd0a..eeb2027af77e
❌ check-patch-compliance

Root cause: Two issues on commit eeb2027: (1) patch content differs from upstream lore link, (2) author email mismatch.

Failure details:
Checking commit: FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes
Change is different from the one mentioned in Link
Author mismatch:
  Original author: Jie Gan <jie.gan@oss.qualcomm.com>
  Commit author : Jie Gan <jiegan@qti.qualcomm.com>
Fix:
Author mismatch: Same as checkpatch — update commit author to jie.gan@oss.qualcomm.com:
git commit --amend --author="Jie Gan <jie.gan@oss.qualcomm.com>"
Content mismatch: Fetch the upstream patch and compare:
b4 am --single-message -C -l -3 \
  https://lore.kernel.org/all/20260715-add-coresight-nodes-for-shikra-v2-2-ebd485e39a51@oss.qualcomm.com/ \
  -o /tmp/upstream

# Compare the diff content
git format-patch -1 eeb2027af77e --stdout > /tmp/pr-patch.patch
diff -u /tmp/upstream/*.mbx /tmp/pr-patch.patch
If the content difference is legitimate (e.g., context-only shift or necessary adaptation for the target branch), document it in the commit message with an explanation. If there are missing or extra hunks, reconcile them.
Reproduce locally:
cd kernel
bash ../kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base a19888edbd0a --head eeb2027af77e
⚠️ dtb-check (pre-existing issue)

Root cause: Pre-existing video-codec@5a00000 node in shikra DTBs has iommus property with insufficient cells — not introduced by this PR.

Failure details:
shikra-cqm-evk.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[47, 1920, 32]] is too short
shikra-cqs-evk.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[47, 1920, 32]] is too short
shikra-iqs-evk.dtb: video-codec@5a00000 (qcom,shikra-iris): iommus: [[46, 1920, 32]] is too short
Analysis: The PR modifies shikra.dtsi to add coresight nodes but does not touch the video-codec@5a00000 node. This error is a pre-existing tree issue that gets exposed when building shikra DTBs. The dtb-check baseline subtraction should have filtered this out, but it appears in the log because the base build may have been incomplete or the error was not present at the exact base SHA.

Fix: This is not a blocker for this PR. The video-codec node's iommus property needs additional cells per the binding requirements, but that fix should be submitted as a separate patch targeting the pre-existing issue in shikra.dtsi.

Reproduce locally:
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb
⚠️ dt-binding-check (pre-existing hamoa-ctcu errors)

Root cause: Pre-existing qcom,hamoa-ctcu compatible strings in hamoa/purwa/x1e DTBs fail validation — not introduced by this PR.

Analysis: The PR adds qcom,shikra-ctcu to the binding YAML, and the binding check passed for the modified file:
dt_binding_check passed for Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml...
dtbs_check passed for Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml...
The errors shown in the log are for qcom,hamoa-ctcu compatible strings in other DTB files (hamoa-iot-evk, purwa-iot-evk, x1e001de-devkit, etc.) that are not part of this PR. These are pre-existing tree issues.

Fix: No action needed for this PR. The qcom,hamoa-ctcu compatible should be added to the binding YAML in a separate patch.

✅ tag-check

Analysis: Target branch is qcom-6.18.y (not qcom-next or qcom-next-staging), so subject prefix check is mandatory.

Both commits have valid FROMLIST: prefix:

✅ FROMLIST: dt-bindings: arm: add CTCU device for shikra

✅ FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes

Verdict: ✅ PASS

Verdict

2 blockers to fix before merge:

checkpatch + check-patch-compliance: Fix author email mismatch — change commit author from jiegan@qti.qualcomm.com to jie.gan@oss.qualcomm.com to match the Signed-off-by: trailer.

check-patch-compliance: Investigate and document the content mismatch between the PR patch and the upstream lore link. If the difference is legitimate (e.g., necessary adaptation), add an explanation to the commit message.

Non-blockers (pre-existing tree issues):

dtb-check video-codec iommus error — pre-existing in shikra.dtsi, not introduced by this PR

dt-binding-check hamoa-ctcu errors — pre-existing in other DTBs, not related to this PR's shikra-ctcu addition

qlijarvis · 2026-07-20T10:29:04Z

PR #824 — validate-patch

PR: #824

Verdict	Issues	Detailed Report
❌	7	Full report

Final Summary

Lore link present: Yes — https://lore.kernel.org/all/20260715-add-coresight-nodes-for-shikra-v2-1-ebd485e39a51@oss.qualcomm.com/ and https://lore.kernel.org/all/20260715-add-coresight-nodes-for-shikra-v2-2-ebd485e39a51@oss.qualcomm.com/
Lore link matches PR commits: No — PR commit messages link to lore v2 but PR patch content is based on lore v1. Commit 1/2 has context mismatch (missing other SoC compatibles in the binding file). Commit 2/2 includes MMIO regions for ETM devices that were removed in v2 (178 deletions not present in v2).
Upstream patch status: ⏳ Decision Pending — Both patches posted to linux-arm-msm on July 15, 2026 (v2 series). No maintainer replies, ACKs, NAKs, or merge confirmations found in the lore threads. Patches are under review.
PR present in qcom-next/topics: Fail - 1/2 commit(s) are missing from both qcom-next and topics

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #824 — Add CoreSight nodes for Qualcomm Shikra SoC (2 commits)
Upstream commit: https://lore.kernel.org/all/20260715-add-coresight-nodes-for-shikra-v2-0-ebd485e39a51@oss.qualcomm.com/
Verdict: ❌ FAIL

Commit Message

Check Status Note

Subject matches upstream ⚠️ Commit 1: Subject matches v2. Commit 2: Subject matches v2.

Body preserves rationale ✅ Both commits preserve the upstream commit message body.

Fixes tag present/correct N/A No Fixes tags in upstream patches.

Authorship preserved ✅ Author Jie Gan <jie.gan@oss.qualcomm.com> correctly preserved in both commits.

Backport note (if applicable) N/A FROMLIST prefix used correctly; no backport note needed.

Diff

File Status Notes

Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml ❌ Context mismatch: PR patch is based on an older file version. Lore v2 patch adds qcom,shikra-ctcu in alphabetical order between qcom,qcs8300-ctcu and qcom,sm8750-ctcu (with qcom,glymur-ctcu, qcom,kaanapali-ctcu, qcom,x1e80100-ctcu also present). PR patch only shows qcom,qcs8300-ctcu in context, missing the other entries.

arch/arm64/boot/dts/qcom/shikra.dtsi ❌ Wrong upstream version: PR patch shows 1651 insertions(+), 178 deletions(-) but lore v2 patch shows 1295 insertions(+), 0 deletions(-). The PR appears to be based on v1 (posted July 14), not v2 (posted July 15). v2 changelog states: "remove MMIO for the ETM devices." The PR includes MMIO regions that were removed in v2.

Issues

Commit 1/2: dt-bindings patch

The PR patch context shows only qcom,qcs8300-ctcu before the new qcom,shikra-ctcu entry, but the lore v2 patch shows the entry should be added in a list that includes qcom,glymur-ctcu, qcom,kaanapali-ctcu, qcom,qcs8300-ctcu, qcom,sm8750-ctcu, and qcom,x1e80100-ctcu.

This indicates the PR is based on an older version of the binding file that predates the addition of these other SoC compatibles.

The change itself (adding qcom,shikra-ctcu) is correct, but the context mismatch means this patch will not apply cleanly to a tree that already has the lore v2 patch.

Commit 2/2: DTS patch

The PR patch is based on lore v1 (July 14, 2026), not lore v2 (July 15, 2026).

The lore v2 changelog explicitly states: "Changes in v2: remove MMIO for the ETM devices."

The PR patch includes MMIO regions for ETM devices that were removed in v2, resulting in 178 deletions that are not present in the upstream v2 patch.

The PR commit message links to the v2 lore URL but contains v1 content.

Upstream Patch Status

Commit Community Verdict

[PATCH v2 1/2] dt-bindings: arm: add CTCU device for shikra ⏳ Decision Pending — Posted July 15, 2026; no maintainer replies, ACKs, or NAKs found in the lore thread.

[PATCH v2 2/2] arm64: dts: qcom: shikra: Add coresight nodes ⏳ Decision Pending — Posted July 15, 2026; no maintainer replies, ACKs, or NAKs found in the lore thread.

qcom-next/topics Presence

Per integration_presence_report.md:

Commit Status

1/2 dt-bindings: arm: add CTCU device for shikra ⚠️ Missing — Not found in qcom-next or topics

2/2 arm64: dts: qcom: shikra: Add coresight nodes ⚠️ Partial — Subject or partial tree evidence found, but full change not verified

Overall: FAIL — 1/2 commits missing from both qcom-next and topics; 1/2 commits show only partial presence.

Verdict

Do not merge. The PR contains patches based on lore v1 but links to lore v2 in the commit messages. This is a version mismatch.

Required fixes:

Commit 1/2: Rebase the dt-bindings patch onto a tree that includes the upstream v2 context (with qcom,glymur-ctcu, qcom,kaanapali-ctcu, qcom,sm8750-ctcu, qcom,x1e80100-ctcu already present). The current PR patch will not apply cleanly to a tree that has merged other recent CTCU binding updates.

Commit 2/2: Replace the v1-based DTS patch with the v2 version that removes MMIO for ETM devices. The current PR patch includes 178 deletions (MMIO regions) that were removed in v2. Update the patch to match the v2 content (1295 insertions, 0 deletions).

Wait for upstream acceptance: Both patches are still under review (Decision Pending). Consider waiting for maintainer ACKs or merge confirmation before integrating into qcom-next.

Final Summary

Lore link present: Yes — https://lore.kernel.org/all/20260715-add-coresight-nodes-for-shikra-v2-1-ebd485e39a51@oss.qualcomm.com/ and https://lore.kernel.org/all/20260715-add-coresight-nodes-for-shikra-v2-2-ebd485e39a51@oss.qualcomm.com/

Lore link matches PR commits: No — PR commit messages link to lore v2 but PR patch content is based on lore v1. Commit 1/2 has context mismatch (missing other SoC compatibles in the binding file). Commit 2/2 includes MMIO regions for ETM devices that were removed in v2 (178 deletions not present in v2).

Upstream patch status: ⏳ Decision Pending — Both patches posted to linux-arm-msm on July 15, 2026 (v2 series). No maintainer replies, ACKs, NAKs, or merge confirmations found in the lore threads. Patches are under review.

PR present in qcom-next/topics: Fail — 1/2 commits missing from both qcom-next and topics; 1/2 commits show only partial presence (per integration_presence_report.md).

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: a5cf3debd8c3c660711ad586ad4bb84e9ca42635
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final

1/2 [PATCH 1/2] FROMLIST: dt-bindings: arm: add CTCU device for shikra missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing

2/2 [PATCH 2/2] FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial

Final Status

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

qlijarvis · 2026-07-20T10:29:06Z

PR #824 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	✅	Schema validation passed (pre-existing warnings in other DTBs)
dtb-check	❌	`iommus` property too short in shikra video-codec node
sparse-check	⏭️	Skipped (no C/H file changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	Content mismatch detected for commit 2/2
tag-check	✅	Both commits have valid `FROMLIST:` prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #824 - Add CTCU device and coresight nodes for shikra
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/29732822883

Checker Result Summary

checkpatch ✅ No style issues

dt-binding-check ✅ Schema validation passed (pre-existing warnings in other DTBs)

dtb-check ❌ iommus property too short in shikra video-codec node

sparse-check ⏭️ Skipped (no C/H file changes)

check-uapi-headers ⏭️ Skipped (no UAPI changes)

check-patch-compliance ❌ Content mismatch detected for commit 2/2

tag-check ✅ Both commits have valid FROMLIST: prefix

❌ dtb-check

Root cause: The iommus property in shikra.dtsi video-codec@5a00000 node has only 3 cells [47, 1920, 32] but the qcom,shikra-iris binding requires more cells.

Failure details:
/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb: 
  video-codec@5a00000 (qcom,shikra-iris): iommus: [[47, 1920, 32]] is too short

/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dtb: 
  video-codec@5a00000 (qcom,shikra-iris): iommus: [[47, 1920, 32]] is too short

/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/shikra-iqs-evk.dtb: 
  video-codec@5a00000 (qcom,shikra-iris): iommus: [[46, 1920, 32]] is too short
Fix: Check the qcom,shikra-iris binding schema to determine the required number of iommus cells. The binding likely requires 4 or more cells per entry. Update arch/arm64/boot/dts/qcom/shikra.dtsi to add the missing cell(s) to the iommus property in the video-codec@5a00000 node.

Reproduce locally:
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb
❌ check-patch-compliance

Root cause: The second commit's content differs from the upstream patch at the provided lore.kernel.org link.

Failure details:
Checking commit: FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes
Change is different from the one mentioned in Link
Fix: Fetch the upstream patch and compare:
b4 am --single-message -C -l -3 \
  https://lore.kernel.org/all/20260715-add-coresight-nodes-for-shikra-v2-2-ebd485e39a51@oss.qualcomm.com/ \
  -o /tmp/upstream

# Compare the diff content
git format-patch -1 3a3411080fff2f74f7ebebf619787aba93b83aa3 --stdout > /tmp/pr-commit.patch
diff -u /tmp/upstream/*.mbx /tmp/pr-commit.patch
Determine if the difference is:

Context-only shift (line numbers changed due to base differences) → acceptable, no action needed

Legitimate adaptation (e.g., conflict resolution, base difference) → document the adaptation in the commit message

Missing hunk → add the missing changes

Extra hunk → remove or attribute separately

If the change is intentional (e.g., adapted for the target branch), add a note to the commit message explaining the difference, or consider using BACKPORT: prefix instead of FROMLIST: if substantial modifications were made.

Reproduce locally:
cd kernel-checkers
./check-patch-compliance.sh <base_sha> <head_sha>
⚠️ dt-binding-check (pre-existing warnings)

While dt-binding-check passed for the new binding Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml, the dtbs_check phase shows warnings for pre-existing DTBs using qcom,hamoa-ctcu:
ctcu@10001000 (qcom,hamoa-ctcu): compatible: 'oneOf' conditional failed, one must be fixed:
  'qcom,hamoa-ctcu' is not one of ['qcom,qcs8300-ctcu', 'qcom,shikra-ctcu']
  'qcom,hamoa-ctcu' is not one of ['qcom,sa8775p-ctcu']
Analysis: This is a pre-existing tree issue, not caused by this PR. The new binding adds qcom,shikra-ctcu but does not include qcom,hamoa-ctcu, which is used in other DTBs (hamoa-iot-evk, purwa-iot-evk, x1e001de-devkit, etc.). These DTBs were already in the tree before this PR.

Action: No fix required for this PR. The binding validation passed. The warnings are for unrelated DTBs that need their own binding update.

Verdict

2 blockers must be fixed before merge:

dtb-check failure — Fix the iommus property cell count in shikra.dtsi video-codec@5a00000 node

check-patch-compliance failure — Verify and reconcile the content difference between the PR commit and the upstream lore patch, or document the adaptation

The pre-existing qcom,hamoa-ctcu binding warnings are not blockers for this PR.

The CTCU device for the Shikra shares the same configurations as SA8775p. Add a fallback to enable the CTCU for the Shikra to utilize the compatible of the SA8775p. Link: https://lore.kernel.org/all/20260723-add-coresight-nodes-for-shikra-v5-1-fd5494471b36@oss.qualcomm.com/ Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>

Add DT nodes for the CoreSight debug and trace subsystem on Qualcomm Shikra SoC. Link: https://lore.kernel.org/all/20260723-add-coresight-nodes-for-shikra-v5-2-fd5494471b36@oss.qualcomm.com/ Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>

qlijarvis · 2026-07-23T10:47:32Z

PR #824 — validate-patch

PR: #824

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

Lore link present: Yes — both commits have correct lore.kernel.org links in Link: tags
Lore link matches PR commits: Yes — diff content is faithful to lore; context differences are due to different base tree states (expected and acceptable)
Upstream patch status: ⏳ Decision Pending — posted to linux-arm-msm on July 23, 2026 (today); no review comments or acceptance signals yet; patch series is at v5
PR present in qcom-next/topics: Fail - 1/2 commit(s) are missing from both qcom-next and topics

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #824 - Add CoreSight nodes for Qualcomm Shikra SoC (2 commits)
Upstream commits:

Patch 1/2: https://lore.kernel.org/all/20260723-add-coresight-nodes-for-shikra-v5-1-fd5494471b36@oss.qualcomm.com/

Patch 2/2: https://lore.kernel.org/all/20260723-add-coresight-nodes-for-shikra-v5-2-fd5494471b36@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Commit 1/2: FROMLIST: dt-bindings: arm: qcom,coresight-ctcu: Add Shikra

Commit Message

Check Status Note

Subject matches upstream ✅ Subject correctly prefixed with FROMLIST: and matches lore patch

Body preserves rationale ✅ Body text identical to upstream

Fixes tag present/correct N/A No Fixes tag in upstream or PR (new feature, not a fix)

Authorship preserved ✅ From: matches lore author (Jie Gan); FROMLIST: allows submitter to differ, but here they match

Backport note N/A Not a backport; FROMLIST: prefix correct for pending upstream patch

Link tag present ✅ Correct lore.kernel.org link present

Diff Comparison

File Status Notes

Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml ✅ Content identical; context differs (PR based on older tree missing glymur/kaanapali/sm8750/x1e80100 entries) — this is expected and acceptable

Diff analysis: The actual change (adding qcom,shikra-ctcu to the enum) is identical between PR and lore. The context difference (PR shows only qcom,qcs8300-ctcu before the new entry, while lore shows additional entries) is due to the PR being based on an earlier tree state. This is a legitimate context-only delta and does not affect correctness.

Upstream Patch Status

Community verdict: ⏳ Decision Pending — Posted to linux-arm-msm@vger.kernel.org on July 23, 2026 (today). No review comments, Acked-by, Reviewed-by, or maintainer acceptance signals found in the thread yet. Patch is v5, indicating prior review iterations, but current revision has not received formal acceptance.

Commit 2/2: FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes

Commit Message

Check Status Note

Subject matches upstream ✅ Subject correctly prefixed with FROMLIST: and matches lore patch

Body preserves rationale ✅ Body text identical to upstream

Fixes tag present/correct N/A No Fixes tag in upstream or PR (new feature, not a fix)

Authorship preserved ✅ From: matches lore author (Jie Gan)

Backport note N/A Not a backport; FROMLIST: prefix correct

Link tag present ✅ Correct lore.kernel.org link present

Diff Comparison

File Status Notes

arch/arm64/boot/dts/qcom/shikra.dtsi ✅ Content identical; context line numbers differ (PR: @@ -171,6 +171,88 vs lore: @@ -113,6 +113,88) due to different base tree state — acceptable

Diff analysis: The actual coresight node additions (dummy-eud, etm0-7, funnel nodes, replicators, tmc nodes, stm, ctcu, etc.) are identical between PR and lore. The hunk offset difference (PR starts at line 171, lore at line 113) indicates the PR tree has additional content earlier in the file compared to the lore base. This is expected when applying upstream patches to a vendor tree with additional changes. The 1473 insertions / 178 deletions match the scale of adding a complete coresight subsystem.

Upstream Patch Status

Community verdict: ⏳ Decision Pending — Same status as patch 1/2; posted today with no review activity yet.

Integration Presence Check

Per integration_presence_report.md:

Commit qcom-next topics Final Status

1/2 (dt-bindings) ❌ missing ❌ missing missing

2/2 (dts nodes) ⚠️ partial ⚠️ partial partial

Analysis:

Commit 1/2: Not found in qcom-next or topics branches by subject, patch-id, or full tree-content match.

Commit 2/2: Partial evidence found (subject or partial tree match) but full change not verified in qcom-next or topics.

Impact: The integration presence report indicates these patches are not yet fully integrated into qcom-next or the topic branches. This is consistent with the upstream status (Decision Pending) — the patches were posted to the mailing list today and have not been merged anywhere yet.

Issues Found

None for commit message or diff correctness. Both commits faithfully represent their lore upstream sources.

Integration concern (not a validation failure):
The patches are not present in qcom-next or topics, and upstream review is still pending. Merging these commits now means pulling in patches that:

Have not been accepted by the upstream maintainers yet

Are not yet integrated into the Qualcomm integration branches

Could potentially be revised (this is v5, indicating prior iterations)

Recommendation

From a patch validation perspective: The PR commits are faithful representations of the lore upstream patches. Commit messages are correct, authorship is preserved, FROMLIST: prefix is appropriate, and diffs match the upstream content (context differences are expected and acceptable).

From an integration perspective: Consider whether it is appropriate to merge patches that are:

Still under upstream review (posted today, no acceptance signals yet)

Not yet present in qcom-next or topics branches

At revision v5 (may be revised again based on maintainer feedback)

Suggested action:

If the goal is to track upstream submissions closely and test them in the vendor tree before acceptance, merging is reasonable with the understanding that future revisions may require updates.

If the policy is to wait for upstream acceptance or qcom-next integration before merging, hold this PR until the patches receive maintainer Acked-by/Reviewed-by or are merged into a maintainer tree.

Final Summary

Lore link present: Yes — both commits have correct lore.kernel.org links in Link: tags

Lore link matches PR commits: Yes — diff content is faithful to lore; context differences are due to different base tree states (expected and acceptable)

Upstream patch status: ⏳ Decision Pending — posted to linux-arm-msm on July 23, 2026 (today); no review comments or acceptance signals yet; patch series is at v5

PR present in qcom-next/topics: No — commit 1/2 is missing from both qcom-next and topics; commit 2/2 shows partial evidence but full change not verified; consistent with patches being freshly posted upstream today

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: 07f50dc44eddcf748a99d1a7523a466438bfffa6
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final

1/2 [PATCH 1/2] FROMLIST: dt-bindings: arm: qcom,coresight-ctcu: Add missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing

2/2 [PATCH 2/2] FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial

Final Status

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

qlijarvis · 2026-07-23T10:47:34Z

PR #824 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	All commits pass style checks
dt-binding-check	⚠️	Binding passes but exposes pre-existing hamoa-ctcu issue
dtb-check	⚠️	Pre-existing video-codec iommus issue exposed
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	Content mismatch on commit 2/2
tag-check	✅	Both commits have FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: Add coresight nodes for Shikra (#824)
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/29996229279

Checker Result Summary

checkpatch ✅ All commits pass style checks

dt-binding-check ⚠️ Binding passes but exposes pre-existing hamoa-ctcu issue

dtb-check ⚠️ Pre-existing video-codec iommus issue exposed

sparse-check ⏭️ Skipped (no C/H changes)

check-uapi-headers ⏭️ Skipped (no UAPI changes)

check-patch-compliance ❌ Content mismatch on commit 2/2

tag-check ✅ Both commits have FROMLIST: prefix

❌ check-patch-compliance

Root cause: The second commit differs from the upstream lore patch at the provided Link.

Failure details:
Checking commit: FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes
Change is different from the one mentioned in Link
Analysis:
The checker detected that commit d11422423e5b ("FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes") has different content than the patch at:
https://lore.kernel.org/all/20260723-add-coresight-nodes-for-shikra-v5-2-fd5494471b36@oss.qualcomm.com/

This could be due to:

Context-only differences (line number shifts from other patches)

Legitimate local adaptations not yet posted upstream

Missing or extra hunks

Fix:
Fetch the upstream patch and compare:
b4 am --single-message -C -l -3 \
  https://lore.kernel.org/all/20260723-add-coresight-nodes-for-shikra-v5-2-fd5494471b36@oss.qualcomm.com/ \
  -o /tmp/upstream

# Compare added/removed lines only
git format-patch -1 d11422423e5b --stdout | \
  awk '/^diff/,/^--$/' | grep -E '^[+-][^+-]' > /tmp/pr.diff

awk '/^diff/,/^--$/' /tmp/upstream/*.mbx | \
  grep -E '^[+-][^+-]' > /tmp/upstream.diff

diff /tmp/pr.diff /tmp/upstream.diff
If the difference is:

Context-only (line numbers shifted) → False positive, no action needed

Legitimate adaptation → Document the change in the commit message

Missing hunk → Add the missing change

Extra hunk → Remove or attribute separately

Reproduce locally:
cd /path/to/kernel
./scripts/check-patch-compliance.sh --base 4def074fd0b5 --head d11422423e5b
⚠️ dt-binding-check

Root cause: The binding change exposes a pre-existing issue with qcom,hamoa-ctcu compatibility.

Failure details:
/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dtb: 
  ctcu@10001000 (qcom,hamoa-ctcu): compatible: 'oneOf' conditional failed, one must be fixed:
    ['qcom,hamoa-ctcu', 'qcom,sa8775p-ctcu'] is too long
    'qcom,hamoa-ctcu' is not one of ['qcom,qcs8300-ctcu', 'qcom,shikra-ctcu']
    'qcom,hamoa-ctcu' is not one of ['qcom,sa8775p-ctcu']
Analysis:
The PR adds qcom,shikra-ctcu to the binding's enum list. However, the tree already contains DTBs using qcom,hamoa-ctcu with the qcom,sa8775p-ctcu fallback. The binding schema now rejects this because qcom,hamoa-ctcu is not in the allowed list.

This is a pre-existing tree issue exposed by the binding change. The hamoa-ctcu compatible was already in use but never added to the binding.

Fix:
Add qcom,hamoa-ctcu to the binding enum alongside qcom,shikra-ctcu:
- items:
    - enum:
        - qcom,hamoa-ctcu
        - qcom,qcs8300-ctcu
        - qcom,shikra-ctcu
    - const: qcom,sa8775p-ctcu
Note: The binding check itself passed for the changed file (qcom,coresight-ctcu.yaml), but the dtbs_check phase exposed this issue when building DTBs that reference the binding.

⚠️ dtb-check

Root cause: Pre-existing video-codec@5a00000 iommus property issue in shikra DTBs, unrelated to this PR.

Failure details:
/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb: 
  video-codec@5a00000 (qcom,shikra-iris): iommus: [[47, 1920, 32]] is too short
/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dtb: 
  video-codec@5a00000 (qcom,shikra-iris): iommus: [[47, 1920, 32]] is too short
/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/shikra-iqs-evk.dtb: 
  video-codec@5a00000 (qcom,shikra-iris): iommus: [[46, 1920, 32]] is too short
Analysis:
The checker reports these as NEW errors (after filtering base errors with grep -vFf base_dtbs_errors.log). However, this PR only adds coresight nodes (ctcu@, stm@, tpdm@, funnel@, etc.) and does not touch the video-codec@5a00000 node.

This is likely a false positive caused by:

The base build may have failed or been incomplete, causing the baseline subtraction to miss these errors

The qcom,shikra-iris binding may have been updated recently, changing the required iommus cell count

The iommus property has 3 cells [47, 1920, 32] but the binding expects more. This is a pre-existing tree issue, not introduced by this PR.

Fix (if genuinely new):
Check the qcom,shikra-iris binding for the required iommus cell count and update the DTS:
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-cqm-evk.dtb
Recommendation: Verify this error exists at the base commit (4def074fd0b5) before attributing it to this PR. If it does, this is a false positive and should be fixed separately.

Verdict

2 blockers to fix before merge:

check-patch-compliance (blocker): Resolve the content mismatch between commit d11422423e5b and the upstream lore patch. Verify the difference is legitimate or update the commit.

dt-binding-check (blocker): Add qcom,hamoa-ctcu to the binding enum to fix the pre-existing compatibility issue exposed by this PR's binding change.

Non-blockers (pre-existing issues):

dtb-check video-codec@5a00000 iommus errors are likely pre-existing and unrelated to this PR's coresight changes.

qcomlnxci · 2026-07-23T13:13:14Z

Test jobs on d114224

qcomlnxci · 2026-07-23T13:13:15Z

Test Matrix

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

Salendarsingh Gaud (sgaud-quic) · 2026-07-24T11:49:40Z

Jie Gan (@jiegan0107) can you share mainline PR's for all the commit.

Jie Gan (jiegan0107) · 2026-07-24T11:52:31Z

Jie Gan (Jie Gan (@jiegan0107)) can you share mainline PR's for all the commit.

Mainline PR: qualcomm-linux/kernel-topics#1102

Added in CR as well.

Salendarsingh Gaud (sgaud-quic) · 2026-07-24T12:08:11Z

Jie Gan (Jie Gan (Jie Gan (@jiegan0107))) can you share mainline PR's for all the commit.

Mainline PR: qualcomm-linux/kernel-topics#1102

Added in CR as well.

i see only one commit in mainline PR. where is DT binding PR for mainline ?

Jie Gan (jiegan0107) · 2026-07-24T12:10:55Z

Jie Gan (Jie Gan (Jie Gan (Jie Gan (@jiegan0107)))) can you share mainline PR's for all the commit.

Mainline PR: qualcomm-linux/kernel-topics#1102
Added in CR as well.

i see only one commit in mainline PR. where is DT binding PR for mainline ?

For Shikra, the change is merged with early topic branch without dt-binding commit. The PR merged before post upstream.

Jie Gan (jiegan0107) requested review from a team, knaveen-qc, Nicolas Dechesne (ndechesne) and Tingwei Zhang (quic-tingweiz) July 14, 2026 08:47

Jie Gan (jiegan0107) force-pushed the shikra-coresight branch from 3b33437 to bbb3559 Compare July 14, 2026 08:59

Tingwei Zhang (quic-tingweiz) previously approved these changes Jul 14, 2026

View reviewed changes

Jie Gan (jiegan0107) dismissed Tingwei Zhang (quic-tingweiz)’s stale review via a47d268 July 15, 2026 07:48

Jie Gan (jiegan0107) force-pushed the shikra-coresight branch from bbb3559 to a47d268 Compare July 15, 2026 07:48

qcomlnxci requested review from a team and Rajendra (rrnayak) July 15, 2026 07:49

Jie Gan (jiegan0107) force-pushed the shikra-coresight branch from a47d268 to 44dda89 Compare July 16, 2026 01:54

Shiraz Hashim (shashim-quic) requested changes Jul 17, 2026

View reviewed changes

Jie Gan (jiegan0107) force-pushed the shikra-coresight branch from 44dda89 to eeb2027 Compare July 19, 2026 02:08

qcomlnxci requested a review from a team July 19, 2026 02:09

Jie Gan (jiegan0107) requested review from Tingwei Zhang (quic-tingweiz) and Shiraz Hashim (shashim-quic) July 19, 2026 02:10

Jie Gan (jiegan0107) force-pushed the shikra-coresight branch from eeb2027 to 3a34110 Compare July 20, 2026 09:47

Jie Gan (jiegan0107) added 2 commits July 23, 2026 17:35

Jie Gan (jiegan0107) force-pushed the shikra-coresight branch from 3a34110 to d114224 Compare July 23, 2026 09:37

Shiraz Hashim (shashim-quic) approved these changes Jul 23, 2026

View reviewed changes

Uh oh!

Conversation

Jie Gan (jiegan0107) commented Jul 14, 2026

Uh oh!

qlijarvis commented Jul 14, 2026

PR #824 — validate-patch

Final Summary

🔍 Patch Validation

Commit 1/2: FROMLIST: dt-bindings: arm: add CTCU device for shikra

Commit Message

Diff

Upstream Patch Status

qcom-next Presence

Issues

Verdict

Commit 2/2: FROMLIST: arm64: dts: qcom: shikra: Add coresight nodes

Commit Message

Diff

Upstream Patch Status

qcom-next Presence

Issues

Verdict

Final Summary

Overall Assessment

Uh oh!

qlijarvis commented Jul 14, 2026

PR #824 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ dtb-check

❌ check-patch-compliance

Verdict

Uh oh!

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

Uh oh!

Uh oh!

qcomlnxci commented Jul 14, 2026

Test jobs on bbb3559

Uh oh!

qcomlnxci commented Jul 14, 2026

Test Matrix

Uh oh!

qcomlnxci commented Jul 14, 2026

Test jobs on bbb3559

Uh oh!

qcomlnxci commented Jul 14, 2026

Test Matrix

Uh oh!

Shiraz Hashim (shashim-quic) left a comment

Choose a reason for hiding this comment

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented Jul 17, 2026

PR #824 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Issues

Verdict

Final Summary

Deterministic Integration Presence

Integration Presence Report

Final Status

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented Jul 17, 2026

PR #824 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ checkpatch

❌ dt-binding-check

❌ dtb-check

❌ check-patch-compliance

Verdict

Uh oh!

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

Uh oh!

Uh oh!

qlijarvis commented Jul 19, 2026

PR #824 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Jie Gan (jiegan0107) commented Jul 14, 2026 •

edited

Loading

Jie Gan (jiegan0107) commented Jul 19, 2026 •

edited

Loading