Skip to content

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

Draft
tharanwa wants to merge 2 commits into
qualcomm-linux:qcom-6.18.yfrom
tharanwa:qli_2_0_camera_lemans_draco
Draft

tharanwa wants to merge 2 commits into
qualcomm-linux:qcom-6.18.yfrom
tharanwa:qli_2_0_camera_lemans_draco

Conversation

@tharanwa

@tharanwa tharanwa commented Nov 2, 2026

Copy link
Copy Markdown
  • Added multi-camera support on CSI0, CSI1, CSI2 and CSI3 ports.
  • 4 sensors are supported on each of the 4 CSI camera ports.
  • Target: Lemans Draco, Sensor: Omnivision OX03F10, Ser: MAX96717, Des: MAX96724, Power IC: MAX20086.

CRs-Fixed: 4730275

…, ov13b10 and imx577

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

Signed-off-by: Sushil Pratap Singh <sussin@qti.qualcomm.com>
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4730275 is not eligible for merge.

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

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

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

@tharanwa

tharanwa commented Nov 2, 2026

Copy link
Copy Markdown
Author

Moving to draft.
This PR will be rebased and moved to active after PR#1040 gets merged.

@tharanwa
tharanwa marked this pull request as draft November 2, 2026 06:13
@tharanwa
tharanwa force-pushed the qli_2_0_camera_lemans_draco branch from ed40468 to 61e28a9 Compare November 2, 2026 07:45
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4730275 is not eligible for merge.

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

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

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

@tharanwa
tharanwa force-pushed the qli_2_0_camera_lemans_draco branch from 61e28a9 to 1115ebe Compare November 2, 2026 07:56
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4730275 is not eligible for merge.

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

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

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

@qlijarvis

Copy link
Copy Markdown

PR #1375 — validate-patch

PR: #1375

Verdict Issues Detailed Report
⚠️ 3 Full report

Final Summary

  1. Lore link present: No — QCLINUX: prefix; no lore link expected or required for vendor-only commits
  2. Lore link matches PR commits: N/A — no lore link to compare against (vendor-only changes)
  3. Upstream patch status: N/A — vendor-only changes, not posted upstream
  4. PR present in qcom-next/topics: Fail - 2/2 commit(s) are missing from both qcom-next and topics
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1375 - QCLINUX: arm64: dts: qcom: lemans camera sensor support (2 commits)
Upstream commit: N/A (vendor-only commits)
Verdict: ⚠️ PARTIAL


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

Commit Message

Check Status Note
Subject matches upstream N/A QCLINUX: prefix — vendor-only commit
Body preserves rationale ✅ Clear description of added camera sensor nodes
Fixes tag present/correct N/A New feature, no Fixes tag expected
Authorship preserved ✅ Sushil Pratap Singh sussin@qti.qualcomm.com
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds lemans-draco-evk-camx build targets
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

Commit 2/2: QCLINUX: arm64: dts: qcom: lemans: Add changes for OX03F10 GMSL Camera Support

Commit Message

Check Status Note
Subject matches upstream N/A QCLINUX: prefix — vendor-only commit
Body preserves rationale ✅ Clear description: multi-camera support on 4 CSI ports, sensor details
Fixes tag present/correct N/A New feature, no Fixes tag expected
Authorship preserved ✅ Tharik Anwar tharanwa@qti.qualcomm.com
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi ✅ Adds 476 lines for OX03F10 GMSL camera support

Issues

Integration Presence (Critical):

  • ❌ Both commits are missing from qcom-next and kernel-topics branches
    • Commit 1/2: Not found in qcom-next or topics (no subject, patch-id, or tree-content match)
    • Commit 2/2: Not found in qcom-next or topics (no subject, patch-id, or tree-content match)
    • Impact: These vendor-only changes have not been integrated into the authoritative qcom-next branch yet

