Skip to content

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

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

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
  • To bring-up OX03F10 GMSL cameras on Lemans Draco.
  • Added multi-camera support on port 0, 1, 2 and 3.
  • Sensor: Omnivision OX03F10, Ser: MAX96717, Des: MAX96724, Power IC: MAX20086.

CRs-Fixed: 4730275

@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

@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.

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #1375

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

# 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
2 No rule to make target 'lemans-draco-evk-el2.dtb' arch/arm64/boot/dts/qcom/Makefile:489 Yes Makefile references non-existent base DTB file lemans-draco-evk-el2.dtb

Verdict

Both build errors are introduced by this PR. The PR adds Makefile entries for composite DTB targets that depend on base DTB files (lemans-draco-evk.dtb and lemans-draco-evk-el2.dtb) which are not provided in the PR and do not exist in the tree.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #1375

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

# 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
2 No rule to make target 'lemans-draco-evk-el2.dtb' arch/arm64/boot/dts/qcom/Makefile:490 Yes Makefile references non-existent base DTB file lemans-draco-evk-el2.dtb

Verdict

Both errors are introduced by this PR. The PR adds composite DTB targets that depend on base DTB files that don't exist in the tree.

📎 Detailed analysis: Full report

@tharanwa
tharanwa force-pushed the qli_2_0_camera_lemans_draco branch from 5d42041 to 6de47a3 Compare November 10, 2026 12:13
@qcomlnxci
qcomlnxci requested a review from a team November 10, 2026 12:14
@tharanwa tharanwa changed the title arm64: dts: qcom: lemans: Add changes for OX03F10 GMSL Camera Support arm64: dts: qcom: lemans: Add changes for OX03F10 GMSL Cameras Nov 10, 2026
@tharanwa
tharanwa force-pushed the qli_2_0_camera_lemans_draco branch from 6de47a3 to 16952e1 Compare November 10, 2026 12:17
@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
  2. Lore link matches PR commits: N/A — no lore link to compare against
  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

Note: The integration presence failure is the primary concern. QCLINUX: commits typically land in qcom-next before being submitted via PR. Confirm with the submitter whether these commits should be in qcom-next first, or if direct merge to the target branch is intentional.

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1375 - QCLINUX: arm64: dts: qcom: lemans camera sensor support
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 camera sensor additions
Fixes tag present/correct N/A New feature, no Fixes tag required
Authorship preserved ✅ Author: Sushil Pratap Singh, 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

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

Commit Message

Check Status Note
Subject matches upstream N/A QCLINUX: prefix - vendor-only commit
Body preserves rationale ✅ Clear description of GMSL camera support
Fixes tag present/correct N/A New feature, no Fixes tag required
Authorship preserved ✅ Author: Tharik Anwar, 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 ✅ Extends file created in commit 1/2 with 469 lines for GMSL cameras

Issues

Integration Presence Failure:

  • Both commits are missing from qcom-next and kernel-topics branches
  • This is unusual for QCLINUX: commits, which typically land in qcom-next before PR submission
  • Recommendation: Verify these commits are intended for direct merge, or ensure they land in qcom-next first

Verdict

⚠️ PARTIAL - Commits are well-formed vendor-only changes with proper QCLINUX: prefix and clear commit messages. However, both commits are missing from qcom-next/topics, which requires verification that direct merge is intended.


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 changes, 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)

Note: The integration presence failure is the primary concern. QCLINUX: commits typically land in qcom-next before being submitted via PR. Confirm with the submitter whether these commits should be in qcom-next first, or if direct merge to the target branch is intentional.

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/42814711370

Checker Result Summary
Checker Result Summary
checkpatch ❌ 41 warnings: undocumented DT compatible string qcom,cam-gmsl-sensor
dt-binding-check ⏭️ No binding changes
dtb-check ❌ Build failure: missing lemans-draco-evk.dtb dependency; graph_port errors
sparse-check ⏭️ No C/H changes
check-uapi-headers ⏭️ No C/H changes
check-patch-compliance ❌ QCLINUX: prefix not accepted (known limitation)
tag-check ❌ QCLINUX: prefix not valid for qcom-6.18.y branch

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/42814711370

Checker Result Summary
checkpatch ❌ 41 warnings: undocumented DT compatible string qcom,cam-gmsl-sensor
dt-binding-check ⏭️ No binding changes
dtb-check ❌ Build failure: missing lemans-draco-evk.dtb dependency; graph_port errors
sparse-check ⏭️ No C/H changes
check-uapi-headers ⏭️ No C/H changes
check-patch-compliance ❌ QCLINUX: prefix not accepted (known limitation)
tag-check ❌ QCLINUX: prefix not valid for qcom-6.18.y branch

❌ checkpatch

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

Failure details:

Commit 3f9145724b38 ("QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577")
WARNING: DT compatible string "qcom,cam-gmsl-sensor" appears un-documented -- check ./Documentation/devicetree/bindings/
#91: FILE: arch/arm64/boot/dts/qcom/lemans-draco-evk-camera-sensor.dtsi:77:
+		compatible = "qcom,cam-gmsl-sensor";
[... 24 more identical warnings across both commits ...]
3f9145724b38 total: 0 errors, 25 warnings, 0 checks, 967 lines checked
16952e145aff total: 0 errors, 16 warnings, 0 checks, 496 lines checked

Fix: Add a DT binding YAML for qcom,cam-gmsl-sensor:

# Create Documentation/devicetree/bindings/media/qcom,cam-gmsl-sensor.yaml
# with properties: compatible, reg, clocks, etc.
# Then rebase and amend both commits

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 28d4ebb856739c854af1ef40d7745714ae1befd0..20af74b31142df8f0a9520c0b924b8207cf7c460

❌ dtb-check

Root cause: The Makefile references lemans-draco-evk.dtb as a dependency for composite DTB targets, but this base DTB file 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.

Additionally, the log shows graph_port warnings for all camera deserializer port nodes:

lemans-camera-sensor.dtsi:40.10-46.5: Warning (graph_port): port@0: graph node '#address-cells' is -1, must be 1
lemans-camera-sensor.dtsi:40.10-46.5: Warning (graph_port): port@0: graph node '#size-cells' is -1, must be 0
lemans-camera-sensor.dtsi:56.10-62.5: Warning (graph_port): port@2: graph node unit address error, expected "0"
lemans-camera-sensor.dtsi:64.10-70.5: Warning (graph_port): port@3: graph node unit address error, expected "1"
[... repeated for all 4 deserializers ...]

Fix:

  1. Missing base DTB: Either:

    • Add lemans-draco-evk.dts to the tree, or
    • Remove the composite DTB targets from the Makefile if they're not needed yet
  2. graph_port errors: Add #address-cells and #size-cells to each ports parent node, and renumber port unit addresses sequentially from 0:

    ports {
        #address-cells = <1>;
        #size-cells = <0>;
        
        port@0 { reg = <0>; ... };
        port@1 { reg = <1>; ... };
        port@2 { reg = <2>; ... };  // not port@2 expecting "0"
        port@3 { reg = <3>; ... };  // not port@3 expecting "1"
    };
    

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 Cameras Current device tree doesn't have support for GMSL cameras on Lemans Draco platform.
Commit summary does not start with a required prefix

Fix: This is a known checker limitation — QCLINUX: is a valid vendor-internal prefix but not accepted by check-patch-compliance. If these patches are vendor-only with no upstream equivalent, the checker will always fail. No patch change can fix this.

If the patches have been posted upstream, change the prefix to FROMLIST: and add a Link: trailer pointing to the lore.kernel.org URL.


❌ tag-check

Root cause: The PR targets qcom-6.18.y, which is not qcom-next or qcom-next-staging. All branches except those two require every commit subject to start with a valid prefix tag. The QCLINUX: prefix is valid for vendor-only commits, but the tag-check enforces a stricter policy than check-patch-compliance.

Failure details:
Both commits use QCLINUX: prefix:

  • Commit 3f91457: QCLINUX: arm64: dts: qcom: lemans: Add camera sensor nodes for imx858, ov13b10 and imx577
  • Commit 16952e1: QCLINUX: arm64: dts: qcom: lemans: Add changes for OX03F10 GMSL Cameras ...

Analysis: The QCLINUX: prefix is one of the valid prefixes for the tag-check (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, WORKAROUND:). However, the check-patch-compliance checker rejects it because it only accepts upstream-linkable prefixes.

Verdict: ✅ tag-check PASS — both commits have a valid prefix tag (QCLINUX:). The failure is only in check-patch-compliance, which is a known limitation for vendor-only commits.


Verdict

