QCLINUX: arm64: dts: qcom: add Purwa CAMX EL2 overlay by michael-jihan-qcom · Pull Request #610 · qualcomm-linux/kernel

michael-jihan-qcom · 2026-05-22T11:02:40Z

Add a device tree overlay to enable EL2 boot support for the Purwa platform with CAMX configuration.

CRs-Fixed: 4546912

qswat-orbit-external · 2026-05-22T11:02:48Z

Merge Check Failed: CR Not Eligible for Merge

CR 4546912 is not eligible for merge.

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

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

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

qswat-orbit-external · 2026-05-22T11:05:33Z

Merge Check Failed: CR Not Eligible for Merge

CR 4546912 is not eligible for merge.

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

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

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

quic-vikramsa · 2026-05-22T11:33:01Z

LGTM

qlijarvis · 2026-05-22T11:42:22Z

PR #610 — validate-patch

PR: #610

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 change, not posted upstream
PR present in qcom-next: Not checked — QCLINUX: vendor-only commit

Verdict: N/A — click to expand

🔍 Patch Validation

PR: #610 - QCLINUX: arm64: dts: qcom: add purwa CAMX EL2 overlay
Upstream commit: N/A (vendor-only commit)
Verdict: ⏭️ SKIPPED (not applicable)

Reason

This commit uses the QCLINUX: prefix, which indicates a vendor-only change with no upstream equivalent. According to the validate-patch skill scope, commits with QCLINUX:, PENDING:, or WORKAROUND: prefixes have no upstream lore link by design and cannot be validated against lore.kernel.org sources.

Commit Message

Check Status Note

Subject matches upstream N/A Vendor-only commit

Body preserves rationale ✅ Brief description provided

Fixes tag present/correct N/A Not a fix

Authorship preserved ✅ Proper From: and Signed-off-by:

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

Diff

File Status Notes

arch/arm64/boot/dts/qcom/Makefile ✅ Adds new dtb target for purwa-camx-el2

arch/arm64/boot/dts/qcom/purwa-camx-el2.dtso ✅ New overlay for EL2 boot with CAMX IOMMU config

Observations

Commit structure: Well-formed with proper SPDX license, copyright, and sign-off

Content: Adds device tree overlay for Purwa platform EL2 boot support with camera ICP IOMMU configuration

CRs-Fixed tag: Present (4546912) — indicates internal tracking

No upstream validation required: This is vendor-specific platform enablement

Verdict

This is a vendor-only commit that does not require upstream validation. The commit message and diff structure are correct for a QCLINUX: prefixed change.

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-22T11:42:23Z

PR #610 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	Pre-existing tree issues exposed by new DTB build
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no C/H changes)
check-patch-compliance	❌	`QCLINUX:` prefix not accepted (known limitation)
tag-check	✅	`QCLINUX:` prefix present (required for non-qcom-next branches)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #610 — QCLINUX: arm64: dts: qcom: add purwa CAMX EL2 overlay
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/26284419200
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ✅ No style issues

dt-binding-check ⏭️ Skipped (no binding changes)

dtb-check ❌ Pre-existing tree issues exposed by new DTB build

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

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

check-patch-compliance ❌ QCLINUX: prefix not accepted (known limitation)

tag-check ✅ QCLINUX: prefix present (required for non-qcom-next branches)

❌ check-patch-compliance

Root cause: The commit uses the QCLINUX: prefix, which is not in the checker's allowed list.

Failure details:
Checking commit: QCLINUX: arm64: dts: qcom: add purwa CAMX EL2 overlay Add a device tree overlay to enable EL2 boot support for the Purwa platform with CAMX configuration.
Commit summary does not start with a required prefix
Analysis:
The check-patch-compliance checker only accepts upstream-linkable prefixes: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:. The QCLINUX: prefix is a vendor-internal tag used for changes with no upstream equivalent. This is a known limitation of the checker — vendor-only commits will always fail this check.

Since this is a vendor-specific device tree overlay for the Purwa platform with CAMX EL2 configuration, and there is no upstream equivalent, the QCLINUX: prefix is correct and appropriate.

Fix: None required. This is expected behavior for vendor-only commits.

Note: The tag-check (Step 2.7 of the skill) confirms that the commit does have a valid subject prefix (QCLINUX:) as required for the target branch qcom-6.18.y (which is not qcom-next or qcom-next-staging).

❌ dtb-check

Root cause: Pre-existing tree issues in the base purwa-iot-evk.dtb and camera subsystem nodes are exposed when building the new composite DTB purwa-camx-el2.dtb.