Commit Message Quality:

  • ⚠️ Commit 1/2 subject line is truncated in the patch series header (ends with "imx577" but full context is clear in body)
  • ⚠️ Commit 2/2 uses bullet-point format in body — acceptable for vendor commits but differs from typical kernel style

Verdict

⚠️ PARTIAL — Integration presence check failed

Both commits are well-formed vendor-only changes with clear authorship and appropriate QCLINUX: prefixes. The commit messages adequately describe the camera sensor additions for Lemans Draco EVK. However, neither commit is present in qcom-next or kernel-topics branches, which is a validation failure per the skill requirements.

Recommendation:

  • If these commits are intended for immediate merge into qcom-next, they should be integrated there first before being included in downstream PRs
  • If this PR targets a different branch (e.g., a vendor-specific integration branch), clarify the target branch and integration workflow
  • Verify that the missing integration presence is intentional (e.g., this PR is the mechanism for adding them to qcom-next)

Final Summary

  1. Lore link present: No — QCLINUX: prefix; no lore link expected or required for vendor-only commits
  2. Lore link matches PR commits: N/A — no lore link to compare against (vendor-only changes)
  3. Upstream patch status: N/A — vendor-only changes, not posted upstream
  4. PR present in qcom-next/topics: Fail — 2/2 commits are missing from both qcom-next and topics branches (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/2 [PATCH 1/2] QCLINUX: arm64: dts: qcom: lemans: Add camera sensor missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
2/2 [PATCH 2/2] QCLINUX: arm64: dts: qcom: lemans: Add 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/2
partial_commits: 0/2
missing_commits: 2/2
topics_checked_for_commits: 2/2
final_summary: PR present in qcom-next/topics: Fail - 2/2 commit(s) are missing from both qcom-next and topics

@qlijarvis

Copy link
Copy Markdown

PR #1375 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ❌ 8 errors, 16 warnings in commit 1115ebe
dt-binding-check ⏭️ No binding changes
dtb-check ⏭️ No checker job found (likely skipped)
sparse-check ⏭️ No C/H file changes
check-uapi-headers ⏭️ No C/H file changes
check-patch-compliance ❌ Both commits use QCLINUX: prefix
tag-check ⚠️ QCLINUX: prefix is valid but see note below

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1375 - QCLINUX: arm64: dts: qcom: lemans: Add camera sensor support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/41409668730
Target Branch: qcom-6.18.y

Checker Result Summary
checkpatch ❌ 8 errors, 16 warnings in commit 1115ebe
dt-binding-check ⏭️ No binding changes
dtb-check ⏭️ No checker job found (likely skipped)
sparse-check ⏭️ No C/H file changes
check-uapi-headers ⏭️ No C/H file changes
check-patch-compliance ❌ Both commits use QCLINUX: prefix
tag-check ⚠️ QCLINUX: prefix is valid but see note below

❌ checkpatch

Root cause: Commit 1115ebe contains 8 indentation errors (spaces instead of tabs) and 16 undocumented DT compatible string warnings.

Failure details:

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

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

(6 more similar errors at lines 353, 354, 671, 672, 989, 990)

WARNING: DT compatible string "qcom,cam-gmsl-sensor" appears un-documented
#118: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:118:
+		compatible = "qcom,cam-gmsl-sensor";

(15 more instances of the same warning)

1115ebe6f74c total: 8 errors, 16 warnings, 0 checks, 504 lines checked

Fix:

  1. Indentation errors (8 ERRORs - MUST FIX):

    • Lines 35, 36, 353, 354, 671, 672, 989, 990 in lemans-draco-evk-camera-sensor.dtsi use spaces instead of tabs
    • Replace leading spaces with tabs:
    # Edit the file and replace spaces with tabs on the affected lines
    git add arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi
    git commit --amend --no-edit
  2. Undocumented compatible string (16 WARNINGs - SHOULD FIX):

    • qcom,cam-gmsl-sensor appears 16 times but has no binding documentation
    • Add a binding YAML file:
    # Create Documentation/devicetree/bindings/media/qcom,cam-gmsl-sensor.yaml
    # Or add to an existing camera binding if appropriate

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 58b1e624b961920b9e3924f17301dc4dd0ccc405..9d7c1cbc2eb10e916ff8a7f92bd9705a229b50d3

❌ check-patch-compliance

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

Failure details:

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

Checking commit: QCLINUX: arm64: dts: qcom: lemans: Add changes for OX03F10 GMSL Camera Support
Commit summary does not start with a required prefix

Fix:

This is a known checker limitation. The check-patch-compliance checker only accepts upstream-linkable prefixes (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:). It does not accept vendor-internal prefixes like QCLINUX:, PENDING:, or WORKAROUND:.

Options:

  1. If these patches have been posted upstream: Change prefix to FROMLIST: and add a Link: trailer pointing to the lore.kernel.org URL
  2. If these are vendor-only changes: The checker will always fail for QCLINUX: commits. This is expected behavior for vendor-specific devicetree additions that have no upstream equivalent.

For vendor-only DTS board enablement (which this appears to be), option 2 applies — the check-patch-compliance failure is expected and can be ignored.

Reproduce locally:

# Clone kernel-checkers repo
git clone https://github.com/qualcomm-linux/kernel-checkers.git
cd kernel-checkers
./check-patch-compliance.sh --kernel-src <path> --base 58b1e624b961 --head 71e9658f3d1d

⚠️ tag-check (Subject Prefix)

Status: ✅ PASS (with note)

Analysis:

The target branch is qcom-6.18.y, which is not qcom-next or qcom-next-staging. Therefore, subject-line prefix tags are mandatory for all commits.

Both commits use the QCLINUX: prefix:

  • Commit 1: QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
  • Commit 2: QCLINUX: arm64: dts: qcom: lemans: Add changes for OX03F10 GMSL Camera Support

QCLINUX: is a valid prefix tag (vendor-only change with no upstream equivalent). The commits satisfy the tag-check requirement.

Note: While tag-check passes, check-patch-compliance fails because it enforces a stricter subset of prefixes. This is a known discrepancy between the two checks for vendor-only commits.


Verdict

2 blockers must be fixed before merge:

  1. checkpatch — 8 indentation ERRORs (MUST FIX):

    • Replace spaces with tabs on lines 35, 36, 353, 354, 671, 672, 989, 990 in lemans-draco-evk-camera-sensor.dtsi
  2. checkpatch — 16 undocumented compatible string WARNINGs (SHOULD FIX):

    • Add binding documentation for qcom,cam-gmsl-sensor in Documentation/devicetree/bindings/media/

Known limitation (can be ignored):

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

Next steps:

  1. Fix the 8 indentation errors (mandatory)
  2. Add DT binding documentation for qcom,cam-gmsl-sensor (recommended)
  3. Re-run checkpatch locally to verify fixes
  4. Push updated commits to trigger a new CI run

…a Support

- Added multi-camera support on CSI0, CSI1, CSI2 and CSI3 ports.
- 4 sensors are supported on each of the 4 CSI camera ports.
- Target: Lemans Draco, Sensor: Omnivision OX03F10, Ser: MAX96717,
  Des: MAX96724, Power IC: MAX20086.

Signed-off-by: Tharik Anwar <tharanwa@qti.qualcomm.com>
@tharanwa
tharanwa force-pushed the qli_2_0_camera_lemans_draco branch from 1115ebe to 5d42041 Compare November 2, 2026 11:24
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4730275 is not eligible for merge.

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

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

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

@qlijarvis

Copy link
Copy Markdown

PR #1375 — validate-patch

PR: #1375

Verdict Issues Detailed Report
❌ 2 Full report

Final Summary

  1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: N/A — vendor-only change, not posted upstream
  4. PR present in qcom-next/topics: Fail - 2/2 commit(s) are missing from both qcom-next and topics
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1375 - QCLINUX: arm64: dts: qcom: lemans camera sensor support
Upstream commit: N/A (vendor-only QCLINUX commits)
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream N/A QCLINUX: vendor-only commits
Body preserves rationale ✅ Clear description of camera sensor additions
Fixes tag present/correct N/A New feature additions, no bug fix
Authorship preserved ✅ Commit 1: Sushil Pratap Singh; Commit 2: Tharik Anwar
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds lemans-draco-evk-camx build targets
arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi ✅ New file: 811 lines (commit 1), +469 lines (commit 2)
arch/arm64/boot/dts/qcom/lemans-draco-evk-camx.dtso ✅ New file: 138 lines of camera overlay

Issues

  • CRITICAL: Both commits (1/2 and 2/2) are missing from qcom-next and all kernel topic branches. Per integration_presence_report.md, no subject, patch-id, or full tree-content match was found in either qcom-next (ref 17bbb4b37bbc) or the topics remote.
  • This indicates the PR contains new work that has not been integrated into the baseline kernel tree.

Verdict

Reject - Both commits are absent from qcom-next and kernel-topics. QCLINUX vendor commits must be present in the integration baseline before being accepted in a PR. The commits need to be merged into qcom-next first, or this PR should target a different branch/workflow if it represents new development work.

Final Summary

  1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: N/A — vendor-only change, not posted upstream
  4. PR present in qcom-next/topics: Fail - 2/2 commit(s) are missing from both qcom-next and topics (per integration_presence_report.md: overall_status FAIL, 0/2 commits present)

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/2 [PATCH 1/2] QCLINUX: arm64: dts: qcom: lemans: Add camera sensor missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
2/2 [PATCH 2/2] QCLINUX: arm64: dts: qcom: lemans: Add 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/2
partial_commits: 0/2
missing_commits: 2/2
topics_checked_for_commits: 2/2
final_summary: PR present in qcom-next/topics: Fail - 2/2 commit(s) are missing from both qcom-next and topics

@qlijarvis

Copy link
Copy Markdown

PR #1375 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ❌ 16 warnings: undocumented DT compatible string qcom,cam-gmsl-sensor
dt-binding-check ⏭️ No binding changes
dtb-check ❌ Build failure: missing lemans-draco-evk.dtb prerequisite
sparse-check ⏭️ No C/H file changes
check-uapi-headers ⏭️ No C/H file changes
check-patch-compliance ❌ 2 commits: QCLINUX: prefix not in allowed list
tag-check ✅ Both commits have valid prefix (QCLINUX:)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1375 — Add camera sensor nodes for Lemans Draco EVK
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/41436683849
Target branch: qcom-6.18.y

Checker Result Summary
checkpatch ❌ 16 warnings: undocumented DT compatible string qcom,cam-gmsl-sensor
dt-binding-check ⏭️ No binding changes
dtb-check ❌ Build failure: missing lemans-draco-evk.dtb prerequisite
sparse-check ⏭️ No C/H file changes
check-uapi-headers ⏭️ No C/H file changes
check-patch-compliance ❌ 2 commits: QCLINUX: prefix not in allowed list
tag-check ✅ Both commits have valid prefix (QCLINUX:)

❌ checkpatch

Root cause: The compatible string "qcom,cam-gmsl-sensor" is used 16 times across both commits but has no corresponding vendor prefix or binding documentation.

Failure details:

WARNING: DT compatible string "qcom,cam-gmsl-sensor" appears un-documented -- check ./Documentation/devicetree/bindings/
#92: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:77:
+		compatible = "qcom,cam-gmsl-sensor";

(Repeated 16 times across lemans-draco-evk-camera-sensor.dtsi and lemans-draco-evk-camx.dtso)

Fix:
Add a device tree binding YAML file for qcom,cam-gmsl-sensor:

# Create the binding file
cat > Documentation/devicetree/bindings/media/qcom,cam-gmsl-sensor.yaml <<'EOF'
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/media/qcom,cam-gmsl-sensor.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Qualcomm Camera GMSL Sensor

maintainers:
  - <maintainer-email>

properties:
  compatible:
    const: qcom,cam-gmsl-sensor

  # Add other required properties here

required:
  - compatible

additionalProperties: false
EOF

# Commit the binding as a separate patch
git add Documentation/devicetree/bindings/media/qcom,cam-gmsl-sensor.yaml
git commit -m "dt-bindings: media: Add Qualcomm GMSL camera sensor binding"

Then rebase the DTS patches on top of the binding patch.

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 5c398266004176fbadb0864af19dd6e6ad3706c6..7beb6c869d656c4b3737b58f8b2fae1cb3a514ca

❌ dtb-check

Root cause: The Makefile references lemans-draco-evk.dtb as a prerequisite for building 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.

The Makefile adds:

lemans-draco-evk-camx-dtbs	:= lemans-draco-evk.dtb lemans-draco-evk-camx.dtbo
dtb-$(CONFIG_ARCH_QCOM)	+= lemans-draco-evk-camx.dtb

But lemans-draco-evk.dtb is never defined as a build target.

Fix:
Either:

  1. Add the base DTB if it should exist:

    dtb-$(CONFIG_ARCH_QCOM)	+= lemans-draco-evk.dtb

    And create the corresponding lemans-draco-evk.dts file.

  2. Or use an existing base DTB if lemans-draco-evk is a variant of another board:

    lemans-draco-evk-camx-dtbs	:= lemans-evk.dtb lemans-draco-evk-camx.dtbo
  3. Or remove the composite target if the overlay should be standalone:

    # Remove the composite target line:
    # lemans-draco-evk-camx-dtbs	:= lemans-draco-evk.dtb lemans-draco-evk-camx.dtbo
    
    # Keep only:
    dtb-$(CONFIG_ARCH_QCOM)	+= lemans-draco-evk-camx.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: Both commits use the QCLINUX: prefix, which is not in the checker's allowed list (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:).

Failure details:

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

Checking commit: QCLINUX: arm64: dts: qcom: lemans: Add changes for OX03F10 GMSL Camera Support
Commit summary does not start with a required prefix

Analysis:
The QCLINUX: prefix is a vendor-internal tag used for Qualcomm-specific changes that have no upstream equivalent. The check-patch-compliance checker enforces upstream-linkable prefixes only and will always fail for QCLINUX: commits. This is a known limitation of the checker.

Options:

  1. If these patches are vendor-only (no upstream submission planned):
    Accept that check-patch-compliance will fail. The QCLINUX: prefix is correct for vendor-only changes. The tag-check (which validates that a prefix exists) passes ✅.

  2. If these patches should be upstreamed:
    Post them to the mailing list and change the prefix to FROMLIST:, then add a Link: trailer:

    git rebase -i <base_sha>
    # Mark commits as 'edit'
    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:

# The checker will always fail for QCLINUX: commits
bash ../kernel-checkers/check-patch-compliance.sh --kernel-src . --base <base> --head <head>

Verdict

3 blockers must be fixed before merge:

  1. checkpatch — Add DT binding YAML for qcom,cam-gmsl-sensor (16 warnings)
  2. dtb-check — Fix Makefile: add lemans-draco-evk.dtb target or correct the composite DTB dependency
  3. check-patch-compliance — Known limitation for QCLINUX: prefix; acceptable if vendor-only, otherwise post upstream and use FROMLIST:

Note: The tag-check passes because both commits have a valid prefix (QCLINUX:). However, check-patch-compliance rejects QCLINUX: as it only accepts upstream-linkable prefixes. This is expected behavior for vendor-only patches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants