Lt9611uxd DSI HDMI Bridge for Shikra IQS

[mohitdsor]

Lt9611uxd DSI HDMI Bridge for Shikra IQS
CRs-Fixed: 4552827

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

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

[qlijarvis]

PR #841 — validate-patch

PR: #841

Verdict	Issues	Detailed Report
❌	0	Full report

Final Summary

1. Lore link present: No — no lore.kernel.org link found in patch; no commit message present
2. Lore link matches PR commits: N/A — no lore link to compare against; patch is a raw diff without commit metadata
3. Upstream patch status: Unknown — cannot determine without lore link; patch combines multiple unrelated changes that likely have different upstream status
4. PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #841 (title unknown - no metadata available)
Upstream commit: N/A
Verdict: ❌ FAIL

Commit Message

Check	Status	Note
Subject matches upstream	❌	No commit message present in patch
Body preserves rationale	❌	No commit message present in patch
Fixes tag present/correct	❌	No commit message present in patch
Authorship preserved	❌	No commit message present in patch
Backport note (if applicable)	N/A	No commit message present in patch

Diff

File	Status	Notes
354 files changed	❌	Raw diff without commit metadata; appears to combine multiple unrelated changes
Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml	⚠️	Adds new compatible strings (lt9611c, lt9611ex, lt9611uxd)
Documentation/gpu/drm-kms.rst	⚠️	Mass rename: drm_atomic_state → drm_atomic_commit
Documentation/gpu/todo.rst	⚠️	Updates TODO item about renaming drm_atomic_state
MAINTAINERS	⚠️	Adds new LONTIUM LT9611C entry
arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts	⚠️	Adds HDMI connector and LT9611 regulators
arch/arm64/configs/defconfig	⚠️	Config changes
drivers/gpu/drm/* (300+ files)	⚠️	Mass rename: drm_atomic_state → drm_atomic_commit throughout DRM subsystem

Issues

Critical Issues:

1. No lore.kernel.org link found — The PR patch contains no commit message and no Link: tag pointing to lore.kernel.org. According to kernel development practices, all patches must reference their upstream source.

2. No commit message metadata — The patch is a raw diff without From:, Date:, Subject:, or commit body. This violates kernel commit message requirements.

3. Multiple unrelated changes combined — The patch appears to combine at least three distinct changes:

   • A massive DRM subsystem-wide refactoring (drm_atomic_state → drm_atomic_commit) touching 300+ files
   • LT9611 bridge driver binding updates (new compatible strings)
   • Qualcomm Shikra board DTS additions (HDMI connector, regulators)
   • MAINTAINERS entry addition

4. Missing integration evidence — According to integration_presence_report.md, the commit has only "partial" presence in qcom-next/topics. Specifically, 161 added lines are missing from qcom-next, including:

   • Documentation/gpu/todo.rst changes about renaming drm_atomic_commit
   • MAINTAINERS entry for LONTIUM LT9611C

Structural Issues:

5. No commit prefix — Without a commit message, there's no UPSTREAM:, FROMLIST:, BACKPORT:, or QCLINUX: prefix to indicate the patch's origin and status.

6. No Signed-off-by chain — Required for all kernel contributions per DCO (Developer Certificate of Origin).

Verdict

Do not merge. This PR fails validation on multiple critical criteria:

1. Missing lore link — Cannot validate against upstream source
2. Missing commit message — Violates kernel commit requirements
3. Combining unrelated changes — Should be split into separate, logically independent commits
4. Incomplete integration — Missing lines indicate the change is not fully present in qcom-next

Required actions before merge:

1. Split this into separate commits:

   • One commit for the DRM atomic_state → atomic_commit refactoring (if this is intended to be included)
   • One commit for LT9611 binding updates
   • One commit for Shikra DTS additions
   • One commit for MAINTAINERS update

2. For each commit, add proper commit message with:

   • Descriptive subject line with appropriate prefix (UPSTREAM:, FROMLIST:, BACKPORT:, or QCLINUX:)
   • Commit body explaining the change rationale
   • Link: tag pointing to lore.kernel.org (for upstream/fromlist patches)
   • Signed-off-by: chain

3. Verify each commit's presence in qcom-next or explain why it's not there yet

4. If the DRM refactoring is unintentional, remove it entirely — this appears to be a massive upstream change that should not be in a vendor tree without clear justification

Final Summary

1. Lore link present: No — no lore.kernel.org link found in patch; no commit message present
2. Lore link matches PR commits: N/A — no lore link to compare against; patch is a raw diff without commit metadata
3. Upstream patch status: Unknown — cannot determine without lore link; patch combines multiple unrelated changes that likely have different upstream status
4. PR present in qcom-next/topics: Partial — 161/3354 added lines missing from qcom-next, including Documentation/gpu/todo.rst changes and MAINTAINERS entry; indicates incomplete or incorrect integration

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

Commit	Subject	qcom-next	topics	Final
1/1	``	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

Final Status

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

[qlijarvis]

PR #841 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	2 commits: 67 errors + 58 warnings (c5e2179), email mismatch (2 commits)
dt-binding-check	✅	Passed
dtb-check	✅	Passed
sparse-check	✅	Passed
check-uapi-headers	✅	Passed
check-patch-compliance	❌	4 commits: b4 fetch failed (1), content mismatch (3), author mismatch (2)
tag-check	✅	All commits have valid prefixes (BACKPORT:/FROMLIST:)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #841 - Add Lontium LT9611C MIPI DSI to HDMI bridge driver support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/29747685578
Target Branch: qcom-6.18.y (subject prefix check mandatory)

Checker	Result	Summary
checkpatch	❌	2 commits: 67 errors + 58 warnings (c5e2179), email mismatch (2 commits)
dt-binding-check	✅	Passed
dtb-check	✅	Passed
sparse-check	✅	Passed
check-uapi-headers	✅	Passed
check-patch-compliance	❌	4 commits: b4 fetch failed (1), content mismatch (3), author mismatch (2)
tag-check	✅	All commits have valid prefixes (BACKPORT:/FROMLIST:)

---

❌ checkpatch

Root cause: Commit c5e2179 has 67 indentation errors (spaces instead of tabs) and 58 warnings; 2 commits have From:/Signed-off-by email mismatch.

Failure details:

Commit c5e2179 ("FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support"):

ERROR: code indent should use tabs where possible
#40: FILE: arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts:32:
+                compatible = "hdmi-connector";

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

[... 67 errors, 58 warnings total ...]

WARNING: From:/Signed-off-by: email address mismatch: 
  'From: Mohit Dsor <mdsor@oss.qualcomm.com>' != 
  'Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>'

c5e21795e4660fcd60c43259a8803dd0424e286b total: 67 errors, 58 warnings, 0 checks, 146 lines checked

Commit 81ea68c ("FROMLIST: arm64: defconfig: Enable LT9611C bridge driver"):

WARNING: From:/Signed-off-by: email address mismatch: 
  'From: Mohit Dsor <mdsor@oss.qualcomm.com>' != 
  'Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>'

81ea68c2c0206e13b0088a64dff31b0ded9975f8 total: 0 errors, 1 warnings, 0 checks, 7 lines checked

Fix:

1. Indentation errors (c5e2179): The DTS file uses spaces instead of tabs. Run:

   git rebase -i 94c6f41183c5b71f0cd81ca0c46bb17c3c1efa4e  # mark c5e21795e466 as 'edit'
   # Convert spaces to tabs in arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
   sed -i 's/^        /\t/g' 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

2. Email mismatch (both commits): The From: line uses mdsor@oss.qualcomm.com but Signed-off-by: uses mohit.dsor@oss.qualcomm.com. Fix by amending the Signed-off-by: to match the From: email:

   git rebase -i 94c6f41183c5b71f0cd81ca0c46bb17c3c1efa4e
   # For each commit (c5e21795e466 and 81ea68c2c020), mark as 'edit'
   # Edit commit message to change:
   #   Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
   # to:
   #   Signed-off-by: Mohit Dsor <mdsor@oss.qualcomm.com>
   git commit --amend
   git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES \
  --git 94c6f41183c5b71f0cd81ca0c46bb17c3c1efa4e..a1d0ff09cc775a3d74552593d364eba4f8167d3c

---

❌ check-patch-compliance

Root cause: 4 commits have upstream link/content/author issues: 1 b4 fetch failure, 3 content mismatches, 2 author mismatches.

Failure details:

Commit 1 ("BACKPORT: drm/bridge: add next_bridge pointer to struct drm_bridge"):

Something seems wrong with the provided link. Please verify it
Try below command to run locally-
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20251201-thick-jasmine-oarfish-1eceb0@houat/
https://patch.msgid.link/20251216-drm-bridge-alloc-getput-drm_of_find_bridge-v3-6-b5165fab8058@bootlin.com

→ The Link: tag in the commit message points to an invalid or inaccessible lore URL. The checker cannot fetch the upstream patch with b4.

Commit 2 ("BACKPORT: drm/bridge: refactor HDMI InfoFrame callbacks"):

Change is different from the one mentioned in Link
Author mismatch:
  Original author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
  Commit author : Mohit Dsor <mdsor@oss.qualcomm.com>

→ The patch content differs from the upstream lore patch, and the commit author is not the original author.

Commit 4 ("BACKPORT: drm: Rename struct drm_atomic_state to drm_atomic_commit"):

Change is different from the one mentioned in Link
Author mismatch:
  Original author: Maxime Ripard <mripard@kernel.org>
  Commit author : Mohit Dsor <mdsor@oss.qualcomm.com>

→ Same issues: content mismatch and author mismatch.

Commit 14 ("FROMLIST: arm64: dts: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support"):

Change is different from the one mentioned in Link

→ Content mismatch only (no author mismatch for this one).

Fix:

1. b4 fetch failure (Commit 1): Verify the Link: tag in the commit message points to a valid lore.kernel.org URL. If the link is correct but the patch was deleted/moved, update the link. If the link is a PR URL or invalid format, replace it with the correct lore message-ID URL.

2. Author mismatch (Commits 2, 4): These are BACKPORT: commits where the original author is different from the commit author. For backports, the commit author should be the original author, and the person who backported it should be credited with Signed-off-by: or Co-developed-by:. Fix:

   git rebase -i 94c6f41183c5b71f0cd81ca0c46bb17c3c1efa4e
   # For each commit with author mismatch, mark as 'edit'
   git commit --amend --author="Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>"  # for commit 2
   git commit --amend --author="Maxime Ripard <mripard@kernel.org>"  # for commit 4
   # Ensure Mohit Dsor is credited with Signed-off-by:
   git rebase --continue

3. Content mismatch (Commits 2, 4, 14): Fetch the upstream patch with b4 and compare:

   b4 am --single-message -C -l -3 <link-from-commit-message> -o /tmp/upstream.mbx
   git format-patch -1 <commit-sha> --stdout > /tmp/pr-patch.patch
   # Compare the diff sections (ignore context shifts)
   diff <(awk '/^diff/,/^--$/' /tmp/upstream.mbx/*.mbx | grep -E '^[+-][^+-]') \
        <(awk '/^diff/,/^--$/' /tmp/pr-patch.patch | grep -E '^[+-][^+-]')

   • If the difference is only context lines (line numbers shifted) → not a real issue, but the checker cannot distinguish this. Document the adaptation in the commit message.
   • If there are missing hunks → add them.
   • If there are extra hunks → remove them or attribute them separately.
   • If the changes are legitimate adaptations for backporting → document them in the commit message body (e.g., "Adapted for 6.18.y: ...").

Reproduce locally:

cd /path/to/kernel
bash ../kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base 94c6f41183c5b71f0cd81ca0c46bb17c3c1efa4e \
  --head <PR-head-sha>

---

Verdict

3 blockers must be fixed before merge:

1. checkpatch: Fix 67 indentation errors in arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts (spaces → tabs).
2. checkpatch: Fix email mismatch in 2 commits (align Signed-off-by: with From: email).
3. check-patch-compliance: Fix author mismatch in 2 BACKPORT commits (set original author as commit author, credit backporter with Signed-off-by:).

Non-blocking issues (should fix but not blockers):

• check-patch-compliance: Investigate content mismatches in 3 commits — if they are legitimate backport adaptations, document them in commit messages; if they are unintended diffs, align with upstream.
• check-patch-compliance: Fix b4 fetch failure for commit 1 (verify Link: URL is valid).