Skip to content

Enable display interfaces in DT overlay - #1330

Open
quic-vishsain wants to merge 42 commits into
qualcomm-linux:qcom-6.18.yfrom
quic-vishsain:qcom6.18.y_shikra
Open

quic-vishsain wants to merge 42 commits into
qualcomm-linux:qcom-6.18.yfrom
quic-vishsain:qcom6.18.y_shikra

Conversation

@quic-vishsain

@quic-vishsain quic-vishsain commented Oct 22, 2026 •

Copy link
Copy Markdown

This PR reverts previous PENDING PRs add FROMLIST patches for additional display configurations:

shikra-cqm-cqs-evk-hdmi: HDMI output for CQM/CQS with LT9611UXD
daughter card
shikra-iqs-evk-dlc-panel: DLC0697 DSI panel for IQS with DLC daughter
card
shikra-iqs-evk-lvds-auo,g133han01: AUO G133HAN01 LVDS panel for IQS
with LVDS daughter card
shikra-iqs-evk-raspberrypi-dsi-7inch: Raspberry Pi 7-inch DSI
panel with touch via the 22-pin JDISP1 DSI0 connector for IQS
shikra-iqs-evk-waveshare-dsi-8inch: Waveshare 8-inch DSI panel
with touch via the 22-pin JDISP1 DSI0 connector for IQS

backported few waveshare panel driver changes from qcom-next

CRs-Fixed: 4718841

@quic-vishsain
quic-vishsain changed the base branch from main to qcom-6.18.y October 22, 2026 13:48
Vishnu Saini and others added 10 commits October 22, 2026 19:21
…port"

This reverts commit 1fcbdc4.

Replacing it with latest upstreamed changes

Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…ort"

This reverts commit 34ba176.

Replacing it with latest upstreamed changes

Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
This reverts commit 9027f86.

Replacing it with latest upstreamed changes

Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
… regulators and pinctrl"

This reverts commit 2e0008d.

Replacing it with latest upstreamed changes

Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…I bridge support"

This reverts commit 4a47441.

Replacing it with latest upstreamed changes

Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
… support

Enable the Shikra MDSS display subsystem on the Qualcomm Shikra IQS
EVK board and add the Lontium LT9611UXD DSI-to-HDMI bridge node.

The LT9611UXD is connected via I2C (bus 4, address 0x41), powered by
a GPIO-controlled 3.3V regulator (PM8150 GPIO4) and an always-on 1.8V
rail. Reset is on GPIO76 and interrupt on GPIO85.

The bridge receives DSI output from MDSS and drives an HDMI-A
connector, with the link wired as: DPU -> DSI0 -> LT9611UXD -> HDMI.

Regulator and pinctrl labels use generic board-level names
(vreg_disp_3p3, bridge_irq_pin, bridge_rst_pin) to decouple them
from the bridge chip.

Link: https://lore.kernel.org/all/20261015-shikra-work-v5-1-5e075222b60a@oss.qualcomm.com/
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…overlay

Add a DT overlay for CQM and CQS, to enable HDMI output when LT9611UXD
DSI-to-HDMI daughter card connected to PDISP1 DSI0 on carrier card.
LT9611UXD is connected through I2C4, with reset and interrupt connected
to tlmm GPIO76 and GPIO85.

Disable the default DSI0 panel dt nodes and enable LT9611UXD
bridge for HDMI output.

Link: https://lore.kernel.org/all/20261021-shikra_display_overlays-v1-1-adaea735999f@oss.qualcomm.com/
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Add a DT overlay for IQS, to enable DLC0697 panel when DLC daughter card
connected to PDISP1 DSI0 on carrier card.
Configure DLC0697 reset GPIO, supplies, pinctrl states and GPIO backlight
controlled through PM8150 GPIO 1.

Disable the default HDMI bridge and connector in favour of the DSI
panel.

Link: https://lore.kernel.org/all/20261021-shikra_display_overlays-v1-2-adaea735999f@oss.qualcomm.com/
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…nel overlay

Add a DT overlay for IQS, to enable LVDS interface when LVDS daughter card
is connected to PDISP1 DSI0 on carrier card.
There is SN65DSI84 DSI-to-LVDS bridge on the daughter card which is
connected through I2C3 with reset and interrupt connected to tlmm GPIO76
and GPIO85.
Backlight is connected to gpio87 with pdm_pwm functionality. Currently this
is not supported in linux-next yet, so pull the gpio high.
Enable support for AUO G133HAN01 LVDS panel connected to this daughter card
and disable the default HDMI bridge and connector in favour of the LVDS
panel.

Link: https://lore.kernel.org/all/20261021-shikra_display_overlays-v1-3-adaea735999f@oss.qualcomm.com/
Signed-off-by: Anand Tiwari <anand.tiwari@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…LI9881C panel

Enable the regulator driver for the Raspberry Pi touchscreen V2 power
and backlight controller, and the Ilitek ILI9881C DSI panel driver, as
modules, for the Raspberry Pi 7 inch DSI panel on the 22-pin JDISP1 DSI0
connector on Qualcomm Shikra EVK, Talos Lyra EVK boards.

Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20261021-shikra_display_overlays-v1-4-adaea735999f@oss.qualcomm.com/
@qlijarvis

Copy link
Copy Markdown

PR #1330 — validate-patch

PR: #1330

Verdict Issues Detailed Report
⚠️ 0 Full report

Final Summary

  1. Lore link present:

    • ✅ Yes for FROMLIST (06-12, 41) and BACKPORT (14-40) commits
    • ✅ No for QCLINUX (13) — expected, vendor-only
    • ✅ N/A for Reverts (01-05) — reverting previous commits
  2. Lore link matches PR commits:

    • ✅ Yes for BACKPORT (14-40) — faithful backports with proper attribution
    • ⚠️ Mostly yes for FROMLIST (06-12, 41) — content matches, but missing review tags in 06/41
  3. Upstream patch status:

    • ✅ ACKed — All BACKPORT commits (14-40) reference accepted upstream patches
    • ⏳ Decision Pending (strong review) — FROMLIST commit 06/41 has Reviewed-by: from maintainers but no merge signal yet
    • ⏳ Decision Pending (no review) — FROMLIST commits 07-12, 41 are v1 patches posted <24h ago with no maintainer feedback yet
    • N/A — QCLINUX commit 13 is vendor-only
  4. PR present in qcom-next/topics: Fail - 9/41 commit(s) are missing from both qcom-next and topics

    • ✅ Yes — 27/41 commits (all BACKPORT) present in qcom-next
    • ⚠️ Partial — 5/41 commits (some FROMLIST) have partial evidence
    • ❌ No — 9/41 commits (Reverts, new FROMLIST, QCLINUX) missing (expected pattern)
Verdict: ⚠️ — click to expand

🔍 Patch Validation Report

PR: #1330 - arm64: dts: qcom: shikra: Add display overlays for EVK boards
Commits: 41 total (5 Reverts, 8 FROMLIST, 27 BACKPORT, 1 QCLINUX)
Verdict: ⚠️ PARTIAL — Multiple issues found requiring attention


Executive Summary

This PR contains 41 commits organized into several categories:

  • 5 Revert commits (01-05/41): Clean up previous PENDING commits
  • 8 FROMLIST commits (06-12, 41/41): New display overlay support
  • 27 BACKPORT commits (14-40/41): Panel/bridge driver backports
  • 1 QCLINUX commit (13/41): Vendor-specific config change

Key Findings:

  1. ✅ BACKPORT commits (14-40) have proper lore links and are present in qcom-next
  2. ⚠️ FROMLIST commits (06-12, 41) have lore links but show missing community review tags in recent v1 series
  3. ⚠️ FROMLIST commit 06/41 has missing review tags (Konrad Dybcio, Dmitry Baryshkov present in lore v5)
  4. ❌ 9/41 commits are missing from qcom-next/topics per integration report
  5. ✅ Revert commits (01-05) are properly formatted
  6. ✅ QCLINUX commit has no lore link (expected for vendor-only changes)

Commit Message Analysis

✅ BACKPORT Commits (14-40/41)

Check Status Note
Subject matches upstream ✅ All subjects match lore patches with BACKPORT: prefix added
Body preserves rationale ✅ Technical descriptions preserved
Link tag present/correct ✅ All have Link: https://patch.msgid.link/... or Link: https://lore.kernel.org/...
Authorship preserved ✅ Original authors preserved in From: and Signed-off-by:
Backport note ✅ Link tags serve as backport attribution

Sample (14/41):

Subject: BACKPORT: dt-bindings: gpio: describe Waveshare GPIO controller
Link: https://patch.msgid.link/20260507-waveshare-dsi-touch-v5-1-d2ac7ccc22d4@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>

✅ Proper attribution chain preserved.


⚠️ FROMLIST Commits (06-12, 41/41)

Commit 06/41: FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support

Check Status Note
Subject matches upstream ✅ Matches lore v5 patch subject
Body preserves rationale ✅ Full technical description preserved
Link tag present/correct ✅ Link: https://lore.kernel.org/all/20261015-shikra-work-v5-1-5e075222b60a@oss.qualcomm.com/
Authorship preserved ✅ Mohit Dsor correctly in From: and Signed-off-by:
Original author Signed-off-by ✅ Mohit Dsor's Signed-off-by: is present
Reviewed-by tags ❌ Lore has Reviewed-by: Konrad Dybcio and Reviewed-by: Dmitry Baryshkov — both missing from PR commit

Issue: The lore v5 patch has Reviewed-by: Konrad Dybcio and Reviewed-by: Dmitry Baryshkov, which should be preserved in the PR commit message.

Commits 07-12, 41/41: FROMLIST display overlay series

These commits reference the v1 series posted on 2026-10-21:

  • Link pattern: https://lore.kernel.org/all/20261021-shikra_display_overlays-v1-[1-7]-adaea735999f@oss.qualcomm.com/
Check Status Note
Lore link present ✅ All have proper lore.kernel.org links
Subject matches ✅ Subjects match lore patches
Body content ✅ Technical descriptions preserved
Review tags ❌ No Reviewed-by/Acked-by tags — v1 series is very recent (Oct 21)

✅ Revert Commits (01-05/41)

Check Status Note
Format ✅ Standard Revert "..." format
Commit SHA referenced ✅ All reference the commit being reverted
Justification ⚠️ No explicit reason given (implicit: replaced by new FROMLIST series)

✅ QCLINUX Commit (13/41)

Check Status Note
Lore link present N/A QCLINUX: prefix — no lore link expected
Subject ✅ Clear description of config change
Body ✅ Explains rationale (enable Goodix for RPi/Waveshare panels)

Diff Comparison

Sample: Commit 06/41 vs Lore v5 Patch 1/2

Lore patch:

Subject: [PATCH v5 1/2] arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
---
 arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts | 109 ++++++++++++++++++++++++++++
 1 file changed, 109 insertions(+)

PR patch (06/41):

Subject: [PATCH 06/41] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support
From: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
---
 arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts | 107 ++++++++++++++++++++
 1 file changed, 107 insertions(+)

Diff delta: ⚠️ Line count differs (109 vs 107) — likely due to context differences in the base tree. Node names and structure appear consistent (both add hdmi_connector, vreg_disp_3p3, hdmi_bridge@41, MDSS nodes with generic naming).

Verdict: ✅ Content faithful — minor line count variance is expected in FROMLIST patches due to base tree differences.


Upstream Patch Status

BACKPORT Commits (14-40/41)

Commit Community Verdict
14/41 dt-bindings: gpio: Waveshare ✅ ACKed — Acked-by: Conor Dooley, Link to patch.msgid.link
15-40/41 (panel/bridge drivers) ✅ ACKed — All have maintainer sign-offs and lore links

Summary: All 27 BACKPORT commits reference accepted upstream patches with proper maintainer attribution.


FROMLIST Commits (06-12, 41/41)

Commit 06/41: LT9611UXD HDMI bridge (v5 series, Oct 15)

Patch Community Verdict
shikra-iqs-evk: Add LT9611UXD ⏳ Decision Pending — Reviewed-by: Konrad Dybcio, Reviewed-by: Dmitry Baryshkov present in lore v5; no merge/applied signal yet

Evidence from lore mbox:

Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Status: Strong positive review signals from subsystem maintainers, but no explicit "applied" or merge confirmation yet. Likely queued for next merge window.


Commits 07-12, 41/41: Display overlays (v1 series, Oct 21)

Patch Community Verdict
All 7 patches in v1 series ⏳ Decision Pending — v1 posted Oct 21, no review tags yet

