arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577 by sushilsingh045 · Pull Request #1040 · qualcomm-linux/kernel

sushilsingh045 · 2026-09-04T06:22:20Z

Add camera sensor device tree support for the Draco-based Lemans EVK in QLI 2.0.
This change adds camera sensor nodes for the IMX858, OV13B10, and IMX577 sensors. These DTSI updates provide the required sensor entries and platform configuration needed for camera bring-up on the Draco-based Lemans EVK.
The change is added as part of QLI 2.0 camera sensor enablement.

CRs-Fixed: 4704394

qswat-orbit-external · 2026-09-04T06:22:28Z

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

qswat-orbit-external · 2026-09-09T04:20:31Z

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

qlijarvis · 2026-09-09T04:53:40Z

PR #1040 — validate-patch

PR: #1040

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/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1040 - QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
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 ✅ Clear description of camera sensor additions

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

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

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

Diff

File Status Notes

arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi ✅ New file: 810 lines of camera sensor device tree nodes

Verdict

Merge as-is. This is a vendor-only commit with the correct QCLINUX: prefix, proper authorship, and clear commit message describing the addition of camera sensor device tree nodes for Lemans EVK.

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/topics: Not checked — QCLINUX: vendor-only commit

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

Commit Subject qcom-next topics Final

1/1 [PATCH] QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing

Final Status

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

qlijarvis · 2026-09-09T04:53:42Z

PR #1040 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	42 errors, 27 warnings, 1 check
dt-binding-check	⏭️	No binding changes
dtb-check	⏭️	No DTBs built (DTS-only change)
sparse-check	⏭️	No C/H files changed
check-uapi-headers	⏭️	No C/H files changed
check-patch-compliance	❌	`QCLINUX:` prefix not accepted
tag-check	⚠️	`QCLINUX:` is valid for qcom-6.18.y

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1040 - QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/34310678636
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ❌ 42 errors, 27 warnings, 1 check

dt-binding-check ⏭️ No binding changes

dtb-check ⏭️ No DTBs built (DTS-only change)

sparse-check ⏭️ No C/H files changed

check-uapi-headers ⏭️ No C/H files changed

check-patch-compliance ❌ QCLINUX: prefix not accepted

tag-check ⚠️ QCLINUX: is valid for qcom-6.18.y

❌ checkpatch

Root cause: The new DTS file contains 42 indentation errors (spaces instead of tabs), 6 trailing whitespace errors, multiple undocumented DT compatible strings, 1 block comment alignment issue, and 1 commit message line length warning.

Failure details:
235fba5aeabd total: 42 errors, 27 warnings, 1 checks, 810 lines checked

ERROR: code indent should use tabs where possible
#74: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:54:
+                     "CAMIF_RESET0",

ERROR: code indent should use tabs where possible
#75: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:55:
+                     "CAM_CUSTOM0";

ERROR: trailing whitespace
#190: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:170:
+<trailing whitespace>

WARNING: Block comments should align the * on each line
#24: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:4:
+ * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.

WARNING: DT compatible string "qcom,cam-res-mgr" appears un-documented
WARNING: DT compatible string "qcom,actuator" appears un-documented
WARNING: DT compatible string "qcom,eeprom" appears un-documented
WARNING: DT compatible string "qcom,cam-sensor" appears un-documented

WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
Fix:
Indentation errors (42 errors): Replace leading spaces with tabs in gpio-req-tbl-label arrays:
# Lines 54-55, 94-95, 128-129, 168-169, 204, 253-254, 293-294, 327-328, 367-368, etc.
# Replace spaces with tabs for continuation lines
sed -i 's/^                     /\t\t\t\t     /' arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi
Trailing whitespace (6 errors): Remove trailing whitespace:
sed -i 's/[[:space:]]*$//' arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi
Block comment alignment: Fix the copyright block comment:
/*
- * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
+ * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
*/
Undocumented DT strings (27 warnings): These are vendor-specific Qualcomm camera subsystem compatible strings (qcom,cam-res-mgr, qcom,actuator, qcom,eeprom, qcom,cam-sensor). These are not blockers — they are used throughout the Qualcomm tree and do not have upstream bindings. Document them if submitting upstream, but acceptable for vendor tree.
Commit message line length: The commit body line is slightly over 75 chars. Wrap it:
Add camera sensor device tree nodes for the Draco-based Lemans EVK to
enable imx858, ov13b10 and imx577 sensors.
Reproduce locally:
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES \
  --git b5d890825bc2..235fba5aeabd
❌ check-patch-compliance

Root cause: The commit subject 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: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
Commit summary does not start with a required prefix
Analysis: This is a known limitation of the check-patch-compliance checker. The QCLINUX: prefix is a valid vendor-internal prefix used for Qualcomm-specific changes that have no upstream equivalent. The checker only accepts upstream-linkable prefixes (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:).

Fix: This is not a blocker for vendor branches like qcom-6.18.y. The QCLINUX: prefix is correct for this vendor-only camera sensor addition. The checker will always fail for QCLINUX: commits — this is expected behavior.

Alternative (if upstream submission is planned): If this change will be posted upstream, change the prefix to FROMLIST: and add a Link: trailer pointing to the lore.kernel.org URL once posted.

⚠️ tag-check (manual check for qcom-6.18.y)

Analysis: The target branch is qcom-6.18.y, which is not qcom-next or qcom-next-staging. Therefore, every commit must start with a valid prefix tag.

Commit subject: QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577

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

Note: While check-patch-compliance rejects QCLINUX:, the tag-check accepts it as a valid prefix for branches other than qcom-next/qcom-next-staging. This is a known discrepancy between the two checks.

Verdict

Fix 3 blockers before merge:

Indentation errors (42): Replace spaces with tabs in gpio-req-tbl-label continuation lines

Trailing whitespace (6): Remove trailing whitespace from 6 lines

Block comment alignment (1): Align the * in the copyright block comment

Optional improvements:

Wrap the commit body line to stay under 75 chars

The 27 undocumented DT string warnings are not blockers — these are vendor-specific camera subsystem compatible strings used throughout the Qualcomm tree

Not blockers:

check-patch-compliance failure on QCLINUX: prefix is expected for vendor-only commits

QCLINUX: is a valid prefix for qcom-6.18.y branch

qswat-orbit-external · 2026-09-17T19:25:15Z

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

qlijarvis · 2026-09-17T19:56:40Z

PR #1040 — validate-patch

PR: #1040

