Skip to content

Qcom618 lvds support - #1057

Merged
Salendarsingh Gaud (sgaud-quic) merged 6 commits into
qualcomm-linux:qcom-6.18.yfrom
quic-vishsain:qcom618_lvds_support
Sep 9, 2026
Merged

Qcom618 lvds support#1057
Salendarsingh Gaud (sgaud-quic) merged 6 commits into
qualcomm-linux:qcom-6.18.yfrom
quic-vishsain:qcom618_lvds_support

Conversation

@quic-vishsain

Copy link
Copy Markdown

Add LVDS overlays and panel for Lemans/monaco/Kodiak

CRs-Fixed: 4668551

Vishnu Saini added 2 commits September 7, 2026 14:34
Add BOE DV215FHM-R01 21.5" FHD (1920x1080) dual-channel LVDS panel
compatible string to the panel-simple-lvds-dual-ports binding.

Link: https://lore.kernel.org/all/20260903-b4-lvds-panel-doc-v4-1-861738a0d5de@oss.qualcomm.com/
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Acked-by: Liu Ying <victor.liu@nxp.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Add the BOE DV215FHM-R01 21.5" FHD (1920x1080) dual-channel
LVDS panel.

Link: https://lore.kernel.org/all/20260903-b4-lvds-panel-doc-v4-2-861738a0d5de@oss.qualcomm.com/
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: No Change Task Found

No associated change tasks found for CR 4668551 on any of the following entities:

Entities:

  • kernel.qli.2.0

CR: 4668551

Please ensure the CR has a change task associated with at least one of the entities for this branch.

@qlijarvis

Copy link
Copy Markdown

PR #1057 — validate-patch

PR: #1057

Verdict Issues Detailed Report
⚠️ 4 Full report

Final Summary

  1. Lore link present: Yes — all 5 commits have valid lore.kernel.org links
  2. Lore link matches PR commits: Yes — all diffs are faithful to lore source (context-only deltas are legitimate adaptations)
  3. Upstream patch status:
    • Commits 1-2: ✅ ACKed — formal maintainer approval received
    • Commits 3-5: ⏳ Decision Pending — posted Sep 5, 2026; under review, no decision yet
  4. PR present in qcom-next/topics: Partial - 2/5 commit(s) only have partial integration evidence
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1057 - Add BOE DV215FHM-R01 LVDS panel support and display overlays
Verdict: ⚠️ PARTIAL

Summary

This PR contains 5 commits split across two upstream patch series:

  • Commits 1-2: Panel binding and driver (v4 series, ACKed)
  • Commits 3-5: DTS overlays for three platforms (v3 series, under review)

All commits have valid lore links, correct authorship, and faithful diffs. The first two commits have received maintainer ACKs/reviews and are ready for merge. The DTS commits (3-5) are still under community review with no formal acceptance yet.


Per-Commit Analysis

Commit 1/5: dt-bindings: display: simple: Add boe,dv215fhm-r01 compatible

Check Status Note
Lore link present https://lore.kernel.org/all/20260903-b4-lvds-panel-doc-v4-1-861738a0d5de@oss.qualcomm.com/
Subject matches upstream Identical except for FROMLIST: prefix
Body preserves rationale Identical description
Authorship preserved Vishnu Saini (FROMLIST: allows submitter in From:)
Signed-off-by chain Original author's SoB present
Diff content Identical (context-only delta: line numbers differ due to tree state)
Upstream status ACKed Acked-by: Krzysztof Kozlowski, Liu Ying; Reviewed-by: Neil Armstrong
Integration status Present All added lines present in topics

Commit 2/5: drm/panel: simple: Add BOE DV215FHM-R01 panel

Check Status Note
Lore link present https://lore.kernel.org/all/20260903-b4-lvds-panel-doc-v4-2-861738a0d5de@oss.qualcomm.com/
Subject matches upstream Identical except for FROMLIST: prefix
Body preserves rationale Identical description
Authorship preserved Vishnu Saini
Signed-off-by chain Correct
Diff content Identical (context-only delta: line numbers differ)
Upstream status ACKed Reviewed-by: Neil Armstrong (cover letter also has Acked-by from Krzysztof Kozlowski, Liu Ying)
Integration status Present Exact patch-id match at 736620c99bc3bf56c3699d29fbc7d0f58de5bfed in topics