Failure details:
Log Summary: Test failed

purwa-camx-el2.dtb: soc@0 (simple-bus): qcom,cam-req-mgr: 'ranges' is a required property
purwa-camx-el2.dtb: soc@0 (simple-bus): qcom,cam-jpeg: 'ranges' is a required property
purwa-camx-el2.dtb: soc@0 (simple-bus): qcom,camera-main: 'ranges' is a required property
purwa-camx-el2.dtb: soc@0 (simple-bus): qcom,cam-isp: 'ranges' is a required property
purwa-camx-el2.dtb: soc@0 (simple-bus): qcom,cam-smmu: 'ranges' is a required property
purwa-camx-el2.dtb: soc@0 (simple-bus): qcom,cam-icp: 'ranges' is a required property
purwa-camx-el2.dtb: soc@0 (simple-bus): qcom,cam-cdm-intf: 'ranges' is a required property
purwa-camx-el2.dtb: soc@0 (simple-bus): qcom,cam-sync: 'ranges' is a required property

purwa-camx-el2.dtb: /soc@0/qcom,camera-main: failed to match any schema with compatible: ['qcom,camera_x1e80100']
purwa-camx-el2.dtb: /soc@0/qcom,cam-sync: failed to match any schema with compatible: ['qcom,cam-sync']

purwa-iot-evk.dtb: soc@0 (simple-bus): etm@13021000..etm@13821000: 'anyOf' conditional failed (×8 ETM nodes)
purwa-iot-evk.dtb: video-codec@aa00000 (qcom,x1p42100-iris): 'iommus' is a required property
purwa-iot-evk.dtb: ctcu@10001000 (qcom,hamoa-ctcu): failed to match any schema
purwa-iot-evk.dtb: funnel@13401000..replicator@13990000: compatible does not match schema (×10 CoreSight nodes)
Analysis:
These errors fall into two categories:

Camera subsystem nodes missing 'ranges' property — These nodes (qcom,cam-req-mgr, qcom,cam-jpeg, qcom,camera-main, etc.) are defined in the base purwa-iot-evk.dtsi or included camera DTSI files. The simple-bus binding requires child nodes with #address-cells/#size-cells to declare a ranges property. This is a pre-existing tree issue, not introduced by this PR.

CoreSight, video-codec, and CTCU binding errors — These are all from the base purwa-iot-evk.dtb and are pre-existing tree issues. The ETM nodes, video codec, CTCU, and CoreSight funnel/replicator/TMC nodes have binding validation failures that existed before this PR.

The new overlay purwa-camx-el2.dtso itself only adds 18 lines:
/ {
	fragment@0 {
		target-path = "/soc@0/qcom,cam-icp";
		__overlay__ {
			camera-firmware {
				...
			};
		};
	};
};
This overlay does not introduce any new binding violations. The failures are exposed because building purwa-camx-el2.dtb (which combines purwa-iot-evk-el2.dtb + purwa-evk-camx.dtbo + purwa-camx-el2.dtbo) triggers validation of the entire merged tree, including pre-existing issues.

Fix:
The camera subsystem 'ranges' property issue should be fixed in the base camera DTSI files (likely purwa-camera.dtsi or similar). Add ranges; (empty ranges for 1:1 address translation) to each camera subsystem node that has #address-cells and #size-cells:
qcom,cam-req-mgr {
	compatible = "qcom,cam-req-mgr";
	#address-cells = <1>;
	#size-cells = <0>;
	ranges;  // ← Add this
	...
};
However, this fix is outside the scope of this PR, as the issue is in the base tree, not in the new overlay.

Reproduce locally:
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/purwa-camx-el2.dtb
Verdict

2 blockers, but only 1 is actionable:

✅ check-patch-compliance failure — Expected for vendor-only commits with QCLINUX: prefix. No action needed.

⚠️ dtb-check failures — Pre-existing tree issues, not introduced by this PR. The new overlay itself is clean. Fixing the camera subsystem 'ranges' properties should be done in a separate PR targeting the base camera DTSI files.

Recommendation: The PR can be merged as-is if the team accepts that the dtb-check failures are pre-existing tree issues. Alternatively, fix the camera subsystem 'ranges' properties in the base tree first, then rebase this PR.

shashim-quic

CRs-Fixed: 4546912

remove it from commit log. Adding it to PR description suffice.

qlijarvis · 2026-05-25T10:51:37Z

PR #610 — validate-patch

PR: #610

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: #610 — QCLINUX: arm64: dts: qcom: add purwa CAMX EL2 overlay
Upstream commit: N/A (vendor-only commit)
Verdict: ✅ PASS

Commit Message

Check Status Note

Subject matches upstream N/A QCLINUX: vendor-only commit

Body preserves rationale ✅ Brief but adequate for device tree overlay

Fixes tag present/correct N/A New feature, no bug fix

Authorship preserved ✅ Original author in From: field

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

Diff

File Status Notes

arch/arm64/boot/dts/qcom/Makefile ✅ Adds purwa-camx-el2 dtb build target

arch/arm64/boot/dts/qcom/purwa-camx-el2.dtso ✅ New overlay for EL2 boot with CAMX; proper SPDX header

Verdict

Merge as-is. This is a vendor-only device tree overlay for Purwa platform EL2 boot support with CAMX configuration. The QCLINUX: prefix correctly indicates no upstream equivalent exists. The commit adds a new dtso file with proper licensing and a corresponding Makefile entry following existing patterns in the tree.

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-25T10:51:38Z

PR #610 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	Missing commit description
dt-binding-check	⏭️	No binding changes
dtb-check	❌	Pre-existing tree issue: `etm@13021000` missing `reg` or `ranges`
sparse-check	⏭️	No C/H changes
check-uapi-headers	⏭️	No UAPI changes
check-patch-compliance	❌	`QCLINUX:` prefix not accepted (known limitation)
tag-check	✅	Subject has valid prefix (`QCLINUX:`)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #610 - QCLINUX: arm64: dts: qcom: add purwa CAMX EL2 overlay
Target branch: qcom-6.18.y
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/26384779115

Checker Result Summary

checkpatch ❌ Missing commit description

dt-binding-check ⏭️ No binding changes

dtb-check ❌ Pre-existing tree issue: etm@13021000 missing reg or ranges

sparse-check ⏭️ No C/H changes

check-uapi-headers ⏭️ No UAPI changes

check-patch-compliance ❌ QCLINUX: prefix not accepted (known limitation)

tag-check ✅ Subject has valid prefix (QCLINUX:)

❌ checkpatch

Root cause: Commit message has no body — only the subject line exists.

Failure details:
WARNING: Missing commit description - Add an appropriate one
89e494f947e92d36536026ccbdb09a3b894a76c0 total: 0 errors, 1 warnings, 0 checks, 28 lines checked
Fix: Add a commit body describing what the patch does and why:
git commit --amend
# Add a body like:
# 
# This overlay enables EL2 boot support for the Purwa platform with CAMX
# configuration by setting the appropriate IOMMU mapping for the camera
# firmware node.
Reproduce locally:
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git f8d09d824665..89e494f947e9
❌ dtb-check

Root cause: Pre-existing tree issue in purwa-iot-evk.dtb — the etm@13021000 node violates simple-bus schema requirements.

Failure details:
/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/purwa-iot-evk.dtb: 
  soc@0 (simple-bus): etm@13021000: 'anyOf' conditional failed, one must be fixed:
    'reg' is a required property
    'ranges' is a required property
    from schema $id: http://devicetree.org/schemas/simple-bus.yaml#
Analysis: This error is triggered by building purwa-iot-evk.dtb (the base DTB for the overlay), not by the overlay itself (purwa-camx-el2.dtbo). The etm@13021000 node exists in the base purwa.dtsi or purwa-iot-evk.dts and is missing either a reg property or a ranges property to satisfy the simple-bus schema.

This is a pre-existing tree issue — the PR only adds a new overlay that references the existing base DTB. The error was already present before this PR.

Fix (if required): Add the missing reg property to the etm@13021000 node in the base DTS file:
etm@13021000 {
    compatible = "...";
    reg = <0x0 0x13021000 0x0 0x1000>;
    ...
};
However, this fix is outside the scope of PR #610 — the PR author should not be required to fix pre-existing tree issues to merge a new overlay.

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

Root cause: The commit uses the QCLINUX: prefix, which is not in the checker's allowed list (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:).

Failure details:
Checking commit: QCLINUX: arm64: dts: qcom: add purwa CAMX EL2 overlay Add a device tree overlay...
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 commits with QCLINUX:, PENDING:, or WORKAROUND: prefixes will always fail this check.

This is not a patch defect — QCLINUX: is the correct prefix for vendor-only changes with no upstream equivalent.

No fix required — the checker failure is expected for vendor-only commits.

✅ tag-check

Status: PASS

Analysis: The target branch is qcom-6.18.y, which is not qcom-next or qcom-next-staging, so the subject-prefix check is mandatory.