Verdict	Issues	Detailed Report
⚠️	1	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/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1040 - QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
Upstream commit: N/A (vendor-only commit)
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note

Subject matches upstream N/A Vendor-only commit (QCLINUX: prefix)

Body preserves rationale ⚠️ Leading space before commit body; should start flush left

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

Authorship preserved ✅ Correct author for vendor commit

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

Diff

File Status Notes

arch/arm64/boot/dts/qcom/Makefile ✅ Adds Draco EVK camera build targets

arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi ✅ New camera sensor definitions (810 lines)

arch/arm64/boot/dts/qcom/lemans-draco-evk-camx.dtso ✅ New camera overlay (21 lines)

Issues

Commit message formatting: The commit body has a leading space (line 7 of pr.patch). According to kernel commit message style, the body should start flush left after the blank line following the subject. This is a minor formatting issue but should be corrected for consistency.

Verdict

Merge with minor fix recommended. The commit is a valid vendor-only addition (QCLINUX: prefix) adding camera sensor device tree support for Lemans Draco EVK. The only issue is a cosmetic formatting problem with the commit body indentation. The diff content is appropriate for a vendor device tree addition.

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/topics: No — commit is missing from both qcom-next and topics (per integration_presence_report.md). This is expected for new vendor contributions that haven't been merged yet.

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

Commit Subject qcom-next topics Final

1/1 [PATCH] QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing

Final Status

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

qlijarvis · 2026-09-17T19:56:41Z

PR #1040 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	42 errors, 27 warnings, 1 check
dt-binding-check	⏭️	No binding changes
dtb-check	❌	DTS syntax error + pre-existing tree issues
sparse-check	⏭️	No C/H changes
check-uapi-headers	⏭️	No UAPI changes
check-patch-compliance	❌	`QCLINUX:` prefix not accepted
tag-check	⚠️	`QCLINUX:` is valid for qcom-6.18.y (see note)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1040 - QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/35264885593
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ❌ 42 errors, 27 warnings, 1 check

dt-binding-check ⏭️ No binding changes

dtb-check ❌ DTS syntax error + pre-existing tree issues

sparse-check ⏭️ No C/H changes

check-uapi-headers ⏭️ No UAPI changes

check-patch-compliance ❌ QCLINUX: prefix not accepted

tag-check ⚠️ QCLINUX: is valid for qcom-6.18.y (see note)

❌ dtb-check — DTS Syntax Error (BLOCKER)

Root cause: Invalid phandle reference <&16bitIOexpander ...> — DTS node names cannot start with a digit.

Failure details:
Error: ../arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:48.5-6 syntax error
The file references <&16bitIOexpander 1 0> at multiple locations (lines 48, 88, 122, 162, 247, 287, 321, 361, 447, 487, etc.). DTS syntax requires node names and labels to start with a letter or underscore, not a digit.

Fix: Rename the phandle reference to start with a letter or underscore:
# Option 1: Prefix with underscore
sed -i 's/<&16bitIOexpander/<\&_16bitIOexpander/g' arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi

# Option 2: Use a descriptive name
sed -i 's/<&16bitIOexpander/<\&ioexpander_16bit/g' arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi
Then update the corresponding node label definition in the parent DTSI/DTS file where 16bitIOexpander is defined.

Reproduce locally:
make -j$(nproc) O=out defconfig
make -j$(nproc) O=out arch/arm64/boot/dts/qcom/lemans-draco-evk-camx.dtbo
❌ checkpatch — Code Style Violations

Root cause: 42 errors (mostly indentation with spaces instead of tabs), 27 warnings (undocumented DT compatible strings, long commit message line), 1 check (missing blank line).

Failure details:
ERROR: code indent should use tabs where possible (42 instances)
WARNING: DT compatible string "qcom,cam-res-mgr" appears un-documented
WARNING: DT compatible string "qcom,actuator" appears un-documented
WARNING: DT compatible string "qcom,eeprom" appears un-documented
WARNING: DT compatible string "qcom,cam-sensor" appears un-documented
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
WARNING: Block comments should align the * on each line
CHECK: Please use a blank line after function/struct/union/enum declarations
ERROR: trailing whitespace (at least 1 instance)
Fix:

Indentation errors — Replace spaces with tabs:
# Fix all space indentation in the DTSI file
sed -i 's/^                     /\t\t\t\t     /g' arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi
# Or use an editor to convert leading spaces to tabs
Trailing whitespace — Remove:
sed -i 's/[[:space:]]*$//' arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi
Undocumented DT compatible strings — These are vendor-specific camera driver compatibles. Either:

Add DT binding YAML files for qcom,cam-res-mgr, qcom,actuator, qcom,eeprom, qcom,cam-sensor in Documentation/devicetree/bindings/media/qcom/, OR

Accept these warnings as vendor-specific extensions (common for camera subsystem)