3 blockers must be fixed before merge:

  1. checkpatch: Add DT binding YAML for qcom,cam-gmsl-sensor to eliminate 41 warnings
  2. dtb-check: Fix missing lemans-draco-evk.dtb dependency and graph_port errors (add #address-cells/#size-cells to ports nodes, renumber port unit addresses)
  3. check-patch-compliance: Known limitation for QCLINUX: prefix — cannot be fixed unless patches are posted upstream (then use FROMLIST: + Link:)

The check-patch-compliance failure is a known checker limitation for vendor-only commits and may be acceptable if these patches are not intended for upstream submission. However, the checkpatch and dtb-check failures are genuine issues that must be resolved.

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #1375

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

# 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
2 No rule to make target 'lemans-draco-evk-el2.dtb' arch/arm64/boot/dts/qcom/Makefile:489 Yes Makefile references non-existent EL2 DTB file

Verdict

Both errors are introduced by this PR. The PR adds Makefile entries that depend on lemans-draco-evk.dtb and lemans-draco-evk-el2.dtb, but these base device tree files do not exist in the PR.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #1375

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

# Error File:Line PR-introduced? Root Cause
1 No rule to make target 'arch/arm64/boot/dts/qcom/lemans-draco-evk.dtb' arch/arm64/boot/dts/qcom/Makefile:481 Yes Makefile references lemans-draco-evk.dtb and lemans-draco-evk-el2.dtb as dependencies, but these base DTB source files do not exist in the tree

Verdict

1 of 1 errors is introduced by this PR. The PR adds Makefile entries for composite DTBs that depend on non-existent base DTB files.

📎 Detailed analysis: Full report

sushilsingh045 and others added 2 commits November 19, 2026 17:18
…raco EVK

The Lemans Draco EVK provides four CSI ports. Assign a sensor configuration
to each CSI port so the device tree represents the board’s camera
connectivity and enables camera support for the IMX858, OV13B10, and
IMX577 sensors.

Add the camera DT changes for the four CSI ports accordingly.

Signed-off-by: Sushil Pratap Singh <sussin@qti.qualcomm.com>
Current device tree doesn't have support for GMSL cameras on
Lemans Draco platform.

Add the required Device Tree nodes and ports to support
up to sixteen OX03F10 cameras across four GMSL ports.

Signed-off-by: Tharik Anwar <tharanwa@qti.qualcomm.com>
@tharanwa
tharanwa force-pushed the qli_2_0_camera_lemans_draco branch from b5366bc to cb3c55f Compare November 19, 2026 12:09
@tharanwa
tharanwa marked this pull request as ready for review November 19, 2026 13:02
@tharanwa

Copy link
Copy Markdown
Author

Dependent on the PR 1040!.

@qcomlnxci

Copy link
Copy Markdown

Test results

Workflow run: 44533297179 attempt 1

Known failures configured: 54

Target Pass Non-pass Total
kbdev-hamoa-iot-evk-multimedia 29 7 36
kbdev-lemans-evk-multimedia 33 3 36
kbdev-monaco-evk-multimedia 33 3 36
kbdev-purwa-iot-evk-multimedia 29 7 36
kbdev-qcs615-ride-multimedia 28 8 36
kbdev-qcs6490-rb3gen2-multimedia 32 4 36
kbdev-qcs8300-ride-multimedia 30 6 36
kbdev-qcs9100-ride-r3-multimedia 29 7 36
kbdev-qrb2210-rb1-multimedia - ⛔ Not submitted -
kbdev-shikra-iqs-evk-multimedia 21 15 36

Test Matrix

Test Case kbdev-hamoa-iot-evk-multimedia kbdev-lemans-evk-multimedia kbdev-monaco-evk-multimedia kbdev-purwa-iot-evk-multimedia kbdev-qcs615-ride-multimedia kbdev-qcs6490-rb3gen2-multimedia kbdev-qcs8300-ride-multimedia kbdev-qcs9100-ride-r3-multimedia kbdev-qrb2210-rb1-multimedia kbdev-shikra-iqs-evk-multimedia
LAVA result ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ✅ Results ⛔ Not submitted ✅ Results
Audio_Card_Registration ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⚠️ skip ✅ Pass ⚠️ skip ⚠️ skip ⛔ Not submitted ⚠️ skip
BT_FW_KMD_Service ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
BT_ON_OFF ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
BT_SCAN ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
CPUFreq_Validation ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
CPU_affinity ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
DSP_AudioPD ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
Ethernet_Basic_Validation ⚠️ skip ⚠️ skip ✅ Pass ⚠️ skip ⚠️ skip ⚠️ skip ⚠️ skip ❌ Fail ⛔ Not submitted ❌ Fail
Freq_Scaling ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
GIC ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
IPA ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Interrupts ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
KVM_Driver ❌ Fail ✅ Pass ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
KVM_EL2_DTB ❌ Fail ✅ Pass ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
KVM_Infra ❌ Fail ✅ Pass ✅ Pass ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
OpenCV ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
PCIe ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
Probe_Failure_Check ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail ⛔ Not submitted ❌ Fail
RMNET ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
UFS_Validation ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
USBHost ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⚠️ skip ✅ Pass ✅ Pass ⛔ Not submitted ❌ Fail
WiFi_Firmware_Driver ✅ Pass ✅ Pass ❌ Fail ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
WiFi_OnOff ✅ Pass ✅ Pass ❌ Fail ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
adsp_remoteproc ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
cdsp_remoteproc ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
gpdsp_remoteproc ⚠️ skip ✅ Pass ✅ Pass ⚠️ skip ⚠️ skip ⚠️ skip ✅ Pass ✅ Pass ⛔ Not submitted ⚠️ skip
hotplug ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
irq ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
kaslr ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
pinctrl ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
qcom_hwrng ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
rngtest ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
shmbridge ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
smmu ❌ Fail ❌ Fail ✅ Pass ❌ Fail ❌ Fail ✅ Pass ✅ Pass ❌ Fail ⛔ Not submitted ✅ Pass
watchdog ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
wpss_remoteproc ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass ⛔ Not submitted ✅ Pass
Failure summary

Known failures

  • kbdev-hamoa-iot-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-hamoa-iot-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-hamoa-iot-evk-multimedia: smmu => fail.
  • kbdev-hamoa-iot-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-hamoa-iot-evk-multimedia: KVM_Driver => fail.
  • kbdev-hamoa-iot-evk-multimedia: KVM_EL2_DTB => fail.
  • kbdev-hamoa-iot-evk-multimedia: KVM_Infra => fail.
  • kbdev-lemans-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-lemans-evk-multimedia: smmu => fail.
  • kbdev-lemans-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-monaco-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-monaco-evk-multimedia: WiFi_Firmware_Driver => fail.
  • kbdev-monaco-evk-multimedia: WiFi_OnOff => fail.
  • kbdev-purwa-iot-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-purwa-iot-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-purwa-iot-evk-multimedia: smmu => fail.
  • kbdev-purwa-iot-evk-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-purwa-iot-evk-multimedia: KVM_Driver => fail.
  • kbdev-purwa-iot-evk-multimedia: KVM_EL2_DTB => fail.
  • kbdev-purwa-iot-evk-multimedia: KVM_Infra => fail.
  • kbdev-qcs615-ride-multimedia: gpdsp_remoteproc => skip.
  • kbdev-qcs615-ride-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs615-ride-multimedia: smmu => fail.
  • kbdev-qcs615-ride-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs615-ride-multimedia: Audio_Card_Registration => skip.
  • kbdev-qcs615-ride-multimedia: KVM_Driver => fail.
  • kbdev-qcs615-ride-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs615-ride-multimedia: KVM_Infra => fail.
  • kbdev-qcs6490-rb3gen2-multimedia: gpdsp_remoteproc => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs6490-rb3gen2-multimedia: USBHost => skip.
  • kbdev-qcs6490-rb3gen2-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs8300-ride-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs8300-ride-multimedia: Ethernet_Basic_Validation => skip.
  • kbdev-qcs8300-ride-multimedia: Audio_Card_Registration => skip.
  • kbdev-qcs8300-ride-multimedia: KVM_Driver => fail.
  • kbdev-qcs8300-ride-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs8300-ride-multimedia: KVM_Infra => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Probe_Failure_Check => fail.
  • kbdev-qcs9100-ride-r3-multimedia: smmu => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Ethernet_Basic_Validation => fail.
  • kbdev-qcs9100-ride-r3-multimedia: Audio_Card_Registration => skip.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_Driver => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_EL2_DTB => fail.
  • kbdev-qcs9100-ride-r3-multimedia: KVM_Infra => fail.
  • kbdev-shikra-iqs-evk-multimedia: adsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: gpdsp_remoteproc => skip.
  • kbdev-shikra-iqs-evk-multimedia: GIC => fail.
  • kbdev-shikra-iqs-evk-multimedia: Probe_Failure_Check => fail.
  • kbdev-shikra-iqs-evk-multimedia: UFS_Validation => skip.
  • kbdev-shikra-iqs-evk-multimedia: PCIe => fail.
  • kbdev-shikra-iqs-evk-multimedia: USBHost => fail.
  • kbdev-shikra-iqs-evk-multimedia: Ethernet_Basic_Validation => fail.
  • kbdev-shikra-iqs-evk-multimedia: WiFi_OnOff => skip.
  • kbdev-shikra-iqs-evk-multimedia: DSP_AudioPD => skip.
  • kbdev-shikra-iqs-evk-multimedia: Audio_Card_Registration => skip.
  • kbdev-shikra-iqs-evk-multimedia: KVM_Driver => fail.
  • kbdev-shikra-iqs-evk-multimedia: KVM_EL2_DTB => fail.
  • kbdev-shikra-iqs-evk-multimedia: KVM_Infra => fail.

Unexpected failures

  • kbdev-qrb2210-rb1-multimedia did not produce a LAVA result artifact.
  • kbdev-shikra-iqs-evk-multimedia: BT_SCAN => fail.

Result: blocked because unexpected failures were found.

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.

6 participants