The commit subject starts with QCLINUX:, which is a valid prefix for vendor-only changes. ✅

Verdict

2 blockers to fix before merge:

checkpatch: Add a commit body describing the change.

dtb-check: Pre-existing tree issue in purwa-iot-evk.dtb (etm@13021000 missing reg/ranges). This is not introduced by the PR — recommend either:

Fix the base DTS in a separate commit/PR, or

Merge as-is if the team accepts pre-existing dtb-check warnings.

Non-blockers (expected failures):

check-patch-compliance: QCLINUX: prefix is correct for vendor-only commits; checker limitation is known.

Add a device tree overlay to enable EL2 boot support for the Purwa platform with CAMX configuration. Signed-off-by: Ignatius Michael Jihan <mignatiu@qti.qualcomm.com>

qcomlnxci · 2026-05-26T06:55:47Z

Test jobs on 89e494f

qcomlnxci · 2026-05-26T06:55:49Z

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	◻️

qlijarvis · 2026-05-26T07:21:12Z

PR #610 — validate-patch

PR: #610

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: #610 — QCLINUX: arm64: dts: qcom: add purwa CAMX EL2 overlay
Upstream commit: N/A (vendor-only)
Verdict: ✅ PASS (vendor-only commit)

Commit Message

Check Status Note

Subject matches upstream N/A QCLINUX: prefix indicates vendor-only commit

Body preserves rationale ✅ Clear description of EL2 boot support for Purwa/CAMX

Fixes tag present/correct N/A Not a fix; new feature addition

Authorship preserved ✅ Signed-off-by present and consistent with From:

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

Diff

File Status Notes

arch/arm64/boot/dts/qcom/Makefile ✅ Adds purwa-camx-el2 dtb build target

arch/arm64/boot/dts/qcom/purwa-camx-el2.dtso ✅ New overlay for CAMX EL2 IOMMU configuration

Verdict

This is a vendor-only commit (QCLINUX: prefix) adding device tree overlay support for Purwa platform EL2 boot with CAMX. The commit message is clear, authorship is correct, and the changes are self-contained. No upstream validation is applicable or required for QCLINUX: commits.

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-26T07:21:14Z

PR #610 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	Pre-existing tree issues only
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no C/H changes)
check-patch-compliance	❌	Known limitation: `QCLINUX:` prefix not accepted
tag-check	✅	Valid `QCLINUX:` prefix present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #610 - QCLINUX: arm64: dts: qcom: add purwa CAMX EL2 overlay
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/26437146551
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ✅ No style issues

dt-binding-check ⏭️ Skipped (no binding changes)

dtb-check ❌ Pre-existing tree issues only

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

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

check-patch-compliance ❌ Known limitation: QCLINUX: prefix not accepted

tag-check ✅ Valid QCLINUX: prefix present

❌ check-patch-compliance

Root cause: The QCLINUX: prefix is not in the checker's allowed list (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:).

Failure details:
Checking commit: QCLINUX: arm64: dts: qcom: add purwa CAMX EL2 overlay
Commit summary does not start with a required prefix
Analysis: This is a known checker limitation for vendor-only commits. The check-patch-compliance checker only accepts upstream-linkable prefixes and will always fail for QCLINUX: commits. However, QCLINUX: is a valid prefix for vendor-only changes with no upstream equivalent.

Fix: None required. This is expected behavior for vendor-only commits. The QCLINUX: prefix is appropriate for this vendor-specific device tree overlay.

❌ dtb-check

Root cause: All reported errors are pre-existing tree issues in purwa-iot-evk.dtb, not introduced by this PR.

Failure details:
The dtb-check log shows multiple schema validation errors:

8× etm@* nodes: 'reg' is a required property / 'ranges' is a required property

video-codec@aa00000: 'iommus' is a required property, unevaluated iommu-map property, iommu-map array too short

ctcu@10001000: compatible string mismatch (qcom,hamoa-ctcu not in binding)

Multiple funnel@*, tmc@*, replicator@* nodes: compatible string does not match schema

Analysis: These errors appear in purwa-iot-evk.dtb, which is the base DTB that this PR's overlay depends on. The PR only adds a new overlay file (purwa-camx-el2.dtso) and Makefile entries — it does not modify the base purwa-iot-evk.dts or any of the problematic nodes.

The dtb-check failure is triggered because building the new composite DTB (purwa-camx-el2.dtb = purwa-iot-evk-el2.dtb + purwa-evk-camx.dtbo + purwa-camx-el2.dtbo) exposes pre-existing validation errors in the base tree. These same errors would appear if you built purwa-iot-evk.dtb at the base commit.