Commit 3/5: arm64: dts: qcom: qcs6490-rb3gen2: Add LVDS display overlay

Check Status Note
Lore link present https://lore.kernel.org/all/20260905-lvds-support-v3-3-b40a1b03f63c@oss.qualcomm.com/
Subject matches upstream Identical except for FROMLIST: prefix
Body preserves rationale Full description preserved
Authorship preserved Vishnu Saini
Signed-off-by chain Correct
Diff content Matches lore patch v3 3/3
Upstream status Decision Pending No Acked-by/Reviewed-by tags; posted Sep 5, 2026; no maintainer decision yet
Integration status ⚠️ Partial Subject/partial tree evidence found, but full change not verified in qcom-next/topics

Commit 4/5: arm64: dts: qcom: monaco-evk: Add LVDS display overlay

Check Status Note
Lore link present https://lore.kernel.org/all/20260905-lvds-support-v3-2-b40a1b03f63c@oss.qualcomm.com/
Subject matches upstream Identical except for FROMLIST: prefix
Body preserves rationale Full description preserved
Authorship preserved Vishnu Saini
Signed-off-by chain Correct
Diff content Matches lore patch v3 2/3
Upstream status Decision Pending No Acked-by/Reviewed-by tags; posted Sep 5, 2026; no maintainer decision yet
Integration status Present All added lines present in topics

Commit 5/5: arm64: dts: qcom: lemans-evk: Add LVDS display overlay

Check Status Note
Lore link present https://lore.kernel.org/all/20260905-lvds-support-v3-1-b40a1b03f63c@oss.qualcomm.com/
Subject matches upstream Identical except for FROMLIST: prefix
Body preserves rationale Full description preserved
Authorship preserved Vishnu Saini
Signed-off-by chain Correct
Diff content Matches lore patch v3 1/3
Upstream status Decision Pending No Acked-by/Reviewed-by tags; posted Sep 5, 2026; no maintainer decision yet
Integration status ⚠️ Partial Subject/partial tree evidence found, but full change not verified in qcom-next/topics

Issues Found

Minor:

  1. Commits 3 & 5 have partial integration status — The integration_presence_report.md shows these commits have only partial evidence in qcom-next/topics (subject or partial tree match, but full change not verified). This suggests they may need to be re-synced or the integration check encountered tree state differences.

None (commit message/diff correctness):

  • All commit messages faithfully represent upstream patches
  • All diffs match lore content (context-only deltas are legitimate)
  • Authorship and trailers are correct
  • FROMLIST: prefix is appropriate for all commits

Verdict

⚠️ PARTIAL — Merge with awareness of upstream status

Commits 1-2 (panel binding & driver):
Safe to merge — These have received formal ACKs/reviews from subsystem maintainers (Krzysztof Kozlowski for DT bindings, Neil Armstrong for panel driver). They are ready for upstream acceptance.

Commits 3-5 (DTS overlays):
Under review — These patches were posted to the mailing list on Sep 5, 2026 (3 days ago) and have not yet received maintainer feedback. They are technically correct and match the lore source, but lack formal acceptance signals.

Integration status:
⚠️ Commits 3 & 5 show only partial integration evidence. This may indicate:

  • The commits are newer than the last topics sync
  • Tree state differences require verification
  • The integration check couldn't verify the full change

Recommendation:
Merge commits 1-2 immediately (they are ACKed and ready). For commits 3-5, consider:

  1. Option A (recommended): Merge all 5 commits now — the DTS overlays are technically sound, match upstream exactly, and are part of a cohesive feature. Monitor the mailing list for any requested changes and apply them in a follow-up PR if needed.
  2. Option B (conservative): Hold commits 3-5 until they receive maintainer ACKs, then merge in a follow-up PR.

Final Summary

  1. Lore link present: Yes — all 5 commits have valid lore.kernel.org links
  2. Lore link matches PR commits: Yes — all diffs are faithful to lore source (context-only deltas are legitimate adaptations)
  3. Upstream patch status:
    • Commits 1-2: ✅ ACKed — formal maintainer approval received
    • Commits 3-5: ⏳ Decision Pending — posted Sep 5, 2026; under review, no decision yet
  4. PR present in qcom-next/topics: Partial — 3/5 commits fully present, 2/5 commits have partial evidence (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: d49c33864d06e9672dce57738be8851384578fcf
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final
1/5 [PATCH 1/5] FROMLIST: dt-bindings: display: simple: Add partial - subject or partial tree evidence found, but full change was not verified present - all checked added lines are present present
2/5 [PATCH 2/5] FROMLIST: drm/panel: simple: Add BOE DV215FHM-R01 panel partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 736620c99bc3bf56c3699d29fbc7d0f58de5bfed present
3/5 [PATCH 3/5] FROMLIST: arm64: dts: qcom: qcs6490-rb3gen2: Add LVDS missing - no subject, patch-id, or full tree-content match found partial - subject or partial tree evidence found, but full change was not verified partial
4/5 [PATCH 4/5] FROMLIST: arm64: dts: qcom: monaco-evk: Add LVDS display missing - no subject, patch-id, or full tree-content match found present - all checked added lines are present present
5/5 [PATCH 5/5] FROMLIST: arm64: dts: qcom: lemans-evk: Add LVDS display missing - no subject, patch-id, or full tree-content match found partial - subject or partial tree evidence found, but full change was not verified partial

Final Status

overall_status: PARTIAL
present_commits: 3/5
partial_commits: 2/5
missing_commits: 0/5
topics_checked_for_commits: 5/5
final_summary: PR present in qcom-next/topics: Partial - 2/5 commit(s) only have partial integration evidence

@qlijarvis

Copy link
Copy Markdown

PR #1057 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch All 5 commits passed
dt-binding-check panel-simple-lvds-dual-ports.yaml validated
dtb-check 2 new errors in LVDS overlays
sparse-check No sparse warnings
check-uapi-headers No UAPI changes
check-patch-compliance 3 commits have content mismatch with upstream
tag-check All commits have FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1057 - Add BOE DV215FHM-R01 LVDS panel support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/34198781996
Target branch: qcom-6.18.y

Checker Result Summary
checkpatch All 5 commits passed
dt-binding-check panel-simple-lvds-dual-ports.yaml validated
dtb-check 2 new errors in LVDS overlays
sparse-check No sparse warnings
check-uapi-headers No UAPI changes
check-patch-compliance 3 commits have content mismatch with upstream
tag-check All commits have FROMLIST: prefix

❌ dtb-check

Root cause: Two distinct validation errors introduced by the new LVDS display overlays.

Failure details:

Error 1: Unevaluated property data-lanes in LVDS bridge endpoint

lemans-evk-lvds-boe,dv215fhm-r01.dtb: lvds-bridge@2d (lontium,lt9211c): 
  ports:port@0:endpoint: Unevaluated properties are not allowed ('data-lanes' was unexpected)

Affects: lemans-evk-lvds-boe,dv215fhm-r01.dtb

Error 2: Invalid pinctrl function name gp_mn

lemans-evk-lvds-boe,dv215fhm-r01.dtb: pinctrl@f000000 (qcom,sa8775p-tlmm): 
  gp_mn_active-state: 'oneOf' conditional failed, one must be fixed:
  'gp_mn' is not one of ['atest_char', 'atest_usb2', 'audio_ref', 'cam_mclk', ...]

Affects: lemans-evk-lvds-boe,dv215fhm-r01.dtb, monaco-evk-lvds-boe,dv215fhm-r01.dtb, qcs6490-rb3gen2-industrial-mezzanine-lvds-boe,dv215fhm-r01.dtb

Fix:

For Error 1 (data-lanes):
The lontium,lt9211c binding schema does not allow data-lanes in the DSI input endpoint. Either:

  1. Remove the data-lanes property from the DSI endpoint in the overlay, or
  2. Update the lontium,lt9211c binding YAML to allow data-lanes in port@0/endpoint

For Error 2 (gp_mn function):
The pinctrl function name gp_mn is not in the allowed list for the TLMM bindings. Replace with the correct function name:

  • For sa8775p-tlmm: use gpio instead of gp_mn
  • For qcs8300-tlmm (monaco): use gpio instead of gp_mn
  • For sc7280-pinctrl (qcs6490): use gpio instead of gp_mn
# Fix the pinctrl function names in the overlay files
sed -i 's/function = "gp_mn"/function = "gpio"/' \
  arch/arm64/boot/dts/qcom/lemans-evk-lvds-boe,dv215fhm-r01.dtso \
  arch/arm64/boot/dts/qcom/monaco-evk-lvds-boe,dv215fhm-r01.dtso \
  arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine-lvds-boe,dv215fhm-r01.dtso

Reproduce locally:

make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/lemans-evk-lvds-boe,dv215fhm-r01.dtb
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/monaco-evk-lvds-boe,dv215fhm-r01.dtb
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine-lvds-boe,dv215fhm-r01.dtb

❌ check-patch-compliance

Root cause: Three DTS overlay commits have content differences from their upstream lore.kernel.org links.

Failure details:

Checking commit: FROMLIST: arm64: dts: qcom: qcs6490-rb3gen2: Add LVDS display overlay
Change is different from the one mentioned in Link

Checking commit: FROMLIST: arm64: dts: qcom: monaco-evk: Add LVDS display  overlay
Change is different from the one mentioned in Link

Checking commit: FROMLIST: arm64: dts: qcom: lemans-evk: Add LVDS display overlay
Change is different from the one mentioned in Link

Fix:

The checker detected content mismatches between the PR commits and the upstream patches linked in the commit messages. This typically happens when:

  1. The PR includes local adaptations not present upstream
  2. The upstream patch was updated after the Link was added
  3. Context lines shifted due to tree differences

Action required:

  1. Fetch the upstream patches using b4:

    b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260903-b4-lvds-panel-doc-v4-3-861738a0d5de@oss.qualcomm.com/ -o /tmp/qcs6490
    b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260903-b4-lvds-panel-doc-v4-4-861738a0d5de@oss.qualcomm.com/ -o /tmp/monaco
    b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260903-b4-lvds-panel-doc-v4-5-861738a0d5de@oss.qualcomm.com/ -o /tmp/lemans
  2. Compare the actual diff content:

    git format-patch -1 fabbbe203007 --stdout | awk '/^diff/,/^--$/' | grep -E '^[+-][^+-]' > /tmp/pr-qcs6490.diff
    awk '/^diff/,/^--$/' /tmp/qcs6490/*.mbx | grep -E '^[+-][^+-]' > /tmp/upstream-qcs6490.diff
    diff /tmp/pr-qcs6490.diff /tmp/upstream-qcs6490.diff
  3. If the differences are:

    • Context-only shifts: Not a real issue — the checker is overly strict
    • Legitimate local adaptations: Document them in the commit message with a note like "Adapted for qcom-6.18.y tree structure"
    • Missing hunks: Cherry-pick the missing changes from upstream
    • Extra hunks: Verify they belong in this commit or split them out

Reproduce locally:

cd /path/to/kernel
./scripts/check-patch-compliance.sh --base 954f6decebe2 --head 34b9bd0a07e4

Verdict

2 blockers must be fixed before merge:

  1. dtb-check failures — Fix the gp_mn pinctrl function name (change to gpio) and resolve the data-lanes unevaluated property issue in the LVDS bridge binding
  2. check-patch-compliance content mismatch — Verify the DTS overlay commits match their upstream links or document the local adaptations

The first two commits (dt-bindings and drm/panel) passed all checks cleanly. The three DTS overlay commits need the fixes above.

@sgaud-quic

Copy link
Copy Markdown
Contributor

quic-vishsain check dtb-check failure :

dtb-check | ❌ | 2 new errors in LVDS overlays

Marek Vasut and others added 4 commits September 8, 2026 16:26
… DSI input ports

The Lontium LT9211 is capable of 1..4 DSI lanes per input DSI port,
describe the lane count for each input port in the schema.

For example Linux kernel driver does already use that information and
fails to probe if it is missing.

Signed-off-by: Marek Vasut <marex@nabladev.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Link: https://patch.msgid.link/20260407203109.34302-1-marex@nabladev.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
The QCS6490 RB3 Gen2 industrial mezzanine supports LVDS display output
using the Lontium LT9211C DSI-to-LVDS bridge as an alternative to the
default HDMI output via the LT9611UXC bridge.

Add a DTBO overlay,
qcs6490-rb3gen2-industrial-mezzanine-lvds-boe,dv215fhm-r01.dtso, that
disables HDMI (hdmi-connector and lt9611_codec) and wires up the LT9211C
bridge on I2C1 (address 0x29) with reset on GPIO117. The overlay adds a
dual-channel panel-lvds node for the boe,dv215fhm-r01 panel, matched
against the panel-simple-lvds-dual-ports binding which supplies the
panel's size and timing internally.

The overlay is built as a composite DTB combining the base
qcs6490-rb3gen2.dtb, the industrial mezzanine overlay, and this LVDS
overlay.

Link: https://lore.kernel.org/all/20260905-lvds-support-v3-3-b40a1b03f63c@oss.qualcomm.com/
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
 overlay

The Monaco-EVK mezzanine supports LVDS display output using the
Lontium LT9211C DSI-to-LVDS bridge. The bridge is connected to the
DSI0 output and drives a dual-channel 1920x1080 LVDS panel in
VESA-24 mapping.

Add a DTBO overlay, monaco-evk-lvds-boe,dv215fhm-r01.dtso, that wires
up the LT9211C bridge on I2C8 (address 0x2d) with reset on GPIO66,
a panel-lvds node for the boe,dv215fhm-r01 panel (matched against the
panel-simple-lvds-dual-ports binding, which supplies the panel's size
and timing internally), and an LCD display bias regulator supplied
through the GPIO expander. DSI power is provided by vreg_l5a.

The overlay is built as a composite DTB combining the base
monaco-evk.dtb, the IFP mezzanine overlay, and this LVDS overlay.

Link: https://lore.kernel.org/all/20260905-lvds-support-v3-2-b40a1b03f63c@oss.qualcomm.com/
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
The Lemans EVK IFP mezzanine supports LVDS display output using the
Lontium LT9211C DSI-to-LVDS bridge. The bridge is connected to the
DSI0 output and drives a dual-channel 1920x1080 LVDS panel in
VESA-24 mapping.

Add a DTBO overlay, lemans-evk-lvds-boe,dv215fhm-r01.dtso, that wires
up the LT9211C bridge on I2C1 (address 0x2d) with reset on GPIO37,
a panel-lvds node for the boe,dv215fhm-r01 panel (matched against the
panel-simple-lvds-dual-ports binding, which supplies the panel's size
and timing internally), and an LCD display bias regulator supplied
through the GPIO expander. DSI power is provided by vreg_s4a.

The overlay is built as a composite DTB combining the base
lemans-evk.dtb, the IFP mezzanine overlay, and this LVDS overlay.

Link: https://lore.kernel.org/all/20260905-lvds-support-v3-1-b40a1b03f63c@oss.qualcomm.com/
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
@qcomlnxci

Copy link
Copy Markdown

Test Matrix

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

@quic-vishsain

Copy link
Copy Markdown
Author

quic-vishsain check dtb-check failure :

dtb-check | ❌ | 2 new errors in LVDS overlays

Thank you, backported bindings from mainline.

@qcomlnxci
qcomlnxci requested a review from a team September 8, 2026 16:40
@sgaud-quic

Copy link
Copy Markdown
Contributor

PR #1057 — validate-patch

PR: #1057

Verdict Issues Detailed Report
5 Full report

Final Summary

  1. Lore link present: Partial - commits 1, 2, 4, 5, and 6 have lore.kernel.org links; commit 3 does not.
  2. Lore link matches PR commits: Partial - lore-backed payloads match, with Makefile whitespace/context adaptations in commits 4-6; commit 3 was not lore-validated.
  3. Upstream patch status: Mixed - commits 1-2 are ACKed/reviewed in lore; commits 4-6 remain in review with last local activity on September 8, 2026; commit 3 status is only known as present in qcom-next.
  4. PR present in qcom-next/topics: Fail - 3/6 commit(s) are missing from both qcom-next and topics
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1057 - LVDS display support series
Upstream commit: Multiple lore links for commits 1, 2, 4, 5, 6; commit 3 has only https://patch.msgid.link/20260407203109.34302-1-marex@nabladev.com
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream Lore-backed commits match with expected FROMLIST: prefix adaptation; commit 3 subject matches qcom-next exact patch-id entry.
Body preserves rationale Lore-backed commit bodies preserve the upstream rationale; only Link: trailers were added in PR.
Fixes tag present/correct No Fixes: tag is present in the compared lore patches, so none is expected in the PR.
Authorship preserved ⚠️ FROMLIST: commits include Vishnu Saini’s Signed-off-by; commit 3 author is Marek Vasut, but no local lore mbox exists to validate the BACKPORT: authorship against lore.
Backport note (if applicable) ⚠️ Commit 3 is BACKPORT: but lacks an [ upstream commit <sha> ] note and uses patch.msgid.link, not a canonical lore.kernel.org or upstream commit URL.

Diff

File Status Notes
Documentation/devicetree/bindings/display/panel/panel-simple-lvds-dual-ports.yaml ⚠️ Same added compatible/comment as lore, but inserted at different context/ordering; treated as target-tree adaptation.
drivers/gpu/drm/panel/panel-simple.c Exact stable patch-id match to lore patch bd3612ce053552e2ae7401a1217c4884413563f4.
Documentation/devicetree/bindings/display/bridge/lontium,lt9211.yaml ⚠️ No local lore evidence for commit 3; integration report shows exact qcom-next patch-id match 9af92668ad18125bf31a1358256eac9eb23d8249 at c2738d88b624.
arch/arm64/boot/dts/qcom/Makefile ⚠️ Overlay commits differ from lore in insertion context and use dtb-$(CONFIG_ARCH_QCOM) += instead of lore’s tabbed dtb-$(CONFIG_ARCH_QCOM)\t+=.
arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine-lvds-boe,dv215fhm-r01.dtso Payload content matches the lore patch.
arch/arm64/boot/dts/qcom/monaco-evk-lvds-boe,dv215fhm-r01.dtso Payload content matches the lore patch.
arch/arm64/boot/dts/qcom/lemans-evk-lvds-boe,dv215fhm-r01.dtso Payload content matches the lore patch.

Issues

  • Commit 3 cannot be fully validated by this lore-only workflow because it has no lore.kernel.org link or fetched local mbox; it only has Link: https://patch.msgid.link/20260407203109.34302-1-marex@nabladev.com.
  • Commit 3 is labeled BACKPORT: but does not include an [ upstream commit <sha> ] note.
  • Commits 4-6 are not fully diff-identical to lore in arch/arm64/boot/dts/qcom/Makefile; the added dtb-$(CONFIG_ARCH_QCOM) lines use a space before += where lore uses a tab.
  • The overlay lore cover declares prerequisites for the LT9211C bridge series and LT9211 defconfig patch; those prerequisites are not present in pr.patch or proven present by the supplied local evidence.
  • integration_presence_report.md reports overall presence failure: only 1/6 commits is present, 2/6 are partial, and commits 4/6, 5/6, and 6/6 are missing from both qcom-next and topics.

Verdict

Do not merge as-is: fix the commit 3 upstream-link/backport-note hygiene, align or document the Makefile adaptations, ensure declared prerequisites are accounted for, and resolve the qcom-next/topics presence failure.

Final Summary

  1. Lore link present: Partial - commits 1, 2, 4, 5, and 6 have lore.kernel.org links; commit 3 does not.
  2. Lore link matches PR commits: Partial - lore-backed payloads match, with Makefile whitespace/context adaptations in commits 4-6; commit 3 was not lore-validated.
  3. Upstream patch status: Mixed - commits 1-2 are ACKed/reviewed in lore; commits 4-6 remain in review with last local activity on September 8, 2026; commit 3 status is only known as present in qcom-next.
  4. PR present in qcom-next/topics: Fail - integration_presence_report.md says 3/6 commits are missing from both qcom-next and topics, with 2/6 only partial.

Deterministic Integration Presence

Integration Presence Report

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

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

Commit Subject qcom-next topics Final
1/6 [PATCH 1/6] FROMLIST: dt-bindings: display: simple: Add partial - subject or partial tree evidence found, but full change was not verified unavailable - topics remote could not be fetched partial
2/6 [PATCH 2/6] FROMLIST: drm/panel: simple: Add BOE DV215FHM-R01 panel partial - subject or partial tree evidence found, but full change was not verified unavailable - topics remote could not be fetched partial
3/6 [PATCH 3/6] BACKPORT: dt-bindings: display: bridge: lt9211: Require present - exact patch-id match at c2738d8 skipped - not checked because qcom-next already contains the change present
4/6 [PATCH 4/6] FROMLIST: arm64: dts: qcom: qcs6490-rb3gen2: Add LVDS missing - no subject, patch-id, or full tree-content match found unavailable - topics remote could not be fetched missing
5/6 [PATCH 5/6] FROMLIST: arm64: dts: qcom: monaco-evk: Add LVDS display missing - no subject, patch-id, or full tree-content match found unavailable - topics remote could not be fetched missing
6/6 [PATCH 6/6] FROMLIST: arm64: dts: qcom: lemans-evk: Add LVDS display missing - no subject, patch-id, or full tree-content match found unavailable - topics remote could not be fetched missing

Final Status

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

@sgaud-quic

Copy link
Copy Markdown
Contributor

PR #1057 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ../kernel-checkers/checkpatch.sh passed
dt-binding-check Both touched bindings passed dt_binding_check and dtbs_check
dtb-check New composite DTB targets expose schema failures in inherited base/mezzanine nodes
sparse-check ../kernel-checkers/sparse-check.sh passed
check-uapi-headers No UAPI header changes; checker passed
check-patch-compliance Three FROMLIST DTS overlay commits differ from their linked lore patches
tag-check Target branch is qcom-6.18.y; all 6 commit subjects have valid prefixes
qcom-next-check ⚠️ Not present as a checker log; needs separate qcom-next presence evidence for FROMLIST/UPSTREAM commits

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: LVDS display support series #1057
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/34252503694

Checker Result Summary
checkpatch ../kernel-checkers/checkpatch.sh passed
dt-binding-check Both touched bindings passed dt_binding_check and dtbs_check
dtb-check New composite DTB targets expose schema failures in inherited base/mezzanine nodes
sparse-check ../kernel-checkers/sparse-check.sh passed
check-uapi-headers No UAPI header changes; checker passed
check-patch-compliance Three FROMLIST DTS overlay commits differ from their linked lore patches
tag-check Target branch is qcom-6.18.y; all 6 commit subjects have valid prefixes
qcom-next-check ⚠️ Not present as a checker log; needs separate qcom-next presence evidence for FROMLIST/UPSTREAM commits

❌ dtb-check

Root cause: Commits 4-6 add new composite DTB build targets, and dtb-check validates those new DTBs; the failures are on inherited nodes from the base/mezzanine DTS content, not on the new panel-lvds / lt9211c LVDS nodes themselves.

Failure details:

Log Summary: Test failed
DTC [C] arch/arm64/boot/dts/qcom/lemans-evk.dtb
DTC     arch/arm64/boot/dts/qcom/lemans-evk-lvds-boe,dv215fhm-r01.dtbo
OVL [C] arch/arm64/boot/dts/qcom/lemans-evk-lvds-boe,dv215fhm-r01.dtb
... lemans-evk*.dtb: usb-typec@67 (ti,hd3ss3220): 'wakeup-source' does not match any regex
... lemans-evk*.dtb: video-codec@aa00000 (qcom,sa8775p-iris): 'iommus' is a required property
... lemans-evk*.dtb: video-codec@aa00000: Unevaluated properties are not allowed ('iommu-map')
... lemans-evk*.dtb: ethernet@23000000 / ethernet@23040000: interconnect* unexpected

DTC [C] arch/arm64/boot/dts/qcom/monaco-evk.dtb
OVL [C] arch/arm64/boot/dts/qcom/monaco-evk-lvds-boe,dv215fhm-r01.dtb
... monaco-evk*.dtb: cci@ac13000/ac14000/ac15000: clock-names:0: 'ahb' was expected
... monaco-evk*.dtb: pinctrl@f100000 (qcom,qcs8300-tlmm): gp_mn_active-state oneOf failed
... monaco-evk*.dtb: pinctrl@f100000: Unevaluated properties are not allowed ('usb1-hs-sel-switch-hog', 'usb1-hub-reset-hog')

DTC [C] arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dtb
OVL [C] arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine-lvds-boe,dv215fhm-r01.dtb
... qcs6490*.dtb: usb-hub@2d: failed to match any schema with compatible: ['smsc,usb4604']
... qcs6490*.dtb: pcie@0,0: Unevaluated properties are not allowed ('aspm-no-l1')
... qcs6490*.dtb: pmic@2 / pwm: pwm:nvmem: [[401, 402]] is too short
... qcs6490*industrial*.dtb: audio-codec: qcom,*jack-type*: 1 is not of type 'boolean'

Fix: Either fix the inherited schema violations in the affected base/mezzanine DTS files and bindings, or do not add these composite DTB targets until the inherited validation debt is fixed. The LVDS overlay nodes themselves did not show a direct schema error in the log.

Reproduce locally:

make -j$(nproc) O=out CHECK_DTBS=y qcom/lemans-evk-lvds-boe,dv215fhm-r01.dtb
make -j$(nproc) O=out CHECK_DTBS=y qcom/monaco-evk-lvds-boe,dv215fhm-r01.dtb
make -j$(nproc) O=out CHECK_DTBS=y qcom/qcs6490-rb3gen2-industrial-mezzanine-lvds-boe,dv215fhm-r01.dtb

❌ check-patch-compliance

Root cause: The three DTS overlay commits have FROMLIST: subjects and Link: trailers, but the local patch content does not match the linked lore submissions.

Failure details:

Checking commit: FROMLIST: arm64: dts: qcom: qcs6490-rb3gen2: Add LVDS display overlay
Change is different from the one mentioned in Link

Checking commit: FROMLIST: arm64: dts: qcom: monaco-evk: Add LVDS display  overlay
Change is different from the one mentioned in Link

Checking commit: FROMLIST: arm64: dts: qcom: lemans-evk: Add LVDS display overlay
Change is different from the one mentioned in Link

Fix: For commits 67ac0ca9281e, 2f5e8ef615f4, and caf9fee4f6cf, either make the patches match the linked lore revisions exactly, or update each commit to link to the exact posted revision that matches this PR. If the differences are intentional downstream adaptations, use the correct prefix/trailer policy for that adaptation.

Reproduce locally:

b4 am --single-message -C -l -3 <Link-from-failing-commit> -o /tmp/out
# then compare the PR commit diff against the fetched mbox diff

Verdict

Not ready to merge: 2 checker blockers remain, dtb-check schema failures and check-patch-compliance content mismatches for commits 4-6.

@qcomlnxci

Copy link
Copy Markdown

Test Matrix

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

@sgaud-quic

Copy link
Copy Markdown
Contributor

quic-vishsain still see dtb-check failed :

New composite DTB targets expose schema failures in inherited base/mezzanine nodes

@Komal-Bajaj

Copy link
Copy Markdown
Contributor

quic-vishsain still see dtb-check failed :

New composite DTB targets expose schema failures in inherited base/mezzanine nodes

These errors seems to be pre-existing, not related to this PR.

@sgaud-quic
Salendarsingh Gaud (sgaud-quic) merged commit d429b61 into qualcomm-linux:qcom-6.18.y Sep 9, 2026
6 of 9 checks passed
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.

5 participants