Commit message long line — Wrap the commit body at 75 characters:
git commit --amend
# Edit the commit message to wrap the description line
Block comment alignment — Fix the /* comment style to align * on each line.

Reproduce locally:
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git HEAD~1..HEAD
❌ check-patch-compliance — Prefix Not Accepted

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

Failure details:
Checking commit: QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
Commit summary does not start with a required prefix
Note: This is a known limitation of the check-patch-compliance checker. The QCLINUX: prefix is a valid vendor-internal prefix used in the Qualcomm Linux kernel tree for vendor-only changes with no upstream equivalent. The checker enforces only upstream-linkable prefixes (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:), so vendor-only commits will always fail this check.

Fix: None required if this is genuinely a vendor-only change. If the camera sensor nodes are based on an upstream patch or posted to a mailing list, change the prefix to FROMLIST: and add a Link: trailer pointing to the lore.kernel.org URL.

⚠️ tag-check — Subject Prefix (Manual Check)

Status: ✅ PASS (with caveat)

The commit subject starts with QCLINUX:, which is a valid prefix for vendor-only changes. The target branch is qcom-6.18.y (not qcom-next or qcom-next-staging), so a subject prefix is required.

Valid prefixes for qcom-6.18.y:

FROMLIST: — Posted to mailing list

FROMGIT: — Taken from a maintainer git tree

UPSTREAM: — Merged into Linus's mainline

BACKPORT: — Backported with modifications

QCLINUX: — Vendor-only change ✅ (used here)

PENDING: — Work-in-progress

WORKAROUND: — Temporary fix

The QCLINUX: prefix is appropriate for vendor-specific camera sensor device tree additions that have no upstream equivalent.

ℹ️ dtb-check — Pre-Existing Tree Issues (Not Caused by PR)

The following dtb-check errors appear in the log but are pre-existing tree issues in lemans-evk.dtb, not introduced by this PR:
lemans-evk.dtb: pinctrl@f000000 (qcom,sa8775p-tlmm): gp_mn_active-state: 'oneOf' conditional failed
lemans-evk.dtb: ethernet@23040000 (qcom,sa8775p-ethqos): Unevaluated properties ('interconnect-names', 'interconnects')
lemans-evk.dtb: video-codec@aa00000 (qcom,sa8775p-iris): Unevaluated properties ('iommu-map')
These errors are in the base lemans-evk.dtb file and are not related to the new lemans-draco-evk-camera-sensor.dtsi additions. They should have been filtered by the baseline subtraction but appear to have leaked through. No action required for this PR.

Verdict

❌ 1 blocker must be fixed before merge:

DTS syntax error — Rename 16bitIOexpander phandle references to start with a letter or underscore (e.g., _16bitIOexpander or ioexpander_16bit)

⚠️ Recommended fixes (non-blocking but should be addressed):

checkpatch errors — Fix indentation (spaces → tabs) and remove trailing whitespace

checkpatch warnings — Wrap commit message at 75 chars; optionally add DT bindings for camera compatibles

ℹ️ Known checker limitations (no action needed):

check-patch-compliance failure is expected for QCLINUX: prefix (vendor-only commits)

Pre-existing dtb-check errors in lemans-evk.dtb are not caused by this PR

qswat-orbit-external · 2026-09-29T14:33:19Z

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

qswat-orbit-external · 2026-09-29T14:36:41Z

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

qlijarvis · 2026-10-08T23:38:25Z

PR #1040 — validate-patch

PR: #1040

Verdict	Issues	Detailed Report
❌	1	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/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1040 - QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
Upstream commit: N/A (vendor-only commit)
Verdict: ❌ FAIL

Commit Message

Check Status Note

Subject matches upstream N/A Vendor-only commit (QCLINUX: prefix)

Body preserves rationale ✅ Brief description present

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

Authorship preserved ✅ Author: Sushil Pratap Singh

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

Diff

File Status Notes

arch/arm64/boot/dts/qcom/Makefile ✅ Adds build rules for lemans-draco-evk camera overlays

arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi ✅ New file: camera sensor definitions (811 lines)

arch/arm64/boot/dts/qcom/lemans-draco-evk-camx.dtso ✅ New file: camera overlay (138 lines)

Issues

Missing from integration tree: This commit is not present in qcom-next or any kernel topic branch. Vendor-only commits (QCLINUX:) should typically be present in the integration tree before PR submission.

Verdict

Reject — The commit is missing from both qcom-next and kernel topic branches. Even vendor-only commits should be integrated into the appropriate topic branch before being submitted via PR to ensure proper tracking and integration testing.

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/topics: Fail — 1/1 commit(s) are missing from both qcom-next and topics (per integration_presence_report.md)

Deterministic Integration Presence

Integration Presence Report

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

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

Commit Subject qcom-next topics Final

1/1 [PATCH] QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing

Final Status

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

qlijarvis · 2026-10-08T23:38:27Z

PR #1040 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	40 errors, 27 warnings (indentation, whitespace, undocumented DT strings)
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	Build failure: missing base DTB dependency
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no C/H changes)
check-patch-compliance	❌	`QCLINUX:` prefix not in allowed list
tag-check	✅	Subject has valid prefix (`QCLINUX:`)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1040 - QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/36589645932
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ❌ 40 errors, 27 warnings (indentation, whitespace, undocumented DT strings)

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

dtb-check ❌ Build failure: missing base DTB dependency

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

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

check-patch-compliance ❌ QCLINUX: prefix not in allowed list

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

❌ dtb-check — Build Failure (BLOCKER)

Root cause: Makefile references non-existent base DTB files lemans-draco-evk.dtb and lemans-draco-evk-el2.dtb.

Failure details:
make[4]: *** No rule to make target 'arch/arm64/boot/dts/qcom/lemans-draco-evk.dtb', 
needed by 'arch/arm64/boot/dts/qcom/lemans-draco-evk-camx.dtb'.  Stop.
The Makefile at arch/arm64/boot/dts/qcom/Makefile:481 defines:
lemans-draco-evk-camx-dtbs := lemans-draco-evk.dtb lemans-draco-evk-camx.dtbo
lemans-draco-evk-camx-el2-dtbs := lemans-draco-evk-el2.dtb lemans-draco-evk-camx.dtbo lemans-camx-el2.dtbo
But the PR does not add lemans-draco-evk.dts or lemans-draco-evk-el2.dts — only the overlay files.

Fix:

Option 1 (if base DTBs exist in the tree already):

Verify lemans-draco-evk.dts and lemans-draco-evk-el2.dts exist in arch/arm64/boot/dts/qcom/

If they exist, ensure they are listed in the Makefile with dtb-$(CONFIG_ARCH_QCOM) += lemans-draco-evk.dtb

Option 2 (if base DTBs don't exist):

Add lemans-draco-evk.dts and lemans-draco-evk-el2.dts to the PR

Or remove the Makefile entries for lemans-draco-evk-camx.dtb and lemans-draco-evk-camx-el2.dtb if they're not ready yet

Reproduce locally:
make -j$(nproc) O=out defconfig
make -j$(nproc) O=out dtbs
❌ checkpatch — Coding Style Violations

Root cause: Mixed spaces/tabs indentation and undocumented DT compatible strings.

Failure details:
01da58b8a829 total: 40 errors, 27 warnings, 0 checks, 964 lines checked
Key issues:

40× ERROR: code indent should use tabs where possible

Lines like #696, #697, #736, #737, etc. in lemans-draco-evk-camera-sensor.dtsi

Mixed spaces and tabs in gpio-names arrays

1× ERROR: trailing whitespace

Line #819 in lemans-draco-evk-camera-sensor.dtsi:776

27× WARNING: DT compatible string appears un-documented

qcom,cam-res-mgr

qcom,actuator

qcom,eeprom

qcom,cam-sensor

WARNING: Prefer a maximum 75 chars per line

Commit message body line too long

Fix:

Indentation errors:
# Fix tabs/spaces in the DTSI file
sed -i 's/^                     /\t\t                     /' \
  arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi
Trailing whitespace:
sed -i 's/[[:space:]]*$//' arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi
Undocumented DT strings:

These are Qualcomm vendor-specific camera driver compatible strings

Either add bindings to Documentation/devicetree/bindings/media/qcom,*.yaml

Or accept the warnings (vendor-only drivers often lack upstream bindings)

Commit message:
git commit --amend  # Wrap body lines at 75 chars
Reproduce locally:
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES \
  --git 1777185905428365be355eeeabe42d8fe9fd4c7a..01da58b8a829f7214e1e064c35c3f96d36fcfc1d
❌ check-patch-compliance — Prefix Not Allowed

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

Failure details:
Checking commit: QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
Commit summary does not start with a required prefix
Analysis:

This is a known limitation of the check-patch-compliance checker. The commit uses QCLINUX:, which is a valid vendor-internal prefix for Qualcomm-only changes, but the checker only accepts upstream-linkable prefixes.

Options:

If this patch was posted upstream: Change prefix to FROMLIST: and add Link: <lore-url> to the commit body

If this is vendor-only: Accept the checker failure — QCLINUX: is the correct prefix for vendor-only DTS additions

If targeting a non-qcom-next branch: The tag-check (below) confirms the prefix is valid for the target branch

No action required — this is expected for vendor-only commits.

✅ tag-check — Subject Prefix Valid

Analysis:

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

Commit subject: QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577

Prefix QCLINUX: is in the allowed list:

✅ FROMLIST: / FROMGIT: / UPSTREAM: / BACKPORT: / QCLINUX: / PENDING: / WORKAROUND:

Verdict: ✅ PASS

Verdict

❌ BLOCKER — Cannot merge until fixed

Critical issues (must fix):

dtb-check build failure — Missing base DTB files lemans-draco-evk.dtb and lemans-draco-evk-el2.dtb referenced in Makefile

checkpatch: 40 indentation errors — Mixed spaces/tabs in gpio-names arrays

checkpatch: 1 trailing whitespace error

Non-blocking issues:

check-patch-compliance failure is expected for QCLINUX: prefix (vendor-only commit)

Undocumented DT compatible strings are acceptable for vendor-only camera drivers

Recommended action:

Add the missing base DTB files (lemans-draco-evk.dts, lemans-draco-evk-el2.dts) to the PR, or remove the Makefile entries if they're not ready

Fix all indentation errors (use tabs consistently)

Remove trailing whitespace

Re-run CI

qswat-orbit-external · 2026-10-09T04:44:56Z

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

qlijarvis · 2026-10-10T08:59:45Z

PR #1040 — validate-patch

PR: #1040

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/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1040 - QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
Upstream commit: N/A (vendor-only)
Verdict: ✅ PASS

Commit Message

Check Status Note

Subject matches upstream N/A Vendor-only commit (QCLINUX: prefix)

Body preserves rationale ✅ Clear description of camera sensor additions

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

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

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

Diff

File Status Notes

arch/arm64/boot/dts/qcom/Makefile ✅ Adds build rules for lemans-draco-evk camera overlays

arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi ✅ New file: 811 lines of camera sensor definitions

arch/arm64/boot/dts/qcom/lemans-draco-evk-camx.dtso ✅ New file: 138 lines of camera overlay

Issues

None. This is a vendor-only commit with the correct QCLINUX: prefix. No lore link is expected or required for vendor-specific device tree additions.

Verdict

Merge as-is. This is a properly formatted vendor-only commit adding Qualcomm-specific camera sensor device tree nodes for the Lemans Draco EVK platform.

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/topics: Not checked — QCLINUX: vendor-only commit

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

Commit Subject qcom-next topics Final

1/1 [PATCH] QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing

Final Status

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

qlijarvis · 2026-10-10T08:59:46Z

PR #1040 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	40 errors, 26 warnings
dt-binding-check	⏭️	No binding changes
dtb-check	❌	Build failure: missing base DTB
sparse-check	⏭️	No C/H changes
check-uapi-headers	⏭️	No C/H changes
check-patch-compliance	❌	Invalid prefix `QCLINUX:`
tag-check	❌	Missing required prefix (mandatory for qcom-6.18.y)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1040 - QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/37885386744
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ❌ 40 errors, 26 warnings

dt-binding-check ⏭️ No binding changes

dtb-check ❌ Build failure: missing base DTB

sparse-check ⏭️ No C/H changes

check-uapi-headers ⏭️ No C/H changes

check-patch-compliance ❌ Invalid prefix QCLINUX:

tag-check ❌ Missing required prefix (mandatory for qcom-6.18.y)

❌ checkpatch

Root cause: Multiple coding style violations — mixed spaces/tabs indentation (40 errors), trailing whitespace (4 errors), undocumented DT compatible strings (26 warnings), and long commit description line.

Failure details:
9879228a42bad5c331dbe58a4eca1409fe8bf7f0 total: 40 errors, 26 warnings, 0 checks, 964 lines checked

ERROR: code indent should use tabs where possible
#90: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:47
#91: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:48
[... 36 more instances across lines 87, 88, 121, 122, 161, 162, 197, 246, etc.]

ERROR: trailing whitespace
#214: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:171
#413: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:370
#613: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:570
#812: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:769

WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)

WARNING: DT compatible string "qcom,actuator" appears un-documented
WARNING: DT compatible string "qcom,eeprom" appears un-documented
WARNING: DT compatible string "qcom,cam-sensor" appears un-documented
WARNING: DT compatible string "qcom,cam-res-mgr" appears un-documented
Fix:
Fix indentation errors — replace spaces with tabs:
# Use checkpatch's auto-fix capability
./scripts/checkpatch.pl --fix-inplace --types=CODE_INDENT arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi

# Or manually with sed (convert leading spaces to tabs)
sed -i 's/^        /\t/g' arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi
Remove trailing whitespace:
sed -i 's/[[:space:]]*$//' arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi
Wrap commit description — the commit body line exceeds 75 chars. Edit the commit message:
git commit --amend
# Wrap the description line at 75 chars
Undocumented DT compatible strings — these are vendor-specific camera subsystem bindings (qcom,actuator, qcom,eeprom, qcom,cam-sensor, qcom,cam-res-mgr). These warnings are expected for vendor-only camera nodes and can be accepted as-is if bindings are not being upstreamed. If bindings will be added later, document them in Documentation/devicetree/bindings/.
Amend the commit:
git add arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi
git commit --amend --no-edit
Reproduce locally:
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git f19f3cdab691f3d6d8bcccf03e46669ba4e714ea..823a86e66ad719ef7aa82a028190768f8f1993a4
❌ dtb-check

Root cause: Build failure — the Makefile references lemans-draco-evk.dtb as a dependency for the overlay lemans-draco-evk-camx.dtb, but lemans-draco-evk.dtb does not exist in the tree.

Failure details:
make[4]: *** No rule to make target 'arch/arm64/boot/dts/qcom/lemans-draco-evk.dtb', 
         needed by 'arch/arm64/boot/dts/qcom/lemans-draco-evk-camx.dtb'.  Stop.
No DTBs were built under head; nothing to validate.
Fix:

The Makefile in arch/arm64/boot/dts/qcom/Makefile declares:
lemans-draco-evk-camx-dtbs := lemans-draco-evk.dtb lemans-draco-evk-camx.dtbo
This line states that lemans-draco-evk-camx.dtb depends on lemans-draco-evk.dtb, but that base DTB file does not exist.

Two possible fixes:
If lemans-draco-evk.dts should exist — add the missing base board DTS file:
# Create arch/arm64/boot/dts/qcom/lemans-draco-evk.dts
# Add it to the Makefile:
dtb-$(CONFIG_ARCH_QCOM) += lemans-draco-evk.dtb
If the overlay should use a different base — update the Makefile to reference the correct base DTB (e.g., lemans-evk.dtb if Draco is a variant):
lemans-draco-evk-camx-dtbs := lemans-evk.dtb lemans-draco-evk-camx.dtbo
lemans-draco-evk-camx-el2-dtbs := lemans-evk-el2.dtb lemans-draco-evk-camx.dtbo lemans-camx-el2.dtbo
Reproduce locally:
make -j$(nproc) O=out defconfig
make -j$(nproc) O=out arch/arm64/boot/dts/qcom/lemans-draco-evk-camx.dtb
❌ check-patch-compliance

Root cause: The commit subject uses the QCLINUX: prefix, which is not in the allowed list for check-patch-compliance. This checker only accepts FROMLIST:, FROMGIT:, UPSTREAM:, and BACKPORT: prefixes.

Failure details:
Checking commit: QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
Commit summary does not start with a required prefix
Fix:

This is a known limitation of the check-patch-compliance checker — it enforces upstream-linkable prefixes only and rejects vendor-only prefixes like QCLINUX: and PENDING:.

If this is a vendor-only change with no upstream equivalent:

The checker will always fail for QCLINUX: commits. This is expected behavior.

No patch change is needed — the failure is a checker limitation, not a defect.

Proceed with merge if the change is intentionally vendor-only.

If this change has been or will be posted upstream:
Change the prefix to FROMLIST: and add a Link: trailer pointing to the lore.kernel.org URL:
git commit --amend -m "FROMLIST: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577

Add camera sensor device tree nodes for the Draco-based Lemans EVK to enable imx858, ov13b10 and imx577 sensors.

Link: https://lore.kernel.org/...
Signed-off-by: Sushil Pratap Singh <sussin@qti.qualcomm.com>"
Reproduce locally:
# Clone kernel-checkers repo
git clone https://github.com/qualcomm-linux/kernel-checkers.git
bash kernel-checkers/check-patch-compliance.sh --kernel-src . --base <base_sha> --head <head_sha>
❌ tag-check

Root cause: The PR targets qcom-6.18.y, which is not qcom-next or qcom-next-staging. All commits merged into branches other than those two must start with a valid prefix tag. The commit uses QCLINUX:, which is valid, but check-patch-compliance rejects it (see above).

Analysis:

The commit subject is:
QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
The prefix QCLINUX: is a valid tag for the tag-check (it's in the allowed list: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, WORKAROUND:).

Verdict: ✅ PASS for tag-check — the commit has a valid prefix.

However, check-patch-compliance (a separate checker) rejects QCLINUX: because it only accepts upstream-linkable prefixes. This is a known discrepancy between the two checkers.

Recommendation

3 blockers must be fixed before merge:

checkpatch — Fix 40 indentation errors and 4 trailing whitespace errors. Use ./scripts/checkpatch.pl --fix-inplace or manual sed commands. The 26 undocumented DT compatible warnings are acceptable for vendor-only camera nodes.

dtb-check — Fix the missing lemans-draco-evk.dtb dependency. Either add the missing base DTS file or update the Makefile to reference an existing base DTB (e.g., lemans-evk.dtb).

check-patch-compliance — If this is a vendor-only change, the QCLINUX: prefix failure is expected and can be accepted. If the change will be posted upstream, change the prefix to FROMLIST: and add a Link: trailer.

After fixes:

Re-run checkpatch locally to verify all errors are resolved.

Build the DTBs locally to confirm the Makefile dependency is correct.

Re-trigger CI to get a clean run.

sushilsingh045 · 2026-10-15T04:55:09Z

Waiting for the base DT branch to get merged

qlijarvis · 2026-11-05T12:06:29Z

PR #1040 — validate-patch

PR: #1040

Verdict	Issues	Detailed Report
⚠️	1	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/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1040 - QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
Upstream commit: N/A (vendor-only commit)
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note

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

Body preserves rationale ✅ Clear description of camera sensor additions

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

Authorship preserved ✅ Proper author and Signed-off-by present

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

Diff

File Status Notes

arch/arm64/boot/dts/qcom/Makefile ✅ Adds camera overlay build targets for lemans-draco-evk

arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi ✅ New file: camera sensor definitions (811 lines)

arch/arm64/boot/dts/qcom/lemans-draco-evk-camx.dtso ✅ New file: camera overlay (138 lines)

Issues

Integration presence: Commit is missing from both qcom-next and kernel-topics branches. For a QCLINUX: vendor commit, this may be expected if it's a new addition, but verify this is intentional and not a duplicate of existing work.

Verdict

This is a vendor-only camera sensor enablement patch for Lemans Draco EVK. The commit message is clear and properly formatted. However, the commit is not present in qcom-next or topics branches - verify this is a new addition and not duplicating existing work before merging.

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/topics: No — commit missing from both qcom-next and topics (per integration_presence_report.md). This may be expected for a new vendor addition, but should be verified to avoid duplicating existing work.

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

Commit Subject qcom-next topics Final

1/1 [PATCH] QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing

Final Status

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

qlijarvis · 2026-11-05T12:06:30Z

PR #1040 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	25 warnings: undocumented DT compatible strings
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	⚠️	Warnings present but no DTBs built for validation
sparse-check	⏭️	Skipped (no C/H file changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	Prefix violation: `QCLINUX:` not accepted
tag-check	❌	Subject prefix required for non-qcom-next branches

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1040 - QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/42018508741
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ❌ 25 warnings: undocumented DT compatible strings

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

dtb-check ⚠️ Warnings present but no DTBs built for validation

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

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

check-patch-compliance ❌ Prefix violation: QCLINUX: not accepted

tag-check ❌ Subject prefix required for non-qcom-next branches

❌ checkpatch

Root cause: The patch introduces 25 instances of undocumented DT compatible strings for Qualcomm camera subsystem components.

Failure details:
WARNING: DT compatible string "qcom,cam-sensor" appears un-documented
WARNING: DT compatible string "qcom,actuator" appears un-documented
WARNING: DT compatible string "qcom,eeprom" appears un-documented
WARNING: DT compatible string "qcom,cam-res-mgr" appears un-documented

3f9145724b38 total: 0 errors, 25 warnings, 0 checks, 967 lines checked
Commit 3f9145724b38 ("QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes") has style problems
The warnings appear across multiple files:

arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi (multiple instances)

Fix: Add YAML binding documentation for the camera subsystem compatible strings:

Create Documentation/devicetree/bindings/media/qcom,cam-sensor.yaml covering:

qcom,cam-sensor

qcom,actuator

qcom,eeprom

qcom,cam-res-mgr

Alternatively, if these are vendor-specific bindings not intended for upstream, the warnings can be noted as expected for QCLINUX: prefixed commits.

Reproduce locally:
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 5553ec2d6565..3f9145724b38
❌ check-patch-compliance

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

Failure details:
Checking commit: QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
Commit summary does not start with a required prefix
Analysis: This is a known limitation of the check-patch-compliance checker. The checker only accepts upstream-linkable prefixes:

FROMLIST: (posted to mailing list)

FROMGIT: (in maintainer tree)

UPSTREAM: (merged to mainline)

BACKPORT: (backported with modifications)

The QCLINUX: prefix is used for vendor-only changes with no upstream equivalent, which this checker does not recognize.

Fix options:

If this is truly vendor-only: Accept that check-patch-compliance will always fail for QCLINUX: commits. This is expected behavior.

If the camera sensor nodes could be upstreamed: Change the prefix to FROMLIST: and post the patches to the devicetree mailing list, then add a Link: tag pointing to the lore.kernel.org URL.

Reproduce locally:
# The checker requires the commit to have FROMLIST:/FROMGIT:/UPSTREAM:/BACKPORT: prefix
# and a Link: tag pointing to lore.kernel.org
❌ tag-check

Root cause: The target branch is qcom-6.18.y (not qcom-next or qcom-next-staging), which requires all commits to have a subject prefix tag.

Analysis: The commit subject is:
QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
The commit does have a valid prefix (QCLINUX:), so this check PASSES.

Verdict: ✅ PASS — The commit has the required QCLINUX: prefix.

⚠️ dtb-check

Root cause: The checker detected graph_port, reg_format, and avoid_default_addr_size warnings in the new lemans-camera-sensor.dtsi file, but no DTBs were actually built for validation.

Failure details:
Warning (graph_port): port@0: graph node '#address-cells' is -1, must be 1
Warning (graph_port): port@0: graph node '#size-cells' is -1, must be 0
Warning (reg_format): port@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
Warning (avoid_default_addr_size): port@0: Relying on default #address-cells value

No DTBs were built under head; nothing to validate.
Analysis: The warnings indicate structural issues in the camera sensor device tree overlay:

Graph port nodes are missing explicit #address-cells = <1>; #size-cells = <0>; declarations

Port reg properties have incorrect cell counts (4 bytes instead of expected format)

Nodes rely on default address/size cell values instead of explicit declarations

However, the checker reported "No DTBs were built under head", meaning the validation could not complete. This suggests the DTB build may have failed or the file is not included in any board's build.

Fix:
Add explicit #address-cells and #size-cells to all graph port parent nodes:
ports {
    #address-cells = <1>;
    #size-cells = <0>;
    
    port@0 {
        reg = <0>;  /* Single cell, not <0 0> */
        ...
    };
};
Fix reg properties in port nodes to use single-cell format (not multi-cell)

Ensure the DTSI is included in a board DTS that gets built during make dtbs
Reproduce locally:
make -j$(nproc) O=out defconfig
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/lemans-*.dtb
Verdict

2 blockers to fix before merge:

checkpatch warnings — 25 undocumented DT compatible strings. Either add YAML bindings or accept warnings for vendor-specific QCLINUX: commits.

check-patch-compliance failure — Expected for QCLINUX: prefix (known checker limitation). If vendor-only, this can be accepted. If upstreamable, change to FROMLIST: and add Link: tag.

dtb-check warnings — Graph port structure issues need fixing (missing #address-cells/#size-cells, incorrect reg format). However, validation was incomplete due to no DTBs being built.

Recommendation: Fix the dtb-check graph port structure issues and verify the DTB builds cleanly. The checkpatch and check-patch-compliance failures are expected for vendor-only QCLINUX: commits and can be accepted if this code is not intended for upstream submission.

qlijarvis · 2026-11-05T12:09:47Z

🔨 Build Failure Analysis — PR #1040

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

#	Error	File:Line	PR-introduced?	Root Cause
1	No rule to make target 'lemans-draco-evk.dtb'	arch/arm64/boot/dts/qcom/Makefile:481	Yes	Makefile references `lemans-draco-evk.dtb` but the corresponding `lemans-draco-evk.dts` source file is not included in the PR
2	No rule to make target 'lemans-draco-evk-el2.dtb'	arch/arm64/boot/dts/qcom/Makefile:489	Yes	Makefile references `lemans-draco-evk-el2.dtb` but the corresponding `lemans-draco-evk-el2.dts` source file is not included in the PR

Verdict

Both errors are introduced by this PR. The PR adds Makefile entries for device tree overlays that depend on base device tree files that are missing from the PR.

📎 Detailed analysis: Full report

qlijarvis · 2026-11-05T12:15:22Z

🔨 Build Failure Analysis — PR #1040

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

#	Error	File:Line	PR-introduced?	Root Cause
1	No rule to make target 'lemans-draco-evk.dtb'	`arch/arm64/boot/dts/qcom/Makefile:481`	Yes	Makefile references non-existent base DTB file `lemans-draco-evk.dtb` as dependency for overlay
2	No rule to make target 'lemans-draco-evk-el2.dtb'	`arch/arm64/boot/dts/qcom/Makefile:488`	Yes	Makefile references non-existent base DTB file `lemans-draco-evk-el2.dtb` as dependency for overlay

Verdict

Both errors are introduced by this PR. The PR adds Makefile rules that depend on base DTB files (lemans-draco-evk.dtb and lemans-draco-evk-el2.dtb) that do not exist in the kernel tree.

📎 Detailed analysis: Full report

…raco EVK Add camera support for Lemans Draco EVK to enable imx858, ov13b10 and imx577 sensors on the four CSI port available on the board. Signed-off-by: Sushil Pratap Singh <sussin@qti.qualcomm.com>

qlijarvis · 2026-11-06T14:12:46Z

PR #1040 — validate-patch

PR: #1040

Verdict	Issues	Detailed Report
❌	1	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/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1040 - QCLINUX: arm64: dts: qcom: lemans: Add camera DT changes for Lemans Draco EVK
Upstream commit: N/A (vendor-only)
Verdict: ❌ FAIL

Commit Message

Check Status Note

Subject matches upstream N/A Vendor-only commit (QCLINUX:)

Body preserves rationale ✅ Clear description of camera support addition

Fixes tag present/correct N/A New feature, not a fix

Authorship preserved ✅ Correct for vendor commit

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

Diff

File Status Notes

arch/arm64/boot/dts/qcom/Makefile ✅ Adds camera overlay build targets for Lemans Draco EVK

arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi ✅ New camera sensor device tree include (803 lines)

arch/arm64/boot/dts/qcom/lemans-draco-evk-camx.dtso ✅ New camera overlay (138 lines)

Issues

Integration presence failure: Commit is missing from both qcom-next and kernel topics branches. QCLINUX: vendor commits should typically be present in qcom-next before PR merge.

Verdict

Reject - commit is missing from qcom-next and topics integration branches. Vendor-only commits should be integrated into qcom-next before being accepted via PR.

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/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics (per integration_presence_report.md)

Deterministic Integration Presence

Integration Presence Report

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

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

Commit Subject qcom-next topics Final

1/1 [PATCH] QCLINUX: arm64: dts: qcom: lemans: Add camera DT changes for missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing

Final Status

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

qlijarvis · 2026-11-06T14:12:48Z

PR #1040 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	25 warnings: undocumented DT compatible strings
dt-binding-check	⏭️	No binding changes
dtb-check	❌	Build failure: missing `lemans-draco-evk.dtb` dependency
sparse-check	⏭️	No C/H file changes
check-uapi-headers	⏭️	No C/H file changes
check-patch-compliance	❌	`QCLINUX:` prefix not in allowed list
tag-check	⚠️	`QCLINUX:` is valid for vendor-only commits (see note)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1040 - QCLINUX: arm64: dts: qcom: lemans: Add camera DT changes for Lemans Draco EVK
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/42227418064
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ❌ 25 warnings: undocumented DT compatible strings

dt-binding-check ⏭️ No binding changes

dtb-check ❌ Build failure: missing lemans-draco-evk.dtb dependency

sparse-check ⏭️ No C/H file changes

check-uapi-headers ⏭️ No C/H file changes

check-patch-compliance ❌ QCLINUX: prefix not in allowed list

tag-check ⚠️ QCLINUX: is valid for vendor-only commits (see note)

❌ checkpatch

Root cause: 25 undocumented DT compatible strings for camera subsystem components.

Failure details:
WARNING: DT compatible string "qcom,eeprom" appears un-documented
WARNING: DT compatible string "qcom,cam-sensor" appears un-documented
WARNING: DT compatible string "qcom,actuator" appears un-documented
WARNING: DT compatible string "qcom,cam-res-mgr" appears un-documented
These warnings appear repeatedly across the new lemans-draco-evk-camera-sensor.dtsi file for camera sensor nodes (eeprom, cam-sensor, actuator, cam-res-mgr).

Fix:

These are vendor-specific camera subsystem compatible strings used by Qualcomm's camera driver stack. You have two options:

Add DT binding documentation (recommended for upstream-bound code):

Create Documentation/devicetree/bindings/media/qcom,cam-sensor.yaml

Create Documentation/devicetree/bindings/media/qcom,eeprom.yaml

Create Documentation/devicetree/bindings/media/qcom,actuator.yaml

Create Documentation/devicetree/bindings/media/qcom,cam-res-mgr.yaml

Accept the warnings (if vendor-only):

These are vendor-specific bindings for the Qualcomm camera subsystem

If this code is not intended for upstream submission, the warnings can be noted but not necessarily fixed

The QCLINUX: prefix already indicates this is vendor-only code

Reproduce locally:
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 9bdb1505d1f89a6f5d4e443d9c6b89aee16d28ff..1a5f2f3d84e1db193686f765618bd3b24e1590d3
❌ dtb-check

Root cause: Build failure due to missing DTB dependency in Makefile.

Failure details:
make[4]: *** No rule to make target 'arch/arm64/boot/dts/qcom/lemans-draco-evk.dtb', 
needed by 'arch/arm64/boot/dts/qcom/lemans-draco-evk-camx.dtb'.  Stop.
The Makefile references lemans-draco-evk-camx.dtb which depends on lemans-draco-evk.dtb, but lemans-draco-evk.dtb is not defined in the Makefile or does not exist in the tree.

Fix:

Check arch/arm64/boot/dts/qcom/Makefile and verify:

If lemans-draco-evk.dts exists in the tree:

Ensure lemans-draco-evk.dtb is listed in the Makefile before lemans-draco-evk-camx.dtb

The overlay .dtbo depends on the base .dtb being built first

If lemans-draco-evk.dts does NOT exist:

Either add the base DTS file first in a separate commit

Or change the Makefile entry to build only the overlay if the base DTB is provided externally

Or change lemans-draco-evk-camx.dtso to reference a different base DTB that exists

Reproduce locally:
make -j$(nproc) O=out defconfig
make -j$(nproc) O=out arch/arm64/boot/dts/qcom/lemans-draco-evk-camx.dtb
❌ check-patch-compliance

Root cause: QCLINUX: prefix is not in the checker's allowed list.

Failure details:
Checking commit: QCLINUX: arm64: dts: qcom: lemans: Add camera DT changes for Lemans Draco EVK
Commit summary does not start with a required prefix
The check-patch-compliance checker only accepts these prefixes:

FROMLIST: (posted to mailing list)

FROMGIT: (from maintainer tree)

UPSTREAM: (merged into mainline)

BACKPORT: (backported with modifications)

Fix:

This is a known limitation of the check-patch-compliance checker. The QCLINUX: prefix is a valid vendor-internal prefix used in the Qualcomm Linux kernel tree for vendor-only changes that have no upstream equivalent.

Options:

Accept the failure (recommended for vendor-only code):

The QCLINUX: prefix correctly indicates this is vendor-specific camera support

This checker failure is expected for vendor-only commits

No patch change needed

If the code was posted upstream:

Change prefix to FROMLIST: and add Link: <lore-url> to the commit body

But this only applies if the patch was actually posted to a mailing list

Note: The tag-check (see below) considers QCLINUX: a valid prefix for vendor-only commits.

⚠️ tag-check (manual check)

Status: ✅ PASS (with note)

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

Note: The target branch is qcom-6.18.y (not qcom-next or qcom-next-staging), so a subject prefix is required. The QCLINUX: prefix is appropriate for vendor-specific camera subsystem support that has no upstream equivalent.

Valid prefixes for qcom-6.18.y:

FROMLIST: / FROMGIT: / UPSTREAM: / BACKPORT: (for upstream-related commits)

QCLINUX: / PENDING: / WORKAROUND: (for vendor-only commits)

Verdict

2 blockers must be fixed before merge:

dtb-check build failure — Missing lemans-draco-evk.dtb dependency. Either add the base DTS file or fix the Makefile dependency chain.

checkpatch warnings — 25 undocumented DT compatible strings. Either add binding documentation or accept the warnings if this is vendor-only code.

1 expected failure (no action needed):

check-patch-compliance — The QCLINUX: prefix is correct for vendor-only code but not accepted by this checker. This is a known limitation.

sushilsingh045 requested review from a team, Komal Bajaj (Komal-Bajaj), aiquny and Dmitry Baryshkov (lumag) September 4, 2026 06:22

sushilsingh045 force-pushed the qli_2_0_lemans_draco_camera_sensor_dtsi branch from 5c90fa5 to 235fba5 Compare September 9, 2026 04:20

sushilsingh045 force-pushed the qli_2_0_lemans_draco_camera_sensor_dtsi branch from 235fba5 to a1604ea Compare September 17, 2026 19:25

Salendarsingh Gaud (sgaud-quic) force-pushed the qcom-6.18.y branch from 6daff4a to 55b3fbc Compare September 18, 2026 05:47

sushilsingh045 force-pushed the qli_2_0_lemans_draco_camera_sensor_dtsi branch from a1604ea to b777813 Compare September 29, 2026 14:33

sushilsingh045 force-pushed the qli_2_0_lemans_draco_camera_sensor_dtsi branch from b777813 to 01da58b Compare September 29, 2026 14:36

sushilsingh045 force-pushed the qli_2_0_lemans_draco_camera_sensor_dtsi branch from 01da58b to 9879228 Compare October 9, 2026 04:44

sushilsingh045 marked this pull request as draft October 15, 2026 04:54

sushilsingh045 force-pushed the qli_2_0_lemans_draco_camera_sensor_dtsi branch from 9879228 to 3f91457 Compare October 31, 2026 11:57

sushilsingh045 changed the title ~~QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577~~ arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577 Oct 31, 2026

tharanwa mentioned this pull request Nov 2, 2026

arm64: dts: qcom: lemans: Add changes for OX03F10 GMSL Camera Support #1375

Draft

Shiraz Hashim (shashim-quic) previously approved these changes Nov 5, 2026

View reviewed changes

qcomlnxci requested a review from a team November 5, 2026 11:23

QCLINUX: arm64: dts: qcom: lemans: Add camera DT changes for Lemans D…

1a5f2f3

…raco EVK Add camera support for Lemans Draco EVK to enable imx858, ov13b10 and imx577 sensors on the four CSI port available on the board. Signed-off-by: Sushil Pratap Singh <sussin@qti.qualcomm.com>

sushilsingh045 dismissed Shiraz Hashim (shashim-quic)’s stale review via 1a5f2f3 November 6, 2026 13:39

sushilsingh045 force-pushed the qli_2_0_lemans_draco_camera_sensor_dtsi branch from 3f91457 to 1a5f2f3 Compare November 6, 2026 13:39

Conversation

sushilsingh045 commented Sep 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qswat-orbit-external Bot commented Sep 4, 2026

Uh oh!

qswat-orbit-external Bot commented Sep 9, 2026

Uh oh!

qlijarvis commented Sep 9, 2026

PR #1040 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Verdict

Final Summary

Deterministic Integration Presence

Integration Presence Report

Final Status

Uh oh!

qlijarvis commented Sep 9, 2026

PR #1040 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ checkpatch

❌ check-patch-compliance

⚠️ tag-check (manual check for qcom-6.18.y)

Verdict

Uh oh!

qswat-orbit-external Bot commented Sep 17, 2026

Uh oh!

qlijarvis commented Sep 17, 2026

PR #1040 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Issues

Verdict

Final Summary

Deterministic Integration Presence

Integration Presence Report

Final Status

Uh oh!

qlijarvis commented Sep 17, 2026

PR #1040 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ dtb-check — DTS Syntax Error (BLOCKER)

❌ checkpatch — Code Style Violations

❌ check-patch-compliance — Prefix Not Accepted

⚠️ tag-check — Subject Prefix (Manual Check)

ℹ️ dtb-check — Pre-Existing Tree Issues (Not Caused by PR)

Verdict

Uh oh!

qswat-orbit-external Bot commented Sep 29, 2026

Uh oh!

qswat-orbit-external Bot commented Sep 29, 2026

Uh oh!

qlijarvis commented Oct 8, 2026

PR #1040 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Issues

Verdict

Final Summary

Deterministic Integration Presence

Integration Presence Report

Final Status

Uh oh!

qlijarvis commented Oct 8, 2026

PR #1040 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ dtb-check — Build Failure (BLOCKER)

❌ checkpatch — Coding Style Violations

❌ check-patch-compliance — Prefix Not Allowed

✅ tag-check — Subject Prefix Valid

Verdict

Uh oh!

qswat-orbit-external Bot commented Oct 9, 2026

sushilsingh045 commented Sep 4, 2026 •

edited

Loading