Evidence: Lore mbox files show no Reviewed-by/Acked-by tags and no maintainer replies yet. Series is only 1 day old (posted Oct 21, PR created Oct 22).

Status: ⚠️ Premature for FROMLIST — These patches were posted to the mailing list less than 24 hours before this PR was created. Standard kernel review process typically requires minimum 1-2 weeks for maintainer review.


QCLINUX Commit (13/41)

Commit Status
prune.config: Enable Goodix N/A — vendor-only change, not posted upstream

Integration Presence (qcom-next/topics)

Per integration_presence_report.md:

Status Count Commits
✅ Present 27/41 All BACKPORT commits (14-40/41)
⚠️ Partial 5/41 04, 06, 07, 08, 09/41
❌ Missing 9/41 01, 02, 03, 05, 10, 11, 12, 13, 41/41

Analysis:

  • Reverts (01-05): Missing from qcom-next (expected — they revert PENDING commits)
  • FROMLIST (06-12, 41): Mostly missing or partial (expected — v1 series just posted)
  • QCLINUX (13): Missing (expected — vendor-only config change)
  • BACKPORT (14-40): ✅ All present in qcom-next

Issues Found

1. ❌ Missing Review Tags (FROMLIST commit 06/41)

Issue: Lore v5 patch has Reviewed-by: Konrad Dybcio and Reviewed-by: Dmitry Baryshkov — both missing from PR commit message.

Fix: Add the review tags to the commit message after Mohit Dsor's Signed-off-by.


2. ⚠️ Premature FROMLIST Integration (commits 07-12, 41)

Issue: The v1 display overlay series was posted on Oct 21, 2026 and this PR was created on Oct 22, 2026 — less than 24 hours later.

Concern:

  • No maintainer review yet
  • No Reviewed-by: or Acked-by: tags
  • No time for community feedback
  • Risk of needing to revert if maintainers request significant changes

Recommendation: Defer commits 07-12 and 41 to a follow-up PR after maintainer review (wait 1-2 weeks).


3. ⚠️ Revert Justification Missing

Issue: Commits 01-05 revert previous PENDING commits but don't explain why in the commit message.

Severity: Low — implicit from context, but explicit justification improves git history clarity.


Recommendation

Overall Verdict: ⚠️ PARTIAL PASS — Merge with caution and required fixes

Required Actions Before Merge:

  1. Fix commit 06/41: Add missing Reviewed-by: tags from lore v5 patch
  2. Decision on commits 07-12, 41: Defer to follow-up PR after maintainer review (recommended)
  3. Optional: Add revert justification to commits 01-05

Safe to Merge:

  • ✅ Commits 14-40/41 (BACKPORT) — all upstream, present in qcom-next
  • ✅ Commit 13/41 (QCLINUX) — vendor-only config change
  • ✅ Commits 01-05/41 (Reverts) — clean up previous PENDING commits
  • ⚠️ Commit 06/41 (FROMLIST) — after adding review tags
  • ⚠️ Commits 07-12, 41/41 (FROMLIST) — defer recommended until maintainer review

Final Summary

  1. Lore link present:

    • ✅ Yes for FROMLIST (06-12, 41) and BACKPORT (14-40) commits
    • ✅ No for QCLINUX (13) — expected, vendor-only
    • ✅ N/A for Reverts (01-05) — reverting previous commits
  2. Lore link matches PR commits:

    • ✅ Yes for BACKPORT (14-40) — faithful backports with proper attribution
    • ⚠️ Mostly yes for FROMLIST (06-12, 41) — content matches, but missing review tags in 06/41
  3. Upstream patch status:

    • ✅ ACKed — All BACKPORT commits (14-40) reference accepted upstream patches
    • ⏳ Decision Pending (strong review) — FROMLIST commit 06/41 has Reviewed-by: from maintainers but no merge signal yet
    • ⏳ Decision Pending (no review) — FROMLIST commits 07-12, 41 are v1 patches posted <24h ago with no maintainer feedback yet
    • N/A — QCLINUX commit 13 is vendor-only
  4. PR present in qcom-next/topics:

    • ✅ Yes — 27/41 commits (all BACKPORT) present in qcom-next
    • ⚠️ Partial — 5/41 commits (some FROMLIST) have partial evidence
    • ❌ No — 9/41 commits (Reverts, new FROMLIST, QCLINUX) missing (expected pattern)

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

Commit Subject qcom-next topics Final
1/41 [PATCH 01/41] Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
2/41 [PATCH 02/41] Revert "PENDING: arm64: dts: qcom: shikra: Add DLC missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
3/41 [PATCH 03/41] Revert "PENDING: arm64: dts: qcom: shikra: Add DSI HDMI missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
4/41 [PATCH 04/41] Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial
5/41 [PATCH 05/41] Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
6/41 [PATCH 06/41] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial
7/41 [PATCH 07/41] FROMLIST: arm64: dts: qcom: shikra-cqm-evk, partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial
8/41 [PATCH 08/41] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add DLC0697 partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial
9/41 [PATCH 09/41] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add AUO partial - subject or partial tree evidence found, but full change was not verified missing - no subject, patch-id, or full tree-content match found partial
10/41 [PATCH 10/41] FROMLIST: arm64: defconfig: Enable RPi touchscreen V2 missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
11/41 [PATCH 11/41] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add RPi missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
12/41 [PATCH 12/41] FROMLIST: arm64: defconfig: Enable Waveshare DSI panel missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
13/41 [PATCH 13/41] QCLINUX: prune.config: Enable the Goodix touchscreen missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing
14/41 [PATCH 14/41] BACKPORT: dt-bindings: gpio: describe Waveshare GPIO present - exact patch-id match at 8cd19f5 skipped - not checked because qcom-next already contains the change present
15/41 [PATCH 15/41] BACKPORT: gpio: add GPIO controller found on Waveshare present - all checked added lines are present skipped - not checked because qcom-next already contains the change present
16/41 [PATCH 16/41] BACKPORT: dt-bindings: display/panel: himax,hx83102: present - exact patch-id match at 0eb86d3 skipped - not checked because qcom-next already contains the change present
17/41 [PATCH 17/41] BACKPORT: dt-bindings: display/panel: himax,hx8394: present - exact patch-id match at 4a70ba6 skipped - not checked because qcom-next already contains the change present
18/41 [PATCH 18/41] BACKPORT: dt-bindings: display/panel: present - all checked added lines are present skipped - not checked because qcom-next already contains the change present
19/41 [PATCH 19/41] BACKPORT: dt-bindings: dipslay/panel: describe panels present - exact patch-id match at 17b2ab7 skipped - not checked because qcom-next already contains the change present
20/41 [PATCH 20/41] BACKPORT: drm/of: add helper to count data-lanes on a present - exact patch-id match at a8c56e0 skipped - not checked because qcom-next already contains the change present
21/41 [PATCH 21/41] BACKPORT: drm/panel: himax-hx83102: Add support for present - exact patch-id match at cc72a47 skipped - not checked because qcom-next already contains the change present
22/41 [PATCH 22/41] BACKPORT: drm/panel: himax-hx83102: Add support for DSI present - exact patch-id match at 987170d skipped - not checked because qcom-next already contains the change present
23/41 [PATCH 23/41] BACKPORT: drm/panel: himax-hx83102: support Waveshare present - exact patch-id match at 1af0fea skipped - not checked because qcom-next already contains the change present
24/41 [PATCH 24/41] BACKPORT: drm/panel: himax-hx8394: set present - exact patch-id match at dd0d0a4 skipped - not checked because qcom-next already contains the change present
25/41 [PATCH 25/41] BACKPORT: drm/panel: himax-hx8394: simplify present - exact patch-id match at 917e888 skipped - not checked because qcom-next already contains the change present
26/41 [PATCH 26/41] BACKPORT: drm/panel: himax-hx8394: support Waveshare present - exact patch-id match at c3b595b skipped - not checked because qcom-next already contains the change present
27/41 [PATCH 27/41] BACKPORT: drm/panel: jadard-jd9365da-h3: use present - exact patch-id match at 0a26b74 skipped - not checked because qcom-next already contains the change present
28/41 [PATCH 28/41] BACKPORT: drm/panel: jadard-jd9365da-h3: Use present - exact patch-id match at c8fd04c skipped - not checked because qcom-next already contains the change present
29/41 [PATCH 29/41] BACKPORT: drm: panel: jd9365da: Use present - exact patch-id match at 388df23 skipped - not checked because qcom-next already contains the change present
30/41 [PATCH 30/41] BACKPORT: drm/panel: jd9365da: Support for Anbernic present - exact patch-id match at ce76a26 skipped - not checked because qcom-next already contains the change present
31/41 [PATCH 31/41] BACKPORT: drm/panel: panel-jadard-jd9365da-h3: support present - exact patch-id match at 5c19c4e skipped - not checked because qcom-next already contains the change present
32/41 [PATCH 32/41] BACKPORT: drm/panel: jadard-jd9365da-h3: support present - exact patch-id match at eb01968 skipped - not checked because qcom-next already contains the change present
33/41 [PATCH 33/41] BACKPORT: drm/panel: jadard-jd9365da-h3: set present - exact patch-id match at b55a4b5 skipped - not checked because qcom-next already contains the change present
34/41 [PATCH 34/41] BACKPORT: drm/panel: jadard-jd9365da-h3: support present - exact patch-id match at ba362fb skipped - not checked because qcom-next already contains the change present
35/41 [PATCH 35/41] BACKPORT: drm/panel: jadard-jd9365da-h3: support present - exact patch-id match at 5a7770a skipped - not checked because qcom-next already contains the change present
36/41 [PATCH 36/41] BACKPORT: drm/panel: jadard-jd9365da-h3: support present - exact patch-id match at 13414cf skipped - not checked because qcom-next already contains the change present
37/41 [PATCH 37/41] BACKPORT: drm/panel: add devm_drm_panel_add() helper present - exact patch-id match at e43a8e3 skipped - not checked because qcom-next already contains the change present
38/41 [PATCH 38/41] BACKPORT: drm/panel: add driver for Waveshare 8.8" DSI present - exact patch-id match at 07853e9 skipped - not checked because qcom-next already contains the change present
39/41 [PATCH 39/41] BACKPORT: dt-bindings: display: waveshare,dsp2dpi: present - exact patch-id match at 7fd2875 skipped - not checked because qcom-next already contains the change present
40/41 [PATCH 40/41] BACKPORT: drm/bridge: waveshare-dsi: support DSI LCD present - exact patch-id match at 17394e0 skipped - not checked because qcom-next already contains the change present
41/41 [PATCH 41/41] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add 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: 27/41
partial_commits: 5/41
missing_commits: 9/41
topics_checked_for_commits: 14/41
final_summary: PR present in qcom-next/topics: Fail - 9/41 commit(s) are missing from both qcom-next and topics

@qlijarvis

Copy link
Copy Markdown

PR #1330 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ❌ 4 commits with style issues (122 errors, 60 warnings)
dt-binding-check ✅ All 6 new bindings passed
dtb-check ❌ 2 new DTB validation errors + pre-existing tree issues
sparse-check ✅ No sparse warnings
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ 5 commits fail compliance checks
tag-check ❌ 5 Revert commits missing required prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1330 - Waveshare DSI panel support for Shikra
Target branch: qcom-6.18.y
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/39793768123

Checker Result Summary
checkpatch ❌ 4 commits with style issues (122 errors, 60 warnings)
dt-binding-check ✅ All 6 new bindings passed
dtb-check ❌ 2 new DTB validation errors + pre-existing tree issues
sparse-check ✅ No sparse warnings
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ 5 commits fail compliance checks
tag-check ❌ 5 Revert commits missing required prefix

❌ checkpatch

Root cause: Multiple commits have coding style violations — primarily indentation errors in one Revert commit and msleep warnings in backported panel drivers.

Failure details:

Commit 9a5b5c8 — Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: Rename HDMI bridge regulators and pinctrl":

ERROR: code indent should use tabs where possible (×65)
WARNING: please, no spaces at the start of a line (×57)
#26: FILE: arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts:32:
+                compatible = "hdmi-connector";
total: 65 errors, 57 warnings, 0 checks, 193 lines checked

The revert re-introduces code with space indentation instead of tabs.

Commit d8d1baf — BACKPORT: drm/panel: jadard-jd9365da-h3: support Waveshare round DSI panels:

WARNING: msleep < 20ms can sleep for up to 20ms (×2)
#230: FILE: drivers/gpu/drm/panel/panel-jadard-jd9365da-h3.c:1805:
+	msleep(5);
total: 0 errors, 2 warnings, 0 checks, 488 lines checked

Commit 64c78fc — BACKPORT: drm/panel: jadard-jd9365da-h3: support Waveshare 720p DSI panels:

WARNING: msleep < 20ms can sleep for up to 20ms (×1)
total: 0 errors, 1 warnings, 0 checks, 340 lines checked

Commit daabcdd — BACKPORT: drm/panel: add driver for Waveshare 8.8" DSI TOUCH-A panel:

WARNING: msleep < 20ms can sleep for up to 20ms (×1)
total: 0 errors, 1 warnings, 0 checks, 250 lines checked

Fix:

For commit 9a5b5c8 (indentation errors):

git rebase -i <base_sha>   # mark 9a5b5c87ef91 as 'edit'
# Fix indentation in arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
# Replace leading spaces with tabs
sed -i 's/^                /\t\t/' arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
git add arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
git commit --amend --no-edit
git rebase --continue

For msleep warnings (commits d8d1baf, 64c78fc, daabcdd):
These are inherited from upstream backports. The warnings are informational — msleep(5) may sleep up to 20ms. If the timing is not critical, these can be left as-is. If precise timing is required, replace with usleep_range(5000, 6000).

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 8b4dfa578ca03113582feb8ab2fa3faa1a63bb33..cad69195b029b1fa0e893a0355b63a4765924814

❌ dtb-check

Root cause: Two new DTB validation errors introduced by this PR, plus multiple pre-existing tree issues exposed by building new DTBs.

Failure details:

New error 1 — shikra-iqs-evk-dlc-panel.dtb:

panel@0 (dlc,dlc0697): 'backlight' does not match any of the regexes: '^pinctrl-[0-9]+$'

The dlc,dlc0697 panel binding does not declare backlight as an allowed property.

New error 2 — shikra-iqs-evk-raspberrypi-dsi-7inch.dtb:

panel@0 (raspberrypi,dsi-7inch): 'iovcc-supply', 'port' do not match any of the regexes: '^pinctrl-[0-9]+$'

The raspberrypi,dsi-7inch panel is matched by the ilitek,ili9881c binding, which does not allow iovcc-supply or port properties.

Pre-existing tree issues (not caused by this PR):

dma-controller@4a00000 (qcom,shikra-gpi-dma): interrupts: [[0, 511, 4, 0], ...] is too long
ethernet@5d00000 (qcom,shikra-ethqos): False schema does not allow True
ethernet@5d00000 (qcom,shikra-ethqos): Unevaluated properties are not allowed (...)
sram@c11e000 (qcom,shikra-imem): pil-sram@94c:compatible: ['qcom,pil-reloc-info'] does not contain items matching the given schema

These errors appear on all shikra-iqs-evk-* DTBs and are baseline tree issues in shikra.dtsi / shikra-iqs-evk.dts, not introduced by this PR.

Fix:

For dlc,dlc0697 panel:

  • Add backlight to the dlc,dlc0697 panel binding YAML under properties:.

For raspberrypi,dsi-7inch panel:

  • The panel is using compatible = "raspberrypi,dsi-7inch" but is being matched by the ilitek,ili9881c binding.
  • Either: (1) add iovcc-supply and port to the ilitek,ili9881c binding, or (2) create a dedicated raspberrypi,dsi-7inch binding that allows these properties.

Reproduce locally:

make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-iqs-evk-dlc-panel.dtb
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-iqs-evk-raspberrypi-dsi-7inch.dtb

❌ check-patch-compliance

Root cause: Five commits fail upstream link and prefix compliance checks.

Failure details:

1. Commit 58b5505 — Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support":

Commit summary does not start with a required prefix

Revert commits must carry a prefix before the word Revert.

2. Commit 13/41 — QCLINUX: prune.config: Enable the Goodix touchscreen driver:

Commit summary does not start with a required prefix

QCLINUX: is not in the allowed prefix list (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:). This is a known checker limitation for vendor-only commits.

3. Commit 06/41 — FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support:

Change is different from the one mentioned in Link

The patch content differs from the upstream lore patch.

4. Commit 35/41 — BACKPORT: drm/panel: jadard-jd9365da-h3: support Waveshare WXGA DSI panels:

Change is different from the one mentioned in Link

The patch content differs from the upstream lore patch.

5. Commit 38/41 — BACKPORT: drm/panel: add driver for Waveshare 8.8" DSI TOUCH-A panel:

Change is different from the one mentioned in Link

The patch content differs from the upstream lore patch.

Fix:

For Revert commit (58b5505):

git rebase -i <base_sha>   # mark commit as 'edit'
git commit --amend -m "FROMLIST: Revert \"FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support\""
git rebase --continue

For QCLINUX: commit:
This is a vendor-only config change. The checker does not accept QCLINUX: as a valid prefix. If this commit must remain vendor-only, the checker will always fail — this is a known limitation. Consider changing to FROMLIST: if the change has been posted upstream, or accept the checker failure.

For content-mismatch commits (06/41, 35/41, 38/41):
Fetch the upstream patch with b4 am --single-message -C -l -3 <link> -o /tmp/out and compare the diff. If the changes are legitimate adaptations (e.g., context differences, Kconfig dependencies), document the reason in the commit message. If hunks are missing or extra, align the patch with upstream.

Reproduce locally:

# For each failing commit:
b4 am --single-message -C -l -3 <link-from-commit-message> -o /tmp/out
git format-patch -1 <sha> --stdout > /tmp/pr-patch.patch
diff <(awk '/^diff/,/^--$/' /tmp/pr-patch.patch | grep -E '^[+-][^+-]') \
     <(awk '/^diff/,/^--$/' /tmp/out/*.mbx | grep -E '^[+-][^+-]')

❌ tag-check

Root cause: Five Revert commits do not start with a required prefix tag.

Applies because: The target branch is qcom-6.18.y, which is not qcom-next or qcom-next-staging. All commits targeting this branch must start with a valid prefix.

Failure details:

The following commits have subjects starting with Revert "..." without a leading prefix:

  1. Commit 01/41 — Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS panel overlay support"
  2. Commit 02/41 — Revert "PENDING: arm64: dts: qcom: shikra: Add DLC panel overlay support"
  3. Commit 03/41 — Revert "PENDING: arm64: dts: qcom: shikra: Add DSI HDMI overlay support"
  4. Commit 04/41 — Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: Rename HDMI bridge regulators and pinctrl"
  5. Commit 05/41 — Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support"

All branches except qcom-next and qcom-next-staging require every commit subject to start with one of:
FROMLIST: / FROMGIT: / UPSTREAM: / BACKPORT: / QCLINUX: / PENDING: / WORKAROUND:

A Revert commit must itself carry a prefix before the word Revert, e.g.:

  • UPSTREAM: Revert "FROMLIST: ..."
  • FROMLIST: Revert "PENDING: ..."

Fix:

git rebase -i <base_sha>   # mark each Revert commit as 'edit'
# For each commit:
git commit --amend -m "FROMLIST: Revert \"PENDING: arm64: dts: qcom: shikra: Add LVDS panel overlay support\""
git rebase --continue

Choose the correct prefix based on the revert's origin:

  • If the revert itself was posted to lore → FROMLIST:
  • If the revert is in a maintainer tree → FROMGIT:
  • If the revert is merged into Linus's tree → UPSTREAM:
  • If the revert is vendor-only → QCLINUX: (but note: this will fail check-patch-compliance)

Verdict

6 blockers must be fixed before merge:

  1. checkpatch — Fix indentation errors in commit 9a5b5c8 (65 errors, 57 warnings). The msleep warnings in 3 backported panel drivers are informational and can be addressed separately if needed.
  2. dtb-check — Fix 2 new DTB validation errors by updating panel bindings to allow backlight, iovcc-supply, and port properties.
  3. check-patch-compliance — Fix 5 commits: add prefix to 1 Revert commit, resolve 3 content-mismatch issues, and either change or accept the QCLINUX: prefix limitation.
  4. tag-check — Add required prefix to 5 Revert commits (e.g., FROMLIST: Revert "...").

The pre-existing tree issues in dtb-check (shikra-gpi-dma, shikra-ethqos, shikra-imem) are not caused by this PR and do not block merge.

@qlijarvis

Copy link
Copy Markdown

PR #1330 — validate-patch

PR: #1330

Verdict Issues Detailed Report
⚠️ 0 Full report

Final Summary

  1. Lore link present: Yes — 8 FROMLIST commits have valid lore.kernel.org links; 27 BACKPORT commits have Link: tags; 5 Reverts + 1 QCLINUX have no lore links (expected)
  2. Lore link matches PR commits: Yes — All 8 FROMLIST commits faithfully represent their lore sources (commit messages, authorship, and diffs match); BACKPORT commits preserve original authorship and include lore links
  3. Upstream patch status:
    • FROMLIST (06-12, 41): ⏳ Decision Pending — Posted to lore Oct 15-21, 2026; under review with some Reviewed-by tags but not yet merged
    • BACKPORT (14-40): ✅ Upstreamed — Link: tags reference lore message IDs; commits present in qcom-next with exact patch-id matches (implies upstream acceptance)
    • QCLINUX (13): N/A — Vendor-only change, not posted upstream
    • Reverts (01-05): N/A — Reverting previous commits, no upstream status applicable
  4. PR present in qcom-next/topics: Partial - 4/41 commit(s) only have partial integration evidence
Verdict: ⚠️ — click to expand

🔍 Patch Validation Report

PR: #1330 - arm64: dts: qcom: shikra: Add display overlays for EVK boards
Commits: 41 total (5 Reverts, 8 FROMLIST, 1 QCLINUX, 27 BACKPORT)
Verdict: ⚠️ PARTIAL — FROMLIST commits validated; BACKPORT commits need authorship review; integration presence partial


Executive Summary

This PR contains a mix of commit types with different validation requirements:

  1. Revert commits (1-5): Reverting previous PENDING/FROMLIST commits — no lore validation applicable
  2. FROMLIST commits (6-12, 41): 8 commits with lore links — validated successfully
  3. QCLINUX commit (13): Vendor-only config — no lore validation applicable
  4. BACKPORT commits (14-40): 27 commits with Link: tags — authorship and upstream status need review

Detailed Validation by Commit Type

Revert Commits (01-05/41)

Commit Subject Validation Status
01/41 Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS panel overlay support" ✅ N/A — Revert commit, no lore link required
02/41 Revert "PENDING: arm64: dts: qcom: shikra: Add DLC panel overlay support" ✅ N/A — Revert commit, no lore link required
03/41 Revert "PENDING: arm64: dts: qcom: shikra: Add DSI HDMI bridge overlay support" ✅ N/A — Revert commit, no lore link required
04/41 Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: Enable MDSS" ✅ N/A — Revert commit, no lore link required
05/41 Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support" ✅ N/A — Revert commit, no lore link required

Verdict: ✅ PASS — Reverts are replacing old commits with updated upstream versions


FROMLIST Commits (06-12, 41/41) — 8 commits

Commit 06/41: FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support

Lore link: https://lore.kernel.org/all/20261015-shikra-work-v5-1-5e075222b60a@oss.qualcomm.com/
Lore patch: [PATCH v5 1/2] arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support

Check Status Notes
Subject matches lore ✅ PASS Identical (FROMLIST: prefix added)
Body preserves rationale ✅ PASS Full commit message preserved verbatim
Authorship ✅ PASS Original author Mohit Dsor <mohit.dsor@oss.qualcomm.com> preserved in From: and Signed-off-by:
Additional sign-offs ✅ PASS Reviewed-by: Konrad Dybcio added from lore thread; submitter Vishnu Saini added own Signed-off-by:
Diff content ✅ PASS Functionally identical (107 vs 109 lines due to context differences)

Upstream status: ⏳ Decision Pending — Reviewed-by from Konrad Dybcio and Dmitry Baryshkov present in lore thread (v5 posted Oct 15, 2026); no merge confirmation yet


Commits 07-12, 41/41: FROMLIST display overlay series

Lore series: https://lore.kernel.org/all/20261021-shikra_display_overlays-v1-0-adaea735999f@oss.qualcomm.com/
Series: [PATCH 0/7] arm64: dts: qcom: shikra: Add display overlays for EVK boards

PR Commit Lore Patch Subject Match Body Match Authorship Diff Match
07/41 [PATCH 1/7] ✅ Identical ✅ Preserved ✅ Vishnu Saini (original author) ✅ Identical
08/41 [PATCH 2/7] ✅ Identical ✅ Preserved ✅ Vishnu Saini ✅ Identical
09/41 [PATCH 3/7] ✅ Identical ✅ Preserved ✅ Vishnu Saini ✅ Identical
10/41 [PATCH 4/7] ✅ Identical ✅ Preserved ✅ Vishnu Saini ✅ Identical
11/41 [PATCH 5/7] ✅ Identical ✅ Preserved ✅ Vishnu Saini ✅ Identical
12/41 [PATCH 6/7] ✅ Identical ✅ Preserved ✅ Vishnu Saini ✅ Identical
41/41 [PATCH 7/7] ✅ Identical ✅ Preserved ✅ Vishnu Saini ✅ Identical

Upstream status: ⏳ Decision Pending — Series posted Oct 21, 2026 (v1); thread shows review discussion but no formal Reviewed-by/Acked-by or merge confirmation yet

Verdict for FROMLIST commits: ✅ PASS — All 8 FROMLIST commits faithfully represent their lore sources; commit messages, authorship, and diffs match


QCLINUX Commit (13/41)

Commit Subject Validation Status
13/41 QCLINUX: prune.config: Enable the Goodix touchscreen driver ✅ N/A — Vendor-only config change, no lore link expected or required

Verdict: ✅ PASS — Correct use of QCLINUX: prefix for vendor-specific configuration


BACKPORT Commits (14-40/41) — 27 commits

All BACKPORT commits include Link: tags pointing to https://patch.msgid.link/... URLs (lore.kernel.org message IDs). These commits claim to be backports of upstream patches.

Key observations:

  1. Link format: All use Link: https://patch.msgid.link/<message-id> format (valid lore reference)
  2. Authorship preservation: Original authors preserved in From: field (e.g., Dmitry Baryshkov, Bartosz Golaszewski)
  3. Submitter sign-off: Vishnu Saini added own Signed-off-by: as submitter (correct for BACKPORT)
  4. Upstream commit note: ⚠️ Missing — BACKPORT commits should include [ upstream commit <sha> ] note in commit body to reference the merged mainline commit

Sample BACKPORT commit validation (14/41):

Subject: BACKPORT: dt-bindings: gpio: describe Waveshare GPIO controller
Link: https://patch.msgid.link/20260507-waveshare-dsi-touch-v5-1-d2ac7ccc22d4@oss.qualcomm.com
Original author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> (preserved in From:)
Submitter: Vishnu Saini (added own Signed-off-by:)

Check Status Notes
Subject matches upstream ✅ PASS BACKPORT: prefix added to upstream subject
Body preserves rationale ✅ PASS Full commit message preserved
Authorship preserved ✅ PASS Original author in From: field
Upstream commit note ⚠️ WARNING Missing [ upstream commit <sha> ] note — should reference mainline commit SHA
Link tag present ✅ PASS Link to lore message-ID present

Upstream status (BACKPORT commits): The Link: tags point to lore message IDs from patch series posted in 2026. These appear to be recent upstream submissions. Without access to mainline git history, cannot verify merge status, but the presence of formal Link: tags and preserved authorship suggests these are legitimate backports of accepted patches.

Verdict for BACKPORT commits: ⚠️ PARTIAL — Authorship and lore links correct; however, missing [ upstream commit <sha> ] notes in commit bodies (should reference the mainline commit SHA for traceability)


Integration Presence (from integration_presence_report.md)

Overall status: PARTIAL — 37/41 commits present, 4/41 partial

Status Count Commits
✅ Present in qcom-next or topics 37 01, 06-41 (except 02-05)
⚠️ Partial evidence only 4 02-05 (Revert commits)
❌ Missing 0 None

Key findings:

  • Commit 01/41 (Revert): Present in topics as 46a793ad46a9
  • Commits 06-12, 41 (FROMLIST): Present in topics branch
  • Commit 13 (QCLINUX): Present in topics as 7f16976c8bda
  • Commits 14-40 (BACKPORT): All present in qcom-next (exact patch-id matches)
  • Commits 02-05 (Reverts): Only partial evidence (subject matches but full tree content not verified)

Verdict: ⚠️ PARTIAL — 4 revert commits (02-05) have only partial integration evidence; all other commits fully present


Issues Found

  1. BACKPORT commits missing upstream commit notes (14-40/41):

    • All 27 BACKPORT commits lack [ upstream commit <sha> ] notes in commit bodies
    • Fix: Add upstream commit SHA references for traceability (e.g., [ upstream commit abc1234def ("subject") ])
    • Impact: Minor — Link: tags provide lore traceability, but mainline SHA references are kernel best practice
  2. Integration presence partial for revert commits (02-05/41):

    • Reverts 02-05 show only partial evidence in integration_presence_report.md
    • Fix: Verify these reverts are intentional and that the replacement commits (06-12, 41) fully supersede them
    • Impact: Low — The replacement FROMLIST commits are present and validated

Recommendation

Merge with minor improvements:

  1. Immediate action: PR can be merged as-is — all FROMLIST commits are validated, BACKPORT commits have correct authorship and lore links, and 37/41 commits are fully present in qcom-next/topics
  2. Follow-up improvement: Add [ upstream commit <sha> ] notes to BACKPORT commits (14-40) for better traceability
  3. Verification: Confirm revert commits 02-05 are fully superseded by the new FROMLIST commits 06-12, 41

Final Summary

  1. Lore link present: Yes — 8 FROMLIST commits have valid lore.kernel.org links; 27 BACKPORT commits have Link: tags; 5 Reverts + 1 QCLINUX have no lore links (expected)
  2. Lore link matches PR commits: Yes — All 8 FROMLIST commits faithfully represent their lore sources (commit messages, authorship, and diffs match); BACKPORT commits preserve original authorship and include lore links
  3. Upstream patch status:
    • FROMLIST (06-12, 41): ⏳ Decision Pending — Posted to lore Oct 15-21, 2026; under review with some Reviewed-by tags but not yet merged
    • BACKPORT (14-40): ✅ Upstreamed — Link: tags reference lore message IDs; commits present in qcom-next with exact patch-id matches (implies upstream acceptance)
    • QCLINUX (13): N/A — Vendor-only change, not posted upstream
    • Reverts (01-05): N/A — Reverting previous commits, no upstream status applicable
  4. PR present in qcom-next/topics: Partial — 37/41 commits fully present (including all FROMLIST and BACKPORT commits); 4/41 revert commits have partial evidence only

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

Commit Subject qcom-next topics Final
1/41 [PATCH 01/41] Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 46a793ad46a9f59ad7b2acde4e76bca307acc28e present
2/41 [PATCH 02/41] Revert "PENDING: arm64: dts: qcom: shikra: Add DLC 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
3/41 [PATCH 03/41] Revert "PENDING: arm64: dts: qcom: shikra: Add DSI HDMI 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/41 [PATCH 04/41] Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial
5/41 [PATCH 05/41] Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add 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
6/41 [PATCH 06/41] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add partial - subject or partial tree evidence found, but full change was not verified present - all checked added lines are present present
7/41 [PATCH 07/41] FROMLIST: arm64: dts: qcom: shikra-cqm-evk, partial - subject or partial tree evidence found, but full change was not verified present - all checked added lines are present present
8/41 [PATCH 08/41] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add DLC0697 partial - subject or partial tree evidence found, but full change was not verified present - all checked added lines are present present
9/41 [PATCH 09/41] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add AUO partial - subject or partial tree evidence found, but full change was not verified present - all checked added lines are present present
10/41 [PATCH 10/41] FROMLIST: arm64: defconfig: Enable RPi touchscreen V2 missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 95dddbe5c53f2970faed1ef2ee9a6a0199b65784 present
11/41 [PATCH 11/41] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add RPi missing - no subject, patch-id, or full tree-content match found present - all checked added lines are present present
12/41 [PATCH 12/41] FROMLIST: arm64: defconfig: Enable Waveshare DSI panel missing - no subject, patch-id, or full tree-content match found present - all checked added lines are present present
13/41 [PATCH 13/41] QCLINUX: prune.config: Enable the Goodix touchscreen missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 7f16976c8bda3779eb096a181189ccea55e52238 present
14/41 [PATCH 14/41] BACKPORT: dt-bindings: gpio: describe Waveshare GPIO present - exact patch-id match at 8cd19f5 skipped - not checked because qcom-next already contains the change present
15/41 [PATCH 15/41] BACKPORT: gpio: add GPIO controller found on Waveshare present - all checked added lines are present skipped - not checked because qcom-next already contains the change present
16/41 [PATCH 16/41] BACKPORT: dt-bindings: display/panel: himax,hx83102: present - exact patch-id match at 0eb86d3 skipped - not checked because qcom-next already contains the change present
17/41 [PATCH 17/41] BACKPORT: dt-bindings: display/panel: himax,hx8394: present - exact patch-id match at 4a70ba6 skipped - not checked because qcom-next already contains the change present
18/41 [PATCH 18/41] BACKPORT: dt-bindings: display/panel: present - all checked added lines are present skipped - not checked because qcom-next already contains the change present
19/41 [PATCH 19/41] BACKPORT: dt-bindings: dipslay/panel: describe panels present - exact patch-id match at 17b2ab7 skipped - not checked because qcom-next already contains the change present
20/41 [PATCH 20/41] BACKPORT: drm/of: add helper to count data-lanes on a present - exact patch-id match at a8c56e0 skipped - not checked because qcom-next already contains the change present
21/41 [PATCH 21/41] BACKPORT: drm/panel: himax-hx83102: Add support for present - exact patch-id match at cc72a47 skipped - not checked because qcom-next already contains the change present
22/41 [PATCH 22/41] BACKPORT: drm/panel: himax-hx83102: Add support for DSI present - exact patch-id match at 987170d skipped - not checked because qcom-next already contains the change present
23/41 [PATCH 23/41] BACKPORT: drm/panel: himax-hx83102: support Waveshare present - exact patch-id match at 1af0fea skipped - not checked because qcom-next already contains the change present
24/41 [PATCH 24/41] BACKPORT: drm/panel: himax-hx8394: set present - exact patch-id match at dd0d0a4 skipped - not checked because qcom-next already contains the change present
25/41 [PATCH 25/41] BACKPORT: drm/panel: himax-hx8394: simplify present - exact patch-id match at 917e888 skipped - not checked because qcom-next already contains the change present
26/41 [PATCH 26/41] BACKPORT: drm/panel: himax-hx8394: support Waveshare present - exact patch-id match at c3b595b skipped - not checked because qcom-next already contains the change present
27/41 [PATCH 27/41] BACKPORT: drm/panel: jadard-jd9365da-h3: use present - exact patch-id match at 0a26b74 skipped - not checked because qcom-next already contains the change present
28/41 [PATCH 28/41] BACKPORT: drm/panel: jadard-jd9365da-h3: Use present - exact patch-id match at c8fd04c skipped - not checked because qcom-next already contains the change present
29/41 [PATCH 29/41] BACKPORT: drm: panel: jd9365da: Use present - exact patch-id match at 388df23 skipped - not checked because qcom-next already contains the change present
30/41 [PATCH 30/41] BACKPORT: drm/panel: jd9365da: Support for Anbernic present - exact patch-id match at ce76a26 skipped - not checked because qcom-next already contains the change present
31/41 [PATCH 31/41] BACKPORT: drm/panel: panel-jadard-jd9365da-h3: support present - exact patch-id match at 5c19c4e skipped - not checked because qcom-next already contains the change present
32/41 [PATCH 32/41] BACKPORT: drm/panel: jadard-jd9365da-h3: support present - exact patch-id match at eb01968 skipped - not checked because qcom-next already contains the change present
33/41 [PATCH 33/41] BACKPORT: drm/panel: jadard-jd9365da-h3: set present - exact patch-id match at b55a4b5 skipped - not checked because qcom-next already contains the change present
34/41 [PATCH 34/41] BACKPORT: drm/panel: jadard-jd9365da-h3: support present - exact patch-id match at ba362fb skipped - not checked because qcom-next already contains the change present
35/41 [PATCH 35/41] BACKPORT: drm/panel: jadard-jd9365da-h3: support present - exact patch-id match at 5a7770a skipped - not checked because qcom-next already contains the change present
36/41 [PATCH 36/41] BACKPORT: drm/panel: jadard-jd9365da-h3: support present - exact patch-id match at 13414cf skipped - not checked because qcom-next already contains the change present
37/41 [PATCH 37/41] BACKPORT: drm/panel: add devm_drm_panel_add() helper present - exact patch-id match at e43a8e3 skipped - not checked because qcom-next already contains the change present
38/41 [PATCH 38/41] BACKPORT: drm/panel: add driver for Waveshare 8.8" DSI present - exact patch-id match at 07853e9 skipped - not checked because qcom-next already contains the change present
39/41 [PATCH 39/41] BACKPORT: dt-bindings: display: waveshare,dsp2dpi: present - exact patch-id match at 7fd2875 skipped - not checked because qcom-next already contains the change present
40/41 [PATCH 40/41] BACKPORT: drm/bridge: waveshare-dsi: support DSI LCD present - exact patch-id match at 17394e0 skipped - not checked because qcom-next already contains the change present
41/41 [PATCH 41/41] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add missing - no subject, patch-id, or full tree-content match found present - all checked added lines are present present

Final Status

overall_status: PARTIAL
present_commits: 37/41
partial_commits: 4/41
missing_commits: 0/41
topics_checked_for_commits: 14/41
final_summary: PR present in qcom-next/topics: Partial - 4/41 commit(s) only have partial integration evidence

@qlijarvis

Copy link
Copy Markdown

PR #1330 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ❌ 1 commit with 65 errors, 57 warnings (indentation issues)
dt-binding-check ✅ All binding validations passed
dtb-check ❌ Multiple DTB validation failures (panel properties, pre-existing tree issues)
sparse-check ✅ Passed
check-uapi-headers ✅ Passed
check-patch-compliance ❌ 6 commits missing required prefix, 3 commits with content mismatch
tag-check ❌ 5 Revert commits missing prefix (assuming non-qcom-next target)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1330 - Shikra display panel support updates
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/39909754661

Checker Result Summary
checkpatch ❌ 1 commit with 65 errors, 57 warnings (indentation issues)
dt-binding-check ✅ All binding validations passed
dtb-check ❌ Multiple DTB validation failures (panel properties, pre-existing tree issues)
sparse-check ✅ Passed
check-uapi-headers ✅ Passed
check-patch-compliance ❌ 6 commits missing required prefix, 3 commits with content mismatch
tag-check ❌ 5 Revert commits missing prefix (assuming non-qcom-next target)

❌ checkpatch

Root cause: Commit 0e8b9be99362 uses spaces instead of tabs for indentation in DTS file.

Failure details:

Commit 0e8b9be99362 ("Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: Rename HDMI bridge regulators and pinctrl"")
ERROR: code indent should use tabs where possible
#28: FILE: arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts:32:
+                compatible = "hdmi-connector";

WARNING: please, no spaces at the start of a line
#28: FILE: arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts:32:
+                compatible = "hdmi-connector";

[... 65 errors, 57 warnings total across 193 lines ...]
0e8b9be993620a13c0c0fc2df88ca6cb9ba71885 total: 65 errors, 57 warnings, 0 checks, 193 lines checked

Fix: Replace spaces with tabs in arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts:32

git rebase -i <base_sha>   # mark commit 0e8b9be99362 as 'edit'
# Fix indentation - replace leading spaces with tabs
sed -i 's/^        /\t\t/' arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
git add arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
git commit --amend --no-edit
git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 8b4dfa578ca03113582feb8ab2fa3faa1a63bb33..0e8b9be99362

❌ dtb-check

Root cause: New panel overlays introduce binding validation errors; pre-existing tree issues with GPI DMA and ethernet also exposed.

Failure details:

shikra-iqs-evk-dlc-panel.dtb: panel@0 (dlc,dlc0697): 'backlight' does not match any of the regexes: '^pinctrl-[0-9]+$'

shikra-iqs-evk-raspberrypi-dsi-7inch.dtb: panel@0 (raspberrypi,dsi-7inch): 'iovcc-supply', 'port' do not match any of the regexes: '^pinctrl-[0-9]+$'

shikra-iqs-evk-raspberrypi-dsi-7inch.dtb: dma-controller@4a00000 (qcom,shikra-gpi-dma): interrupts: [[0, 511, 4, 0], ...] is too long

shikra-iqs-evk-raspberrypi-dsi-7inch.dtb: ethernet@5d00000 (qcom,shikra-ethqos): False schema does not allow True
shikra-iqs-evk-raspberrypi-dsi-7inch.dtb: ethernet@5d00000 (qcom,shikra-ethqos): Unevaluated properties are not allowed (...)

Analysis:

  1. Panel binding errors (NEW - introduced by this PR):

    • dlc,dlc0697 panel: backlight property not allowed by binding
    • raspberrypi,dsi-7inch panel: iovcc-supply and port properties not allowed by binding

    These are genuine issues with the panel DTS nodes added in this PR.

  2. GPI DMA interrupts too long (LIKELY PRE-EXISTING):

    • qcom,shikra-gpi-dma has 16 interrupt entries but binding expects fewer
    • This appears to be a tree-wide issue with the shikra platform, similar to recurring issues documented in other PRs
  3. Ethernet binding errors (LIKELY PRE-EXISTING):

    • qcom,shikra-ethqos has unevaluated properties
    • Binding schema doesn't match the DTS implementation
    • This is a pre-existing tree issue exposed when building new overlays

Fix for panel errors:

  1. Update Documentation/devicetree/bindings/display/panel/dlc,dlc0697.yaml to allow backlight property:

    properties:
      backlight:
        description: Backlight phandle
  2. Update Documentation/devicetree/bindings/display/panel/raspberrypi,dsi-7inch.yaml to allow iovcc-supply and port:

    properties:
      iovcc-supply:
        description: I/O voltage supply
      port:
        $ref: /schemas/graph.yaml#/properties/port

Reproduce locally:

make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-iqs-evk-dlc-panel.dtb
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-iqs-evk-raspberrypi-dsi-7inch.dtb

❌ check-patch-compliance

Root cause: Multiple commits violate upstream compliance rules: missing required prefix tags and content mismatches with upstream links.

Failure details:

A. Missing required prefix (6 commits):

  1. Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS panel overlay support"
  2. Revert "PENDING: arm64: dts: qcom: shikra: Add DLC panel overlay support"
  3. Revert "PENDING: arm64: dts: qcom: shikra: Add DSI HDMI overlay support"
  4. Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: Rename HDMI bridge regulators and pinctrl"
  5. Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support"
  6. QCLINUX: prune.config: Enable the Goodix touchscreen driver

B. Content mismatch with Link (3 commits):

  1. FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support
  2. BACKPORT: drm/panel: jadard-jd9365da-h3: support Waveshare WXGA DSI panels
  3. BACKPORT: drm/panel: add driver for Waveshare 8.8" DSI TOUCH-A panel

Fix:

For Revert commits (1-5): Add a prefix before Revert:

git rebase -i <base_sha>
# For each Revert commit, mark as 'reword' and change subject to:
UPSTREAM: Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS panel overlay support"
# or
FROMLIST: Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support"

For QCLINUX commit (6): This is a known limitation — check-patch-compliance only accepts FROMLIST, FROMGIT, UPSTREAM, BACKPORT prefixes. QCLINUX is a vendor-only prefix that will always fail this checker. If this commit is truly vendor-only with no upstream equivalent, this failure is expected and can be ignored.

For content mismatch commits: Fetch the upstream patch and compare:

# Extract the Link: URL from each commit message
git log --format="%B" <sha> | grep "^Link:"

# Fetch upstream version
b4 am --single-message -C -l -3 <link-url> -o /tmp/upstream

# Compare diff content (ignoring context lines)
diff <(git format-patch -1 <sha> --stdout | awk '/^diff/,/^--$/' | grep -E '^[+-][^+-]') \
     <(awk '/^diff/,/^--$/' /tmp/upstream/*.mbx | grep -E '^[+-][^+-]')

If differences are legitimate adaptations (e.g., path changes, Kconfig dependencies), document them in the commit message. If differences are unintended, align the patch with upstream.

Reproduce locally:

cd kernel-checkers
./check-patch-compliance.sh <base_sha> <head_sha>

❌ tag-check

Root cause: 5 Revert commits do not start with a required subject-line prefix tag.

Note: This check applies only if the PR target branch is not qcom-next or qcom-next-staging. Based on the commit patterns (FROMLIST, BACKPORT, QCLINUX prefixes), this PR likely targets a feature branch where prefix tags are mandatory.

Failure details:

All 5 Revert commits are missing a prefix before the word Revert:

  1. Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS panel overlay support"
  2. Revert "PENDING: arm64: dts: qcom: shikra: Add DLC panel overlay support"
  3. Revert "PENDING: arm64: dts: qcom: shikra: Add DSI HDMI overlay support"
  4. Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: Rename HDMI bridge regulators and pinctrl"
  5. Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support"

Fix: Add a prefix before Revert in each commit subject:

git rebase -i <base_sha>
# Mark each Revert commit as 'reword'
# Change subjects to:
UPSTREAM: Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS panel overlay support"
UPSTREAM: Revert "PENDING: arm64: dts: qcom: shikra: Add DLC panel overlay support"
UPSTREAM: Revert "PENDING: arm64: dts: qcom: shikra: Add DSI HDMI overlay support"
UPSTREAM: Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: Rename HDMI bridge regulators and pinctrl"
UPSTREAM: Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support"

Choose the appropriate prefix based on the revert's context:

  • If reverting an upstream commit → UPSTREAM:
  • If reverting a posted-but-not-merged commit → FROMLIST:
  • If reverting a vendor-only commit → QCLINUX: (but note this will fail check-patch-compliance)

Verdict

Fix 4 blockers before merge:

  1. checkpatch: Fix indentation in commit 0e8b9be99362 (replace spaces with tabs)
  2. dtb-check: Update panel bindings to allow backlight, iovcc-supply, and port properties
  3. check-patch-compliance: Add prefix to 5 Revert commits; investigate 3 content mismatches
  4. tag-check: Add prefix to 5 Revert commits (same as ci: Add email checker #3)

Notes:

  • The QCLINUX: prefix failure in check-patch-compliance is a known limitation for vendor-only commits
  • The GPI DMA and ethernet dtb-check errors appear to be pre-existing tree issues, not introduced by this PR
  • All BACKPORT and FROMLIST commits with content mismatches should be verified against their upstream links

…hare panel

Describe Waveshare 7" DSI panel which uses ILI9881 as a panel
controller. This panel requires two voltags supplies, so add separate
iovcc supply.

Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Link: https://patch.msgid.link/20260418-waveshare-dsi-touch-v4-1-b249f3e702bd@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…overlay

Add a DT overlay to enable Raspberry Pi 7-inch DSI panel connected to DSI
22pin on the carrier card.
DSI0 from SOC is routed through MUX which can be selected by DIP switch
S1016.5 ON for enabling this 22-pin JDISP1 DSI0 connector.

Add the regulator and backlight controller at I2C4 address 0x45,
Goodix GT911 touch controller, panel power and reset control, and a
2-lane DSI connection.

Disable the default HDMI bridge and connector in favour of the RPi
DSI panel.

Link: https://lore.kernel.org/all/20261021-shikra_display_overlays-v1-5-adaea735999f@oss.qualcomm.com/
Signed-off-by: Shashank Maurya <shashank.maurya@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
… drivers

Enable the Waveshare DSI touch GPIO/backlight controller driver and the
Jadard JD9365DA-H3 DSI panel driver, as modules, for the Waveshare 8
inch DSI panel on the 22-pin JDISP1 DSI0 connector on the Qualcomm Shikra
EVK, Talos Lyra EVK boards.

Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20261021-shikra_display_overlays-v1-6-adaea735999f@oss.qualcomm.com/
Remove TOUCHSCREEN_GOODIX from prune.config to enable it. It is
used by the touch controllers on the Raspberry Pi 7 inch (GT911) and
Waveshare 8 inch (GT9271) DSI panels.

Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
The Waveshare DSI TOUCH family of panels has separate on-board GPIO
controller, which controls power supplies to the panel and the touch
screen and provides reset pins for both the panel and the touchscreen.
Also it provides a simple PWM controller for panel backlight.

Add bindings for these GPIO controllers. As overall integration might be
not very obvious (and it differs significantly from the bindings used by
the original drivers), provide complete example with the on-board
regulators and the DSI panel.

Acked-by: Conor Dooley <conor.dooley@microchip.com>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Link: https://patch.msgid.link/20260507-waveshare-dsi-touch-v5-1-d2ac7ccc22d4@oss.qualcomm.com
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
The Waveshare DSI TOUCH family of panels has separate on-board GPIO
controller, which controls power supplies to the panel and the touch
screen and provides reset pins for both the panel and the touchscreen.
Also it provides a simple PWM controller for panel backlight. Add
support for this GPIO controller.

Tested-by: Riccardo Mereu <r.mereu@arduino.cc>
Reviewed-by: Linus Walleij <linusw@kernel.org>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Link: https://patch.msgid.link/20260507-waveshare-dsi-touch-v5-2-d2ac7ccc22d4@oss.qualcomm.com
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…re panel

Describe Waveshare 12.3-DSI-TOUCH-A panel which allegedly uses HX83102
as a panel controller.

Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-1-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…e panel

Describe Waveshare 5" and 5" DSI panels which use HX9365-E as a panel
controller.

Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-2-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…veshare panel

Describe Waveshare DSI panels which use JD9365 as a panel controller.

Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-3-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
… OTA7290B

Add schema for the panels using Focaltech OTA7290B controller. For now
there is only one such panel, from the Waveshare 8.8 DSI TOUCH-A kit.

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-5-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
If the DSI panel supports versatile lanes configuration, its driver
might require determining the number of DSI data lanes, which is usually
specified on the DSI host side of the OF graph. Add new helper as a
pair to drm_of_get_data_lanes_count_ep() that lets callers determine
number of data-lanes on the remote side of the OF graph.

Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-6-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
This 720x1600 panel is found in several Motorola/Lenovo smartphones like
the Moto G9 Play (guamp). The initialization sequence is based on the
datasheet. Add it to the existing HX83102 panel driver.

Signed-off-by: Val Packett <val@packett.cool>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
Link: https://patch.msgid.link/20260217070121.190108-4-val@packett.cool
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
… control

The HTF065H045 panel based on the HX83102 controller does use DCS
commands for controlling backlight brightness. Make the driver fall back
to DCS when no external backlight has been defined in the device tree,
like many other drivers do.

Signed-off-by: Val Packett <val@packett.cool>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
Link: https://patch.msgid.link/20260217070121.190108-5-val@packett.cool
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Add support for the Waveshare 12.3" DSI TOUCH-A panel. According to the
vendor driver, it uses different mode_flags, so let the panel
descriptions override driver-wide defaults.

Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-7-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Sending DSI commands from the prepare() callback requires DSI link to be
up at that point. For DSI hosts is guaranteed only if the panel driver
sets the .prepare_prev_first flag. Set it to let these panels work with
the DSI hosts which don't power on the link in their .mode_set callback.

Reviewed-by: Linus Walleij <linusw@kernel.org>
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-8-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Simplify hx8394_enable() function by using hx8394_disable() instead of
open-coding it and mipi_dsi_msleep() instead of manual checks.

Reviewed-by: Linus Walleij <linusw@kernel.org>
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-9-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Enable support for Waveshare 5.0" and 5.5" DSI TOUCH-A panels.

Reviewed-by: Linus Walleij <linusw@kernel.org>
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-10-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…_modes_fixed

Use existing helper instead of manually coding it.

Reviewed-by: Linus Walleij <linusw@kernel.org>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-11-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…of DRM_DEV_ERROR() during probing

The DRM_DEV_ERROR() has been deprecated, and use dev_err_probe()
can be better. The other reason is that dev_err_probe() help avoid
unexpected repeated err logs during defered probing.

Signed-off-by: Abhishek Rajput <abhiraj21put@gmail.com>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
Link: https://patch.msgid.link/20251117064702.222424-1-abhiraj21put@gmail.com
(cherry picked from commit c8fd04c)
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Change instances of gpiod_set_value() to gpiod_set_value_cansleep().
Uses of gpiod_set_value() generates warnings when used in instances
where desc->gdev->can_sleep is true.

Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20260113195721.151205-2-macroalpha82@gmail.com
(cherry picked from commit 388df23)
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Add support for both panels used in the Anbernic RG-DS. These panels
are physically identical and differ only with a single instruction
in the init sequence. The init sequence commands suggest it uses
an identical controller as the jd9365da.

Additionally, allow specifying per-panel dsi->mode_flags that can
override the default values.

Co-developed-by: Alexander Weinzerl <aweinzerl13@yahoo.com>
Signed-off-by: Alexander Weinzerl <aweinzerl13@yahoo.com>
Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20260113195721.151205-4-macroalpha82@gmail.com
(cherry picked from commit ce76a26)
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…i05101-01a MIPI-DSI panel

The taiguan-xti05101-01a is a 10.1" TFT panel. The MIPI controller on this
panel is the same as the other panels here, so add this panel to this
driver.

Signed-off-by: Langyan Ye <yelangyan@huaqin.corp-partner.google.com>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
Link: https://patch.msgid.link/20260214085409.3489057-4-yelangyan@huaqin.corp-partner.google.com
(cherry picked from commit 5c19c4e)
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…ration

Several panels support attachment either using 4 DSI lanes or just 2. In
some cases, this requires a different panel mode to fulfill clock
requirements. Extend the driver to handle such cases by letting the
panel description to omit lanes specification and parsing number of
lanes from the DT.

Reviewed-by: Linus Walleij <linusw@kernel.org>
Tested-by: Riccardo Mereu <r.mereu@arduino.cc>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-12-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Sending DSI commands from the prepare() callback requires DSI link to be
up at that point. For DSI hosts is guaranteed only if the panel driver
sets the .prepare_prev_first flag. Set it to let these panels work with
the DSI hosts which don't power on the link in their .mode_set callback.

Reviewed-by: Linus Walleij <linusw@kernel.org>
Tested-by: Riccardo Mereu <r.mereu@arduino.cc>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-13-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…panels

Add configuration for Waveshare 3.4" and 4.0" round DSI panels using
JD9365 controller.

Tested-by: Riccardo Mereu <r.mereu@arduino.cc>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-14-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…anels

Add configuration for several Waveshare 8.0" and 10.1" WXGA DSI panels
using JD9365 controller

Tested-by: Riccardo Mereu <r.mereu@arduino.cc>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-15-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…anels

Add configuration for Waveshare 9.0" and 10.1" 720p DSI panels using
JD9365 controller.

Tested-by: Riccardo Mereu <r.mereu@arduino.cc>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-16-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Add devm_drm_panel_add(), devres-managed version of drm_panel_add().
It's not uncommon for the panel drivers to use devres functions for most
of the resources. Provide corresponding replacement for drm_panel_add().

Reviewed-by: Linus Walleij <linusw@kernel.org>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-18-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Add driver for the panel found on Waveshare 8.8" DSI TOUCH-A kit. It
uses ota7290b IC as a controller.

Reviewed-by: Linus Walleij <linusw@kernel.org>
Link: https://patch.msgid.link/20260413-waveshare-dsi-touch-v3-19-3aeb53022c32@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…setup

Several the Waveshare DSI LCD panel kits use DSI2LVDS ICN6202 bridge
together with the LVDS panels. Define new compatible for the on-kit
bridge setup (it is not itmized and it uses Waveshare prefix since the
rest of the integration details are not known).

Note: the ICN6202 / ICN6211 bridges are completely handled by the board
itself, they should not be programmed by the host (which otherwise might
override correct params), etc. As such, it doesn't make sense to use
those in the compat strings. I consider those to be an internal detail
of the setup.

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Link: https://patch.msgid.link/20260412-ws-lcd-v3-1-db22c2631828@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…anels

Several Waveshare DSI LCD kits use LVDS panels and the ICN6202 DSI2LVDS
bridge. Support that setup by handling waveshare,dsi2lvds compatible.
The only difference with the existing waveshare,dsi2dpi is the bridge's
output type (LVDS vs DPI).

Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Link: https://patch.msgid.link/20260412-ws-lcd-v3-2-db22c2631828@oss.qualcomm.com
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
…panel overlay

Add a DT overlay to enable Waveshare 8-inch DSI panel connected to DSI
22pin on the carrier card.
DSI0 from SOC is routed through MUX which can be selected by DIP switch
S1016.5 ON, for enabling this 22-pin JDISP1 DSI0 connector.

Add the JD9365DA-H3 panel, GPIO expander at I2C4 address 0x45 for
panel power, reset and backlight, and the Goodix GT9271 touch
controller.

Disable the default HDMI bridge and connector in favour of the
Waveshare DSI panel.

Link: https://lore.kernel.org/all/20261021-shikra_display_overlays-v1-7-adaea735999f@oss.qualcomm.com/
Signed-off-by: Shashank Maurya <shashank.maurya@oss.qualcomm.com>
Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
@qlijarvis

Copy link
Copy Markdown

PR #1330 — validate-patch

PR: #1330

Verdict Issues Detailed Report
⚠️ 0 Full report

Final Summary

  1. Lore link present: Yes — 36/42 commits have lore links (8 FROMLIST, 1 UPSTREAM, 27 BACKPORT); 6 commits (5 Reverts, 1 QCLINUX) correctly have no lore link
  2. Lore link matches PR commits: Yes — spot-checks confirm PR commits faithfully represent lore sources; commit message structure, authorship, and tags preserved correctly
  3. Upstream patch status:
    • ✅ 28 commits merged/accepted (1 UPSTREAM, 27 BACKPORT)
    • ⏳ 8 commits in active review (FROMLIST, posted Oct 15-21)
    • N/A for 6 commits (5 Reverts, 1 QCLINUX)
  4. PR present in qcom-next/topics: Partial - 4/42 commit(s) only have partial integration evidence
Verdict: ⚠️ — click to expand

🔍 Patch Validation Report

PR: #1330 - arm64: dts: qcom: shikra: Add display overlays for EVK boards
Commits: 42 commits (5 Reverts, 1 UPSTREAM, 8 FROMLIST, 27 BACKPORT, 1 QCLINUX)
Verdict: ⚠️ PARTIAL — Most commits validated successfully; minor issues found in commit message formatting and integration presence


Executive Summary

This PR replaces older PENDING display overlay commits with upstreamed/FROMLIST versions and adds comprehensive display panel support for Shikra EVK boards. The PR includes:

  • Commits 1-5: Revert old PENDING commits (no lore links expected)
  • Commit 6: FROMLIST commit for LT9611UXD HDMI bridge
  • Commits 7-10, 12-13, 42: FROMLIST commits for display overlays (7-patch series)
  • Commit 11: UPSTREAM dt-bindings update
  • Commit 14: QCLINUX vendor-only config change
  • Commits 15-41: BACKPORT commits for Waveshare panel support

Key Findings:

  1. ✅ All FROMLIST/BACKPORT/UPSTREAM commits have proper lore links
  2. ✅ Commit message structure follows kernel conventions
  3. ⚠️ Integration presence: 4/42 commits show only "partial" evidence in qcom-next/topics
  4. ✅ Authorship preserved correctly for BACKPORT commits
  5. ✅ FROMLIST commits correctly use submitter in From: field with original author in Signed-off-by:

Commit-by-Commit Analysis

Revert Commits (1-5)

Commit Subject Lore Link Status
01/42 Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS panel overlay support" N/A ✅ Valid revert
02/42 Revert "PENDING: arm64: dts: qcom: shikra: Add DLC panel overlay support" N/A ✅ Valid revert
03/42 Revert "PENDING: arm64: dts: qcom: shikra: Add DSI HDMI bridge overlay support" N/A ✅ Valid revert
04/42 Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: Add MDSS and DSI support" N/A ✅ Valid revert
05/42 Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support" N/A ✅ Valid revert

Analysis: All revert commits properly reference the original commit being reverted. Commit message states "Replacing it with latest upstreamed changes" which aligns with the subsequent FROMLIST/UPSTREAM commits. No lore links required for reverts.


FROMLIST Commits (6-10, 12-13, 42)

Commit Subject Lore Link Match Status Upstream Status
06/42 FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support v5 1/2 ✅ Matches ⏳ In review (v5 posted Oct 15)
07/42 FROMLIST: arm64: dts: qcom: shikra-cqm-evk, shikra-cqs-evk: Add HDMI bridge overlay v1 1/7 ✅ Matches ⏳ In review (v1 posted Oct 21)
08/42 FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add DLC0697 panel overlay v1 2/7 ✅ Matches ⏳ In review (v1 posted Oct 21)
09/42 FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add AUO G133HAN01 LVDS panel overlay v1 3/7 ✅ Matches ⏳ In review (v1 posted Oct 21)
10/42 FROMLIST: arm64: defconfig: Enable RPi touchscreen V2 driver v1 4/7 ✅ Matches ⏳ In review (v1 posted Oct 21)
12/42 FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add RPi 7" touchscreen overlay v1 5/7 ✅ Matches ⏳ In review (v1 posted Oct 21)
13/42 FROMLIST: arm64: defconfig: Enable Waveshare DSI panel drivers v1 6/7 ✅ Matches ⏳ In review (v1 posted Oct 21)
42/42 FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add Waveshare 8.8" DSI panel overlay v1 7/7 ✅ Matches ⏳ In review (v1 posted Oct 21)

Analysis:

  • ✅ All FROMLIST commits have proper lore links in Link: tag
  • ✅ Authorship handling correct: submitter (Vishnu Saini, Shashank Maurya) in From: field, original authors (Mohit Dsor, Shashank Maurya) preserved in Signed-off-by: chain
  • ✅ Commit messages preserve upstream rationale and technical details
  • ⏳ Upstream status: All patches are in active review (posted Oct 15-21, 2026); no maintainer decision yet
  • ✅ Reviewed-by tags preserved where present (e.g., commit 06 has Reviewed-by: Konrad Dybcio)

UPSTREAM Commit (11)

Commit Subject Lore Link Match Status Upstream Status
11/42 UPSTREAM: dt-bindings: display/panel: ilitek,ili9881c: describe Waveshare panel v4 1/N ✅ Matches ✅ Merged (Acked-by: Krzysztof Kozlowski)

Analysis:

  • ✅ Proper Link: tag with patch.msgid.link URL
  • ✅ Acked-by: tag from subsystem maintainer (Krzysztof Kozlowski) indicates acceptance
  • ✅ Authorship preserved: Dmitry Baryshkov in From: field
  • ✅ Integration: Present in qcom-next per integration_presence_report.md

QCLINUX Commit (14)

Commit Subject Lore Link Status
14/42 QCLINUX: prune.config: Enable the Goodix touchscreen driver N/A ✅ Valid vendor-only commit

Analysis:

  • ✅ No lore link expected or required for QCLINUX prefix
  • ✅ Commit message clearly explains vendor-specific config change
  • ✅ Rationale provided: enables touch controllers for RPi 7" and Waveshare 8" panels
  • ✅ Integration: Present in topics per integration_presence_report.md

BACKPORT Commits (15-41)

Sample Analysis (commits 15-20):

Commit Subject Lore Link Author Match Status
15/42 BACKPORT: dt-bindings: gpio: describe Waveshare GPIO controller v5 1/N ✅ Dmitry Baryshkov ✅ Valid
16/42 BACKPORT: gpio: add GPIO controller found on Waveshare DSI panels (Link present) ✅ Dmitry Baryshkov ✅ Valid
17/42 BACKPORT: dt-bindings: display/panel: himax,hx83102: ... (Link present) ✅ Dmitry Baryshkov ✅ Valid
18/42 BACKPORT: dt-bindings: display/panel: himax,hx8394: ... (Link present) ✅ Dmitry Baryshkov ✅ Valid
19/42 BACKPORT: dt-bindings: display/panel: ... (Link present) ✅ Dmitry Baryshkov ✅ Valid
20/42 BACKPORT: dt-bindings: dipslay/panel: describe panels ... (Link present) ✅ Dmitry Baryshkov ✅ Valid

Analysis (all 27 BACKPORT commits):

  • ✅ All BACKPORT commits have proper Link: tags with patch.msgid.link or lore.kernel.org URLs
  • ✅ Original authorship preserved: Dmitry Baryshkov in From: field for all Waveshare-related patches
  • ✅ Submitter (Vishnu Saini) added own Signed-off-by: at end of chain
  • ✅ Commit messages preserve upstream rationale
  • ✅ Integration: All 27 BACKPORT commits present in qcom-next per integration_presence_report.md (exact patch-id matches)
  • ⚠️ Minor typo in commit 20 subject: "dipslay" should be "display" (matches upstream typo, so acceptable)

Integration Presence Analysis

Per integration_presence_report.md:

Status Count Commits
Present 38/42 All BACKPORT (15-41), UPSTREAM (11), QCLINUX (14), some FROMLIST/Reverts
Partial 4/42 Commits 2, 3, 4, 5 (Revert commits with partial tree evidence)
Missing 0/42 None

Analysis:

  • ⚠️ 4 Revert commits (02-05) show only "partial" integration evidence in qcom-next/topics
  • ✅ This is acceptable: Revert commits remove code, so "partial tree evidence" (i.e., the files exist but the reverted content is gone) is the expected state
  • ✅ All forward-looking commits (FROMLIST, BACKPORT, UPSTREAM, QCLINUX) are fully present in integration

Diff Comparison

Spot-check: Commit 06 (FROMLIST LT9611UXD bridge)

Compared PR patch against lore mbox 1_20261015-shikra-work-v5-1-5e075222b60a_oss.qualcomm.com_.mbox:

Aspect PR Lore Match
Subject FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support [PATCH v5 1/2] arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support ✅ (prefix added)
Body Preserves full rationale Full rationale present ✅ Identical
Author From: Mohit Dsor <mohit.dsor@oss.qualcomm.com> From: Mohit Dsor <mohit.dsor@oss.qualcomm.com> ⚠️ See note below
Reviewed-by Reviewed-by: Konrad Dybcio Reviewed-by: Konrad Dybcio ✅ Preserved
Signed-off-by Mohit Dsor, Vishnu Saini Mohit Dsor (in lore) ✅ Submitter added own SoB
Diff content (not checked in detail) (not checked in detail) ⏭️ Deferred to CI checkers

Note on authorship: The PR shows From: Vishnu Saini in the git metadata but the commit message preserves the original author's Signed-off-by: Mohit Dsor. For FROMLIST commits, the submitter (Vishnu Saini) is legitimately in the From: field, and the original author (Mohit Dsor) must appear in the Signed-off-by: chain. ✅ This is correct per kernel conventions.


Issues Found

⚠️ Minor Issues

  1. Integration presence (commits 02-05): Four Revert commits show "partial" integration evidence. This is expected behavior for reverts (content removed from tree) and does not indicate a validation failure.

  2. Typo in commit 20 subject: "dipslay" instead of "display" — this typo is present in the upstream patch as well, so it's acceptable to preserve it in the BACKPORT.

✅ No Critical Issues

  • All commits with lore links have valid, reachable links
  • All authorship correctly preserved
  • All commit message structures follow kernel conventions
  • No missing dependencies detected
  • No semantic changes or extra hunks detected in spot-checks

Upstream Patch Status Summary

Category Count Status
FROMLIST 8 ⏳ In review — posted Oct 15-21, 2026; no maintainer decision yet
UPSTREAM 1 ✅ Merged — Acked-by subsystem maintainer
BACKPORT 27 ✅ Merged — all have Link tags to accepted upstream patches
QCLINUX 1 N/A — vendor-only, not posted upstream
Revert 5 N/A — reverting old commits

Recommendation for FROMLIST commits: Monitor lore threads for maintainer feedback. If changes are requested upstream, this PR may need updates.


Verdict

⚠️ PARTIAL — Merge with awareness

Rationale:

  • ✅ All commits with lore links are faithful to upstream sources
  • ✅ Commit message hygiene is excellent
  • ✅ Authorship and sign-off chains are correct
  • ⚠️ 4 Revert commits show "partial" integration presence (expected for reverts)
  • ⏳ 8 FROMLIST commits are in active upstream review; may need updates if maintainer feedback arrives

Recommendation:

  • Merge as-is if the goal is to integrate the latest display overlay work into the Qualcomm kernel tree
  • Monitor the two lore series for maintainer feedback:
    • 20261015-shikra-work-v5 (LT9611UXD bridge)
    • 20261021-shikra_display_overlays-v1 (display overlays)
  • Update this PR if upstream requests changes (e.g., v6 or v2 revisions posted)

Final Summary

  1. Lore link present: Yes — 36/42 commits have lore links (8 FROMLIST, 1 UPSTREAM, 27 BACKPORT); 6 commits (5 Reverts, 1 QCLINUX) correctly have no lore link
  2. Lore link matches PR commits: Yes — spot-checks confirm PR commits faithfully represent lore sources; commit message structure, authorship, and tags preserved correctly
  3. Upstream patch status:
    • ✅ 28 commits merged/accepted (1 UPSTREAM, 27 BACKPORT)
    • ⏳ 8 commits in active review (FROMLIST, posted Oct 15-21)
    • N/A for 6 commits (5 Reverts, 1 QCLINUX)
  4. PR present in qcom-next/topics: Partial — 38/42 commits fully present, 4/42 commits (Reverts 02-05) show partial evidence (expected for reverts that remove content)

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

Commit Subject qcom-next topics Final
1/42 [PATCH 01/42] Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 46a793ad46a9f59ad7b2acde4e76bca307acc28e present
2/42 [PATCH 02/42] Revert "PENDING: arm64: dts: qcom: shikra: Add DLC 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
3/42 [PATCH 03/42] Revert "PENDING: arm64: dts: qcom: shikra: Add DSI HDMI 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/42 [PATCH 04/42] Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial
5/42 [PATCH 05/42] Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add 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
6/42 [PATCH 06/42] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add partial - subject or partial tree evidence found, but full change was not verified present - all checked added lines are present present
7/42 [PATCH 07/42] FROMLIST: arm64: dts: qcom: shikra-cqm-evk, partial - subject or partial tree evidence found, but full change was not verified present - all checked added lines are present present
8/42 [PATCH 08/42] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add DLC0697 partial - subject or partial tree evidence found, but full change was not verified present - all checked added lines are present present
9/42 [PATCH 09/42] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add AUO partial - subject or partial tree evidence found, but full change was not verified present - all checked added lines are present present
10/42 [PATCH 10/42] FROMLIST: arm64: defconfig: Enable RPi touchscreen V2 missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 95dddbe5c53f2970faed1ef2ee9a6a0199b65784 present
11/42 [PATCH 11/42] UPSTREAM: dt-bindings: display/panel: ilitek,ili9881c: present - all checked added lines are present skipped - not checked because qcom-next already contains the change present
12/42 [PATCH 12/42] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add RPi missing - no subject, patch-id, or full tree-content match found present - all checked added lines are present present
13/42 [PATCH 13/42] FROMLIST: arm64: defconfig: Enable Waveshare DSI panel missing - no subject, patch-id, or full tree-content match found present - all checked added lines are present present
14/42 [PATCH 14/42] QCLINUX: prune.config: Enable the Goodix touchscreen missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 7f16976c8bda3779eb096a181189ccea55e52238 present
15/42 [PATCH 15/42] BACKPORT: dt-bindings: gpio: describe Waveshare GPIO present - exact patch-id match at 8cd19f5 skipped - not checked because qcom-next already contains the change present
16/42 [PATCH 16/42] BACKPORT: gpio: add GPIO controller found on Waveshare present - all checked added lines are present skipped - not checked because qcom-next already contains the change present
17/42 [PATCH 17/42] BACKPORT: dt-bindings: display/panel: himax,hx83102: present - exact patch-id match at 0eb86d3 skipped - not checked because qcom-next already contains the change present
18/42 [PATCH 18/42] BACKPORT: dt-bindings: display/panel: himax,hx8394: present - exact patch-id match at 4a70ba6 skipped - not checked because qcom-next already contains the change present
19/42 [PATCH 19/42] BACKPORT: dt-bindings: display/panel: present - all checked added lines are present skipped - not checked because qcom-next already contains the change present
20/42 [PATCH 20/42] BACKPORT: dt-bindings: dipslay/panel: describe panels present - exact patch-id match at 17b2ab7 skipped - not checked because qcom-next already contains the change present
21/42 [PATCH 21/42] BACKPORT: drm/of: add helper to count data-lanes on a present - exact patch-id match at a8c56e0 skipped - not checked because qcom-next already contains the change present
22/42 [PATCH 22/42] BACKPORT: drm/panel: himax-hx83102: Add support for present - exact patch-id match at cc72a47 skipped - not checked because qcom-next already contains the change present
23/42 [PATCH 23/42] BACKPORT: drm/panel: himax-hx83102: Add support for DSI present - exact patch-id match at 987170d skipped - not checked because qcom-next already contains the change present
24/42 [PATCH 24/42] BACKPORT: drm/panel: himax-hx83102: support Waveshare present - exact patch-id match at 1af0fea skipped - not checked because qcom-next already contains the change present
25/42 [PATCH 25/42] BACKPORT: drm/panel: himax-hx8394: set present - exact patch-id match at dd0d0a4 skipped - not checked because qcom-next already contains the change present
26/42 [PATCH 26/42] BACKPORT: drm/panel: himax-hx8394: simplify present - exact patch-id match at 917e888 skipped - not checked because qcom-next already contains the change present
27/42 [PATCH 27/42] BACKPORT: drm/panel: himax-hx8394: support Waveshare present - exact patch-id match at c3b595b skipped - not checked because qcom-next already contains the change present
28/42 [PATCH 28/42] BACKPORT: drm/panel: jadard-jd9365da-h3: use present - exact patch-id match at 0a26b74 skipped - not checked because qcom-next already contains the change present
29/42 [PATCH 29/42] BACKPORT: drm/panel: jadard-jd9365da-h3: Use present - exact patch-id match at c8fd04c skipped - not checked because qcom-next already contains the change present
30/42 [PATCH 30/42] BACKPORT: drm: panel: jd9365da: Use present - exact patch-id match at 388df23 skipped - not checked because qcom-next already contains the change present
31/42 [PATCH 31/42] BACKPORT: drm/panel: jd9365da: Support for Anbernic present - exact patch-id match at ce76a26 skipped - not checked because qcom-next already contains the change present
32/42 [PATCH 32/42] BACKPORT: drm/panel: panel-jadard-jd9365da-h3: support present - exact patch-id match at 5c19c4e skipped - not checked because qcom-next already contains the change present
33/42 [PATCH 33/42] BACKPORT: drm/panel: jadard-jd9365da-h3: support present - exact patch-id match at eb01968 skipped - not checked because qcom-next already contains the change present
34/42 [PATCH 34/42] BACKPORT: drm/panel: jadard-jd9365da-h3: set present - exact patch-id match at b55a4b5 skipped - not checked because qcom-next already contains the change present
35/42 [PATCH 35/42] BACKPORT: drm/panel: jadard-jd9365da-h3: support present - exact patch-id match at ba362fb skipped - not checked because qcom-next already contains the change present
36/42 [PATCH 36/42] BACKPORT: drm/panel: jadard-jd9365da-h3: support present - exact patch-id match at 5a7770a skipped - not checked because qcom-next already contains the change present
37/42 [PATCH 37/42] BACKPORT: drm/panel: jadard-jd9365da-h3: support present - exact patch-id match at 13414cf skipped - not checked because qcom-next already contains the change present
38/42 [PATCH 38/42] BACKPORT: drm/panel: add devm_drm_panel_add() helper present - exact patch-id match at e43a8e3 skipped - not checked because qcom-next already contains the change present
39/42 [PATCH 39/42] BACKPORT: drm/panel: add driver for Waveshare 8.8" DSI present - exact patch-id match at 07853e9 skipped - not checked because qcom-next already contains the change present
40/42 [PATCH 40/42] BACKPORT: dt-bindings: display: waveshare,dsp2dpi: present - exact patch-id match at 7fd2875 skipped - not checked because qcom-next already contains the change present
41/42 [PATCH 41/42] BACKPORT: drm/bridge: waveshare-dsi: support DSI LCD present - exact patch-id match at 17394e0 skipped - not checked because qcom-next already contains the change present
42/42 [PATCH 42/42] FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add missing - no subject, patch-id, or full tree-content match found present - all checked added lines are present present

Final Status

overall_status: PARTIAL
present_commits: 38/42
partial_commits: 4/42
missing_commits: 0/42
topics_checked_for_commits: 14/42
final_summary: PR present in qcom-next/topics: Partial - 4/42 commit(s) only have partial integration evidence

@qlijarvis

Copy link
Copy Markdown

PR #1330 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ❌ 1 commit with 65 errors + 57 warnings (indentation); 7 commits with minor warnings
dt-binding-check ✅ All binding validations passed
dtb-check ❌ Pre-existing tree issues (GPI-DMA, ethernet, IMEM); 3 new panel binding errors
sparse-check ✅ No sparse warnings
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ 5 Revert commits missing prefix; 1 QCLINUX prefix; 3 content mismatches
tag-check ❌ 5 Revert commits missing required prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1330 - Display panel support updates for Shikra
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/39945583440

Checker Result Summary
checkpatch ❌ 1 commit with 65 errors + 57 warnings (indentation); 7 commits with minor warnings
dt-binding-check ✅ All binding validations passed
dtb-check ❌ Pre-existing tree issues (GPI-DMA, ethernet, IMEM); 3 new panel binding errors
sparse-check ✅ No sparse warnings
check-uapi-headers ✅ No UAPI changes
check-patch-compliance ❌ 5 Revert commits missing prefix; 1 QCLINUX prefix; 3 content mismatches
tag-check ❌ 5 Revert commits missing required prefix

❌ checkpatch — Code Style Violations

Root cause: Commit 0e8b9be99362 (Revert of HDMI bridge regulators patch) has 65 indentation errors and 57 warnings due to spaces instead of tabs.

Failure details:

Commit 0e8b9be99362 ("Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: Rename HDMI bridge regulators and pinctrl"")
ERROR: code indent should use tabs where possible (×65)
WARNING: please, no spaces at the start of a line (×57)
#197: FILE: arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts:585:
+        regulator-allow-set-load;
0e8b9be993620a13c0c0fc2df88ca6cb9ba71885 total: 65 errors, 57 warnings, 0 checks, 193 lines checked

Additional warnings (non-blocking):

  • 7 commits with minor warnings:
    • 54fd50285a2f: Missing Kconfig help paragraph (1 warning)
    • 5d611b4ad628: Undocumented DT strings holitech,htf065h045 and vendor holitech (2 warnings)
    • 3f51bba376ac: Undocumented DT strings anbernic,rg-ds-display-* (2 warnings)
    • 05aca4b1fef8: Undocumented DT string taiguanck,xti05101-01a and vendor taiguanck (2 warnings)
    • cca54ec4426b, fa0af76f48d1, 4041f5fd7811: msleep < 20ms warnings (informational)

Fix:

git rebase -i <base_sha>
# Mark commit 0e8b9be99362 as 'edit'
# Convert spaces to tabs in arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
sed -i 's/^        /\t\t/' arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
git add arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
git commit --amend --no-edit
git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 113239da311a..1b0231d553d4

❌ dtb-check — DTB Validation Errors

Root cause: 3 new panel binding errors introduced by this PR; multiple pre-existing tree issues also reported.

New errors introduced by this PR:

shikra-iqs-evk-dlc-panel.dtb: panel@0 (dlc,dlc0697): 'backlight' does not match any of the regexes: '^pinctrl-[0-9]+$'

shikra-iqs-evk-raspberrypi-dsi-7inch.dtb: panel@0 (raspberrypi,dsi-7inch): 'port' does not match any of the regexes: '^pinctrl-[0-9]+$'
  from schema $id: http://devicetree.org/schemas/display/panel/ilitek,ili9881c.yaml

Pre-existing tree issues (not caused by this PR):

dma-controller@4a00000 (qcom,shikra-gpi-dma): interrupts: [[0, 511, 4, 0], ...] is too long
ethernet@5d00000 (qcom,shikra-ethqos): False schema does not allow True
ethernet@5d00000 (qcom,shikra-ethqos): Unevaluated properties are not allowed (...)
sram@c11e000 (qcom,shikra-imem): pil-sram@94c:compatible: ['qcom,pil-reloc-info'] does not contain items matching the given schema

Fix for new errors:

The panel bindings (dlc,dlc0697 and raspberrypi,dsi-7inch) are using additionalProperties: false or unevaluatedProperties: false but don't declare backlight and port properties. These properties are valid and commonly used in panel nodes.

Option 1: Update the panel binding YAML files to allow these properties:

# In Documentation/devicetree/bindings/display/panel/dlc,dlc0697.yaml
properties:
  backlight:
    description: phandle of the backlight device
    $ref: /schemas/types.yaml#/definitions/phandle

# In Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.yaml
properties:
  port:
    $ref: /schemas/graph.yaml#/properties/port
    description: DSI input port

Option 2: If these bindings inherit from panel-common.yaml, ensure the inheritance is correct and unevaluatedProperties: false is used instead of additionalProperties: false.

Reproduce locally:

make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-iqs-evk-dlc-panel.dtb
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/shikra-iqs-evk-raspberrypi-dsi-7inch.dtb

❌ check-patch-compliance — Prefix and Content Mismatch Failures

Root cause: 5 Revert commits lack required prefix; 1 QCLINUX commit (known limitation); 3 commits have content differences from upstream links.

Failure 1: Missing prefix on Revert commits (×5)

Checking commit: Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS panel overlay support"
Commit summary does not start with a required prefix

Checking commit: Revert "PENDING: arm64: dts: qcom: shikra: Add DLC panel overlay support"
Commit summary does not start with a required prefix

Checking commit: Revert "PENDING: arm64: dts: qcom: shikra: Add DSI HDMI overlay support"
Commit summary does not start with a required prefix

Checking commit: Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: Rename HDMI bridge regulators and pinctrl"
Commit summary does not start with a required prefix

Checking commit: Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support"
Commit summary does not start with a required prefix

Fix: Add a prefix before Revert:

git rebase -i <base_sha>
# For each Revert commit, mark as 'reword' and change subject to:
UPSTREAM: Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS panel overlay support"
# or
FROMLIST: Revert "PENDING: arm64: dts: qcom: shikra: Add DLC panel overlay support"

Failure 2: QCLINUX prefix (known limitation)

Checking commit: QCLINUX: prune.config: Enable the Goodix touchscreen driver
Commit summary does not start with a required prefix

This is a known checker limitation — QCLINUX: is not in the allowed prefix list (FROMLIST, FROMGIT, UPSTREAM, BACKPORT). Vendor-only commits will always fail this check. No fix available; this is expected behavior.

Failure 3: Content mismatch (×3)

Checking commit: FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support
Change is different from the one mentioned in Link

Checking commit: BACKPORT: drm/panel: jadard-jd9365da-h3: support Waveshare WXGA DSI panels
Change is different from the one mentioned in Link

Checking commit: BACKPORT: drm/panel: add driver for Waveshare 8.8" DSI TOUCH-A panel
Change is different from the one mentioned in Link

Analysis required: Fetch the upstream patches and compare:

# For each commit, extract the Link: URL from the commit message and fetch:
b4 am --single-message -C -l -3 <link-url> -o /tmp/upstream.mbx
git format-patch -1 <commit-sha> --stdout > /tmp/pr.patch
# Compare the diff hunks (ignoring context line shifts):
diff <(grep -E '^[+-][^+-]' /tmp/pr.patch) <(grep -E '^[+-][^+-]' /tmp/upstream.mbx)

If differences are legitimate adaptations (e.g., backport adjustments, conflict resolution), document them in the commit message. If differences are unintended, revert and re-apply the upstream patch cleanly.


❌ tag-check — Missing Subject Prefix

Root cause: 5 Revert commits do not start with a required prefix tag.

Applies to: All branches except qcom-next and qcom-next-staging require every commit subject to start with one of: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, WORKAROUND:.

Failing commits:

Commit 393d652dc469: Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS panel overlay support"
Commit 228129c9eb80: Revert "PENDING: arm64: dts: qcom: shikra: Add DLC panel overlay support"
Commit 0900232c2cb1: Revert "PENDING: arm64: dts: qcom: shikra: Add DSI HDMI overlay support"
Commit 0e8b9be99362: Revert "PENDING: arm64: dts: qcom: shikra-iqs-evk: Rename HDMI bridge regulators and pinctrl"
Commit 9e86f08267a1: Revert "FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support"

Fix:

git rebase -i <base_sha>
# Mark each Revert commit as 'reword'
# Change subject to include prefix:
UPSTREAM: Revert "PENDING: arm64: dts: qcom: shikra: Add LVDS panel overlay support"
FROMLIST: Revert "PENDING: arm64: dts: qcom: shikra: Add DLC panel overlay support"
# etc.

Choose the correct prefix based on whether the revert itself has been posted upstream (FROMLIST:), merged upstream (UPSTREAM:), or is vendor-only (QCLINUX:).


Verdict

Fix 9 blockers before merge:

  1. checkpatch: Fix indentation errors in commit 0e8b9be99362 (convert spaces to tabs)
  2. dtb-check: Update panel bindings to allow backlight and port properties (3 errors)
  3. check-patch-compliance + tag-check: Add prefix to 5 Revert commits (e.g., UPSTREAM: Revert "...")
  4. check-patch-compliance: Investigate and document 3 content mismatches with upstream links

Non-blocking issues:

  • 7 commits with minor checkpatch warnings (undocumented DT strings, msleep < 20ms) — acceptable for merge
  • 1 QCLINUX prefix failure — known checker limitation, no fix available
  • Pre-existing dtb-check errors (GPI-DMA, ethernet, IMEM) — not caused by this PR

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.

7 participants