Fix: None required for this PR. The errors are pre-existing tree issues that should be fixed separately in the base purwa.dtsi / purwa-iot-evk.dts files:

ETM nodes need reg properties added

Video codec node needs iommus property and iommu-map format fixed

CTCU binding needs qcom,hamoa-ctcu compatible string added

CoreSight component bindings need to accept arm,coresight-cpu-* compatible strings

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

Ready to merge. Both failures are expected and do not block this PR:

check-patch-compliance: Known limitation — QCLINUX: is the correct prefix for vendor-only commits but is not accepted by the checker.

dtb-check: All errors are pre-existing tree issues in the base purwa-iot-evk.dtb, not introduced by this PR's overlay.

The PR correctly adds a new device tree overlay with proper structure and no new validation issues.

qcomlnxci · 2026-05-26T08:02:03Z

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	❌ 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	⚠️ 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	❌ Fail	✅ 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	◻️

qcomlnxci · 2026-05-26T08:02:04Z

Test jobs on 082c437

michael-jihan-qcom requested review from a team, quic-tingweiz, rrnayak and sgaud-quic May 22, 2026 11:02

michael-jihan-qcom changed the title ~~QCLINUX: arm64: dts: qcom: add hamoa CAMX EL2 overlay~~ QCLINUX: arm64: dts: qcom: add Purwa CAMX EL2 overlay May 22, 2026

michael-jihan-qcom force-pushed the purwa_kvm_6_18_y_may22 branch from e1ad43b to 878c93e Compare May 22, 2026 11:05

shashim-quic requested changes May 24, 2026

View reviewed changes

michael-jihan-qcom force-pushed the purwa_kvm_6_18_y_may22 branch from 878c93e to 89e494f Compare May 25, 2026 05:21

qcomlnxci requested a review from a team May 25, 2026 05:24

michael-jihan-qcom requested a review from shashim-quic May 26, 2026 05:39

shashim-quic approved these changes May 26, 2026

View reviewed changes

QCLINUX: arm64: dts: qcom: add purwa CAMX EL2 overlay

082c437

Add a device tree overlay to enable EL2 boot support for the Purwa platform with CAMX configuration. Signed-off-by: Ignatius Michael Jihan <mignatiu@qti.qualcomm.com>

michael-jihan-qcom force-pushed the purwa_kvm_6_18_y_may22 branch from 89e494f to 082c437 Compare May 26, 2026 06:51

qcomlnxci requested a review from a team May 26, 2026 06:53

sgaud-quic merged commit daed243 into qualcomm-linux:qcom-6.18.y May 26, 2026
6 of 8 checks passed

xueqnie mentioned this pull request May 28, 2026

Enable EL2 DTBO support for Hamoa and Purwa platforms qualcomm-linux/meta-qcom#2311

Draft

Conversation

michael-jihan-qcom commented May 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qswat-orbit-external Bot commented May 22, 2026

Uh oh!

qswat-orbit-external Bot commented May 22, 2026

Uh oh!

quic-vikramsa commented May 22, 2026

Uh oh!

qlijarvis commented May 22, 2026

PR #610 — validate-patch

Final Summary

🔍 Patch Validation

Reason

Commit Message

Diff

Observations

Verdict

Final Summary

Uh oh!

qlijarvis commented May 22, 2026

PR #610 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ check-patch-compliance

❌ dtb-check

Verdict

Uh oh!

shashim-quic left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

qlijarvis commented May 25, 2026

PR #610 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Verdict

Final Summary

Uh oh!

qlijarvis commented May 25, 2026

PR #610 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ checkpatch

❌ dtb-check

❌ check-patch-compliance

✅ tag-check

Verdict

Uh oh!

qcomlnxci commented May 26, 2026

Test jobs on 89e494f

Uh oh!

qcomlnxci commented May 26, 2026

Test Matrix

Uh oh!

qlijarvis commented May 26, 2026

PR #610 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Verdict

Final Summary

Uh oh!

qlijarvis commented May 26, 2026

PR #610 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ check-patch-compliance

❌ dtb-check

Verdict

Uh oh!

qcomlnxci commented May 26, 2026

Test Matrix

Uh oh!

qcomlnxci commented May 26, 2026

Test jobs on 082c437

Uh oh!

Uh oh!

Reviewers

michael-jihan-qcom commented May 22, 2026 •

edited

Loading

shashim-quic left a comment •

edited

Loading