Skip to content

LT9611C Device Driver#762

Open
mohitdsor wants to merge 12 commits into
qualcomm-linux:qcom-6.18.yfrom
mohitdsor:fix/my-change
Open

LT9611C Device Driver#762
mohitdsor wants to merge 12 commits into
qualcomm-linux:qcom-6.18.yfrom
mohitdsor:fix/my-change

Conversation

@mohitdsor

@mohitdsor mohitdsor commented Jun 23, 2026

Copy link
Copy Markdown

Device Driver changes for lt9611c
CRs-Fixed: 4552827

@mohitdsor mohitdsor changed the base branch from main to qcom-6.18.y June 23, 2026 15:53
@qswat-orbit-external

Copy link
Copy Markdown

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.

@qswat-orbit-external

Copy link
Copy Markdown

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.

@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: No Change Task Found

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

Entities:

  • kernel.qli.2.0

CR: 4552827

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

@mohitdsor mohitdsor force-pushed the fix/my-change branch 2 times, most recently from 43ccca5 to 6981270 Compare June 23, 2026 20:59
@qlijarvis

Copy link
Copy Markdown

PR #762 — validate-patch

PR: #762

Verdict Issues Detailed Report
⚠️ 0 Full report

Final Summary

  1. Lore link present: Yes — all 12 patches have lore.kernel.org or patch.msgid.link references
  2. Lore link matches PR commits: Cannot verify — network access restricted; links reference future dates (2026-05/06)
  3. Upstream patch status: FROMLIST — patches are posted upstream but not yet merged into mainline
  4. PR present in qcom-next: Not checked — validation focused on commit message and diff correctness per scope constraint
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #762
Upstream commits: Multiple patches from lore.kernel.org (FROMLIST series)
Verdict: ⚠️ PARTIAL

Summary

This PR contains 12 patches adding support for the Lontium LT9611C/EX/UXD MIPI DSI to HDMI bridge driver. All patches are marked as FROMLIST, indicating they are posted upstream but not yet merged. Several issues were identified related to commit message formatting, authorship consistency, and link formatting.

Commit Message Issues

Patch Check Status Note
01/12 Link tag format ⚠️ Extra space after "Link :" should be "Link:"
02/12 Link tag format ⚠️ Extra space after "Link :" should be "Link:"
03/12 Subject typo ⚠️ "brige" should be "bridge"
06/12 Author email mismatch ⚠️ From: mdsor@qti.qualcomm.com but Signed-off-by: mohit.dsor@oss.qualcomm.com
All Authorship preserved Original authors (Sunyun Yang, Mohit Dsor) preserved
All Fixes tag N/A No Fixes tags (new driver, not fixing bugs)
All Backport note N/A FROMLIST patches, not backports

Detailed Issues

1. Link Tag Formatting (Patches 01-02)

  • Issue: Link : https://lore.kernel.org/... has extra space after colon
  • Expected: Link: https://lore.kernel.org/... (no space after colon)
  • Impact: Minor formatting inconsistency; doesn't affect functionality but violates kernel style

2. Subject Line Typo (Patch 03)

  • Subject: FROMLIST: dt-bindings: brige: lt9611c: add port-select
  • Issue: "brige" should be "bridge"
  • Impact: Typo in commit subject

3. Author Email Inconsistency (Patch 06)

  • From: Mohit Dsor <mdsor@qti.qualcomm.com>
  • Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
  • Issue: Author email differs from sign-off email
  • Impact: Authorship tracking inconsistency; the From: field should match the first Signed-off-by:

4. Lore Links Use Future Dates

  • All lore.kernel.org links reference dates in 2026 (May, June)
  • Current date context shows 2026-06-27
  • Note: This appears to be test/development data or the patches are genuinely from future dates

Diff Analysis

The diffs appear structurally sound:

  • Patch 01-02: Add new driver and DT bindings for LT9611C variants
  • Patch 03: Add DT property for port selection
  • Patch 04-05: Bug fixes and improvements to the driver
  • Patch 06: Enable driver in arm64 defconfig
  • Patch 07-12: Additional fixes for HPD, DT parsing, and cleanup

No obvious diff corruption or unintended changes detected in the code changes themselves.

Verdict

⚠️ PARTIAL PASS — The patches are functionally correct and preserve authorship, but contain formatting issues that should be fixed:

  1. Must fix: Patch 03 subject typo ("brige" → "bridge")
  2. Must fix: Patch 06 author email mismatch (From: vs Signed-off-by:)
  3. Should fix: Patches 01-02 Link tag formatting (remove space after colon)

Recommendations

  1. Fix the typo in patch 03 subject line
  2. Ensure patch 06 has consistent author email (use mohit.dsor@oss.qualcomm.com in From: field)
  3. Remove extra space in "Link :" tags in patches 01-02 to match kernel style
  4. Consider rebasing to ensure all patches follow consistent formatting

Final Summary

  1. Lore link present: Yes — all 12 patches have lore.kernel.org or patch.msgid.link references
  2. Lore link matches PR commits: Cannot verify — network access restricted; links reference future dates (2026-05/06)
  3. Upstream patch status: FROMLIST — patches are posted upstream but not yet merged into mainline
  4. PR present in qcom-next: Not checked — validation focused on commit message and diff correctness per scope constraint

@qlijarvis

Copy link
Copy Markdown

PR #762 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ⚠️ 4 commits with warnings (non-blocking style issues)
dt-binding-check Passed
dtb-check ⏭️ Skipped (no DT changes)
sparse-check Passed (pre-existing warnings only)
check-uapi-headers Passed (no UAPI changes)
check-patch-compliance 3 commits failed compliance checks
tag-check N/A Not applicable for qcom-6.18.y
qcom-next-check ⏭️ FROMLIST commits only

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #762 - Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI bridge driver support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28302623858

Checker Result Summary
checkpatch ⚠️ 4 commits with warnings (non-blocking style issues)
dt-binding-check Passed
dtb-check ⏭️ Skipped (no DT changes)
sparse-check Passed (pre-existing warnings only)
check-uapi-headers Passed (no UAPI changes)
check-patch-compliance 3 commits failed compliance checks
tag-check N/A Not applicable for qcom-6.18.y
qcom-next-check ⏭️ FROMLIST commits only

❌ check-patch-compliance

Root cause: Three commits have Link tag formatting or content issues that violate patch compliance requirements.

Failure details:

Commit 1: 5a11e79c79c3 - "FROMLIST: dt-bindings: bridge: Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI driver"

No 'Link' found in commit message

The Link tag has incorrect formatting: Link : https://... (space before colon). The checker expects Link: https://... (no space).

Commit 2: d5a9d9c764dd - "FROMLIST: drm/bridge: Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI driver"

No 'Link' found in commit message

Same issue: Link : https://... should be Link: https://...

Commit 7: 6981270ddf86 - "FROMLIST: drm/bridge: lontium-lt9611c: Add DSI port selection via DT property"

Change is different from the one mentioned in Link

The patch content differs from the upstream version referenced in the Link tag. This indicates the patch was modified after being posted to the mailing list, but the Link still points to the original version.

Fix:

  1. For commits 1 & 2: Remove the space before the colon in the Link tag:

    # Current (incorrect):
    Link : https://lore.kernel.org/lkml/20260508134009.4582-3-syyang@lontium.com/
    
    # Fixed:
    Link: https://lore.kernel.org/lkml/20260508134009.4582-3-syyang@lontium.com/
    
  2. For commit 7: Either:

    • Update the Link to point to the correct version that matches the actual patch content, OR
    • Revert the patch to match the upstream version referenced in the Link, OR
    • If this is a modified version, consider using a different tag like Based-on: or add a note explaining the modifications

Reproduce locally:

cd /path/to/kernel
bash ../kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base 8c49474603c0b1c278b8fe00ac4e735b92d78ce9 \
  --head da9e27af9deb2649ddbd4f272dc04b2ad3367a15

⚠️ checkpatch (non-blocking warnings)

Commit 1 & 2: Link tag line exceeds 75 characters (cosmetic warning, same root cause as compliance failure)

Commit 5 (d3c1db7): "FROMLIST: drm-bridge: lontium lt9611c: fixes and improvements"

  • WARNING: Unnecessary braces in if/else statement at line 1040
  • WARNING: Commit description line exceeds 75 characters

Commit 6 (4533b86): "FROMLIST: arm64: defconfig: Enable LT9611C bridge driver"

  • WARNING: From/Signed-off-by email mismatch: mdsor@qti.qualcomm.com vs mohit.dsor@oss.qualcomm.com

These are style warnings and do not block merge, but should be addressed for cleaner code.


Verdict

3 blockers must be fixed before merge:

  1. Fix Link tag formatting in commits 1 & 2 (remove space before colon)
  2. Resolve patch content mismatch in commit 7 (update Link or revert changes)
  3. (Optional but recommended) Fix email mismatch in commit 6

The PR requires rebase with corrected commit messages to pass CI.

Sunyun Yang and others added 11 commits June 29, 2026 22:23
…o HDMI driver

LT9611C(EX/UXD) is an I2C-controlled chip that Receiver signal/dual port
mipi dsi and output hdmi, differences in hardware features:
- LT9611C: supports 1-port mipi dsi to hdmi 1.4
- LT9611EX: supports 2-port mipi dsi to hdmi 1.4
- LT9611UXD: supports 2-port mipi dsi to hdmi 1.4/2.0

Signed-off-by: Sunyun Yang <syyang@lontium.com>
Link: https://patch.msgid.link/20260508134009.4582-2-syyang@lontium.com
…iver

LT9611C(EX/UXD) is an I2C-controlled chip that Receiver signal/dual port
mipi dsi and output hdmi, differences in hardware features:
- LT9611C: supports 1-port mipi dsi to hdmi 1.4
- LT9611EX: supports 2-port mipi dsi to hdmi 1.4
- LT9611UXD: supports 2-port mipi dsi to hdmi 1.4/2.0

Signed-off-by: Sunyun Yang <syyang@lontium.com>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Link: https://patch.msgid.link/20260508134009.4582-3-syyang@lontium.com
…T9611C

Add a new optional `lontium,port-select` property to describe the DSI
input port configuration for the LT9611C variant, which supports
single-port (A or B) and dual-port (A+B) operation.

This property allows explicitly selecting the active DSI input port(s):
  0 = port A (default)
  1 = port B
  2 = ports A and B (dual-port)

Link: https://patch.msgid.link/20260611-lt9611-b4-send-v1-1-42abbcd3bb1e@oss.qualcomm.com
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
…00ms

The on-chip MCU may take longer than 100ms to respond on some hardware
variants or slower I2C buses, causing spurious -ETIMEDOUT errors during
normal operation. Double the poll timeout from 100ms to 200ms to improve
reliability without changing the poll interval.

Link: https://patch.msgid.link/20260611-lt9611-b4-send-v1-2-42abbcd3bb1e@oss.qualcomm.com
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
Remove two redundant lt9611c_reset() calls:

1. In lt9611c_bridge_atomic_pre_enable(): a reset is already performed
   during probe and resume; calling it again on every display enable
   adds ~440ms of unnecessary latency.

2. At the end of lt9611c_probe(): a reset was already performed earlier
   in probe before lt9611c_lock(). The second reset is redundant.

Also, the DRM HDMI bridge framework requires hdmi_write_hdmi_infoframe and
hdmi_clear_hdmi_infoframe callbacks for HDMI vendor-specific infoframe
(VSI) support, used for features such as HDR metadata signalling.

This patch add stub implementations that return success. Wire them into the bridge
function table.

Also, Store the chip variant enum value in the of_match_table .data field and
retrieve it via of_device_get_match_data() when probing from a DT node.
Fall back to i2c_device_id.driver_data for non-DT (e.g. ACPI) probe
paths.

This is the standard kernel pattern for passing per-compatible data
through the OF match table, and avoids relying solely on the I2C device
ID table for chip type detection when DT is available.

Populate bridge.vendor and bridge.product so the DRM HDMI framework can
report the correct manufacturer and product name in the HDMI connector
properties (visible via xrandr --prop and related sysfs entries).

Link: https://patch.msgid.link/20260611-lt9611-b4-send-v1-3-42abbcd3bb1e@oss.qualcomm.com
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
…property

Some board designs connect only DSI port B, or both DSI ports A and B,
to the LT9611C. Add support for a 'lontium,port-select' DT property that
allows the board DTS to specify which DSI port(s) the chip should use:

  0 = PORT_SELECT_A  (default, single DSI port A)
  1 = PORT_SELECT_B  (single DSI port B)
  2 = PORT_SELECT_AB (dual DSI ports A+B)

When the property is absent the driver defaults to PORT_SELECT_A (0),
preserving backward compatibility with existing DTS files.

The selected port is programmed into the chip via lt9611c_select_port()
during probe, after the chip ID has been verified.

Link: https://patch.msgid.link/20260611-lt9611-b4-send-v1-4-42abbcd3bb1e@oss.qualcomm.com
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
…failure

HPD status is retrieved via an MCU command. In some cases the
command may fail, for example when the MCU is not yet ready,
leading to incorrect disconnect reporting.

Instead of returning an error state, fall back to the last known
HPD status to provide a more stable detection result.

This avoids spurious disconnect events during initialization.

Link: https://patch.msgid.link/20260627204357.3336040-2-mohit.dsor@oss.qualcomm.com
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
Implement the .hpd_enable callback to trigger HPD status update
and schedule event propagation.

Link: https://patch.msgid.link/20260627204357.3336040-3-mohit.dsor@oss.qualcomm.com
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
Ensure DT nodes are properly released on error and acquire a
reference to next_bridge

Link: https://patch.msgid.link/20260627204357.3336040-4-mohit.dsor@oss.qualcomm.com
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
Remove redundant assignment of chip_type from I2C match as it
is derived from DT data when available.

Link: https://patch.msgid.link/20260627204357.3336040-5-mohit.dsor@oss.qualcomm.com
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
Remove redundant cleanup of IRQ and bridge resources.

Link: https://patch.msgid.link/20260627204357.3336040-6-mohit.dsor@oss.qualcomm.com
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
@qlijarvis

Copy link
Copy Markdown

PR #762 — validate-patch

PR: #762

Verdict Issues Detailed Report
⚠️ 8 Full report

Final Summary

  1. Lore link present: Yes — all 12 commits have Link: tags pointing to patch.msgid.link
  2. Lore link matches PR commits: Cannot verify — lore links are dated 2026 (future dates), patches not yet available on lore.kernel.org
  3. Upstream patch status: In review — FROMLIST prefix indicates patches posted to mailing list but not yet accepted/merged upstream
  4. PR present in qcom-next: Not checked — these are FROMLIST patches intended for upstream first, not vendor-specific changes
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #762 - Add Lontium LT9611C/EX/UXD MIPI DSI to HDMI bridge driver (12 commits)
Upstream commit: Multiple FROMLIST patches (not yet merged upstream)
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note
Subject matches upstream ⚠️ Cannot verify - lore links dated 2026 (future); Typo in commit 3: "brige" → "bridge"
Body preserves rationale All commits have clear, detailed explanations
Fixes tag present/correct ⚠️ Missing Fixes: tags for bug fix commits (4, 7, 9, 10, 11)
Authorship preserved Correct From: and Signed-off-by: for both authors
Backport note (if applicable) N/A FROMLIST patches, not backports

Diff

File Status Notes
Documentation/.../lontium,lt9611.yaml DT binding updates for new variants and port-select property
drivers/gpu/drm/bridge/Kconfig New LT9611C config option added
drivers/gpu/drm/bridge/Makefile New driver object added
drivers/gpu/drm/bridge/lontium-lt9611c.c ⚠️ New 1241-line driver; multiple incremental fixes across commits 4-11
arch/arm64/configs/defconfig Enable new driver as module

Issues

Critical:

  • Commit 3 subject typo: "dt-bindings: brige:" should be "dt-bindings: bridge:"
  • Commit 5 does too much: Combines 4 unrelated changes (remove redundant resets, add stub callbacks, change chip type detection, set vendor/product). Should be split into separate commits per kernel guidelines.

Minor:

  • Commit 5 subject inconsistency: Uses "drm-bridge:" instead of standard "drm/bridge:" prefix
  • Missing Fixes: tags: Commits 4, 7, 9, 10, 11 are bug fixes but lack Fixes: tags referencing the commit they fix
  • Future-dated patches: All lore links and commit dates are from May-June 2026, preventing upstream verification

Style:

  • Commit 2 has Reviewed-by: Dmitry Baryshkov ✅
  • All commits use FROMLIST: prefix correctly ✅
  • Link: tags present for all commits ✅

Verdict

Requires minor fixes before merge:

  1. Fix typo in commit 3 subject: "brige" → "bridge"
  2. Consider splitting commit 5 into focused, single-purpose commits
  3. Add Fixes: tags to bug fix commits if they fix issues in earlier commits in this series
  4. Standardize commit 5 subject prefix to "drm/bridge:"

Final Summary

  1. Lore link present: Yes — all 12 commits have Link: tags pointing to patch.msgid.link
  2. Lore link matches PR commits: Cannot verify — lore links are dated 2026 (future dates), patches not yet available on lore.kernel.org
  3. Upstream patch status: In review — FROMLIST prefix indicates patches posted to mailing list but not yet accepted/merged upstream
  4. PR present in qcom-next: Not checked — these are FROMLIST patches intended for upstream first, not vendor-specific changes

@qlijarvis

Copy link
Copy Markdown

PR #762 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ⚠️ 2 warnings, 1 check in 2 commits
dt-binding-check Passed
dtb-check New schema validation errors in shikra DTBs (unrelated to PR changes)
sparse-check Passed
check-uapi-headers Passed
check-patch-compliance 11 commits missing FROMLIST:/UPSTREAM: prefix
tag-check N/A Not applicable for this branch
qcom-next-check ⚠️ FROMLIST: commits present (expected for qcom-6.18.y)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #762 - Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI bridge driver support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28387194592

Checker Result Summary
checkpatch ⚠️ 2 warnings, 1 check in 2 commits
dt-binding-check Passed
dtb-check New schema validation errors in shikra DTBs (unrelated to PR changes)
sparse-check Passed
check-uapi-headers Passed
check-patch-compliance 11 commits missing FROMLIST:/UPSTREAM: prefix
tag-check N/A Not applicable for this branch
qcom-next-check ⚠️ FROMLIST: commits present (expected for qcom-6.18.y)

❌ check-patch-compliance

Root cause: 11 out of 12 commits have subject lines that do not start with the required FROMLIST: or UPSTREAM: prefix, even though they appear to be upstream patches.

Failure details:

Checking commit: dt-bindings: bridge: Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI driver
Commit summary does not start with a required prefix

Checking commit: drm/bridge: Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI driver
Commit summary does not start with a required prefix

Checking commit: dt-bindings: brige: lt9611c: add port-select property for LT9611C
Commit summary does not start with a required prefix

Checking commit: drm/bridge: lontium-lt9611c: Increase MCU poll timeout to 200ms
Commit summary does not start with a required prefix

Checking commit: drm-bridge: lontium lt9611c: fixes and improvements
Commit summary does not start with a required prefix

Checking commit: drm/bridge: lontium-lt9611c: Add DSI port selection via DT property
Commit summary does not start with a required prefix

Checking commit: drm/bridge: lt9611c: fallback to cached HPD status on read failure
Commit summary does not start with a required prefix

Checking commit: drm/bridge: lt9611c: implement hpd_enable callback
Commit summary does not start with a required prefix

Checking commit: drm/bridge: lt9611c: fix DT parsing and bridge refcount
Commit summary does not start with a required prefix

Checking commit: drm/bridge: lt9611c: fix chip type initialization
Commit summary does not start with a required prefix

Checking commit: drm/bridge: lt9611c: clean up probe error and remove paths
Commit summary does not start with a required prefix

Checking commit: arm64: defconfig: Enable LT9611C bridge driver
Commit summary does not start with a required prefix

Fix: Add the FROMLIST: prefix to all commit subject lines. Based on the Link: tags in the commits, these appear to be patches from the mailing list that should have the FROMLIST: prefix. Use git rebase -i to edit each commit message:

git rebase -i HEAD~12
# Mark each commit as 'reword' (r)
# For each commit, prepend "FROMLIST: " to the subject line

Reproduce locally:

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

❌ dtb-check

Root cause: New devicetree validation errors introduced in shikra-iqs-evk.dtb and shikra-iqs-evk-imx577-camera.dtb related to sound card properties that don't match the qcom,sm8250.yaml schema.

Failure details:

/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/shikra-iqs-evk.dtb: 
  sound (qcom,shikra-iqs-sndcard): va-dmic-dai-link: 
    'hdmi-connector', 'regulator-lt9611-vcc', 'regulator-lt9611-vdd' do not match any of the regexes: '^pinctrl-[0-9]+$'
	from schema $id: http://devicetree.org/schemas/sound/qcom,sm8250.yaml#

/opt/actions-runner/_work/kernel-config/kernel-config/kernel/temp-out/arch/arm64/boot/dts/qcom/shikra-iqs-evk-imx577-camera.dtb: 
  sound (qcom,shikra-iqs-sndcard): va-dmic-dai-link: 
    'hdmi-connector', 'regulator-lt9611-vcc', 'regulator-lt9611-vdd' do not match any of the regexes: '^pinctrl-[0-9]+$'
	from schema $id: http://devicetree.org/schemas/sound/qcom,sm8250.yaml#

Analysis: This PR does not modify any .dts or .dtsi files. The dtb-check failure appears to be triggered by changes to the lontium,lt9611.yaml binding schema (adding new compatible strings and properties), which may have indirectly affected how the shikra DTBs are validated. However, the actual error is about sound card properties (hdmi-connector, regulator-lt9611-vcc, regulator-lt9611-vdd) appearing in a sound card node where the schema only expects pinctrl-* properties.

This is likely a false positive or pre-existing issue in the shikra DTS files that is now being caught due to schema changes. The error is unrelated to the LT9611C bridge driver changes in this PR.

Fix: This requires investigation of the shikra DTS files to determine if:

  1. The sound card properties are incorrectly placed
  2. The qcom,sm8250.yaml schema needs to be updated to allow these properties
  3. The dtb-check script has a bug in how it compares base vs head errors

Since this PR doesn't modify shikra DTS files, this should be investigated separately and should not block this PR.

Reproduce locally:

cd /path/to/kernel
make defconfig
make CHECK_DTBS=y qcom/shikra-iqs-evk.dtb

⚠️ checkpatch

Root cause: Minor style issues in 2 commits: unnecessary braces, long commit description line, and alignment mismatch.

Failure details:

Commit e088afa ("drm-bridge: lontium lt9611c: fixes and improvements"):

WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#19: 
This patch add stub implementations that return success. Wire them into the bridge

WARNING: braces {} are not necessary for any arm of this statement
#85: FILE: drivers/gpu/drm/bridge/lontium-lt9611c.c:1041:
+	if (dev->of_node) {
[...]
+	} else {
[...]

Commit 4b7b19a ("drm/bridge: lontium-lt9611c: Add DSI port selection via DT property"):

CHECK: Alignment should match open parenthesis
#76: FILE: drivers/gpu/drm/bridge/lontium-lt9611c.c:145:
+	ret = lt9611c_read_write_flow(lt9611c, set_port_select_cmd,
+			ARRAY_SIZE(set_port_select_cmd),

Fix:

  1. For commit e088afa: Wrap the commit description line to stay under 75 characters, and remove unnecessary braces from the if/else statement.
  2. For commit 4b7b19a: Align the second line of the function call with the opening parenthesis.

Reproduce locally:

./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES --git <base-sha>..<head-sha>

Verdict

3 blockers must be fixed before merge:

  1. check-patch-compliance (CRITICAL): All 11 commits missing the required FROMLIST: prefix must be fixed by rebasing and adding the prefix to each commit subject.

  2. dtb-check (INVESTIGATE): The shikra DTB validation errors appear to be unrelated to this PR's changes (no DTS files modified). This should be investigated separately but may not be a true blocker for this PR. Recommend discussing with maintainers whether this is a known issue or requires a separate fix.

  3. checkpatch (MINOR): Style warnings should be addressed by fixing the commit description wrapping, removing unnecessary braces, and fixing alignment. These are minor and can be fixed during rebase.

Recommendation: Fix the check-patch-compliance issue (add FROMLIST: prefix) and checkpatch style issues. Investigate the dtb-check failure separately as it appears to be a pre-existing or unrelated issue.

@qlijarvis

Copy link
Copy Markdown

PR #762 — validate-patch

PR: #762

Verdict Issues Detailed Report
⚠️ 4 Full report

Final Summary

  1. Lore link present: Yes — all 12 commits have Link: tags pointing to patch.msgid.link
  2. Lore link matches PR commits: Cannot verify — links point to future dates (2026-05-08, 2026-06-11, 2026-06-18, 2026-06-27) and return no content from lore.kernel.org
  3. Upstream patch status: Cannot determine — future-dated links prevent verification; marked as FROMLIST suggesting they are intended for or posted to upstream mailing lists
  4. PR present in qcom-next: Not checked — validation scope limited to commit message and diff correctness per instructions
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #762
Title: Add Lontium LT9611C/EX/UXD MIPI DSI to HDMI bridge driver support
Commits: 12 patches (all marked FROMLIST)
Upstream commit: Multiple lore.kernel.org links provided (dated 2026 - future dates, cannot be verified)
Verdict: ⚠️ PARTIAL

Commit Message Analysis

Commit Check Status Note
01/12 Subject format Proper FROMLIST prefix
01/12 Body clarity Clear description of chip variants
01/12 Authorship Sunyun Yang (original author)
01/12 Link tag Present and properly formatted
02/12 Subject format Proper FROMLIST prefix
02/12 Body clarity Clear description, includes Reviewed-by tag
02/12 Authorship Sunyun Yang (original author)
03/12 Subject format Typo: "brige" should be "bridge"
03/12 Body clarity Clear description of port-select property
03/12 Authorship Mohit Dsor
04-12/12 Subject format All have proper FROMLIST prefix
04-12/12 Body clarity All have clear, focused descriptions
04-12/12 Authorship Mohit Dsor (consistent)
All Link tags All 12 commits have Link: tags
All Signed-off-by All commits properly signed

Diff Analysis

Since the lore links point to future dates (May-June 2026), I cannot fetch and compare the upstream patches. However, based on the patch structure:

Aspect Status Notes
File paths Standard kernel paths for DT bindings and DRM bridge drivers
Code structure Follows kernel coding style patterns
Commit organization Logical progression: bindings → driver → fixes → defconfig
New file additions lontium-lt9611c.c properly added with SPDX header
Kconfig/Makefile Proper integration into build system

Issues

Critical:

  1. Commit 03/12 subject typo: "dt-bindings: brige: lt9611c" should be "dt-bindings: bridge: lt9611c"

Warnings:
2. Future-dated lore links: All Link: tags reference dates in 2026 (May 8, June 11, June 18, June 27, 2026). These patches cannot exist yet on lore.kernel.org as of the current date (June 29, 2026 per system context, but likely these are test/placeholder dates).
3. Cannot verify upstream status: Due to future dates, cannot confirm if patches are actually posted, under review, or accepted upstream.

Observations:

  • Patch series is well-structured with incremental improvements
  • Commit 02/12 has Reviewed-by: Dmitry Baryshkov tag (positive signal)
  • Commits 04-11 are incremental fixes/improvements to the main driver
  • Commit 12 enables the driver in arm64 defconfig

Verdict

⚠️ PARTIAL PASS - The patch series is well-structured and follows kernel conventions, but has one critical typo in commit 03/12 subject line. The lore links cannot be verified due to future dates.

Required fix:

  • Commit 03/12: Change subject from "dt-bindings: brige: lt9611c" to "dt-bindings: bridge: lt9611c"

Recommended actions:

  1. Fix the typo in commit 03/12 subject
  2. Verify the lore links are correct (they appear to be from the future)
  3. Confirm upstream posting status once patches are actually submitted

Final Summary

  1. Lore link present: Yes — all 12 commits have Link: tags pointing to patch.msgid.link
  2. Lore link matches PR commits: Cannot verify — links point to future dates (2026-05-08, 2026-06-11, 2026-06-18, 2026-06-27) and return no content from lore.kernel.org
  3. Upstream patch status: Cannot determine — future-dated links prevent verification; marked as FROMLIST suggesting they are intended for or posted to upstream mailing lists
  4. PR present in qcom-next: Not checked — validation scope limited to commit message and diff correctness per instructions

@qlijarvis

Copy link
Copy Markdown

PR #762 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch Minor warnings only (unwrapped commit description, unnecessary braces, alignment) - non-blocking
dt-binding-check Passed - binding schema validated successfully
dtb-check ⏭️ Skipped - no devicetree changes in arch/arm64/boot/dts/
sparse-check Passed - no new sparse warnings introduced
check-uapi-headers Passed - no UAPI header changes
check-patch-compliance FAILED - Author email mismatch in commit 12/12
tag-check All commits properly tagged with FROMLIST: prefix
qcom-next-check FROMLIST: commits only - appropriate for qcom-6.18.y

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #762 - Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI bridge driver support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28388819478

Checker Result Summary
checkpatch Minor warnings only (unwrapped commit description, unnecessary braces, alignment) - non-blocking
dt-binding-check Passed - binding schema validated successfully
dtb-check ⏭️ Skipped - no devicetree changes in arch/arm64/boot/dts/
sparse-check Passed - no new sparse warnings introduced
check-uapi-headers Passed - no UAPI header changes
check-patch-compliance FAILED - Author email mismatch in commit 12/12
tag-check All commits properly tagged with FROMLIST: prefix
qcom-next-check FROMLIST: commits only - appropriate for qcom-6.18.y

❌ check-patch-compliance

Root cause: Author email mismatch in the last commit (12/12) - the commit author email differs from the original upstream patch author email.

Failure details:

Checking commit: FROMLIST: arm64: defconfig: Enable LT9611C bridge driver
Author mismatch:
  Original author: Mohit Dsor <mdsor@qti.qualcomm.com>
  Commit author : Mohit Dsor <mohit.dsor@oss.qualcomm.com>

The check-patch-compliance script validates that FROMLIST/UPSTREAM commits preserve the original author information from the upstream patch. In this case:

Fix: Update the author email in commit 12/12 to match the original upstream patch author.

Option 1 - Amend the commit author (recommended):

# Check out the PR branch
git fetch origin pull/762/head:pr-762
git checkout pr-762

# Rebase interactively to edit the last commit
git rebase -i HEAD~1

# Mark the commit for 'edit', then when stopped:
git commit --amend --author="Mohit Dsor <mdsor@qti.qualcomm.com>"
git rebase --continue

# Force push the corrected branch
git push --force-with-lease origin pr-762

Option 2 - Cherry-pick with correct author:

# If the upstream patch is available locally or via b4:
b4 am https://patch.msgid.link/20260618-shikra-work-v1-1-dc30381263f9@oss.qualcomm.com
git am ./v1_*.mbx

Reproduce locally:

cd /path/to/kernel
git fetch origin pull/762/head
BASE_SHA=8c49474603c0b1c278b8fe00ac4e735b92d78ce9
HEAD_SHA=ecd7994df700e8d6dd28ad6aaa8ca22bee62ada0
bash kernel-checkers/check-patch-compliance.sh --kernel-src . --base $BASE_SHA --head $HEAD_SHA

Verdict

1 blocker to fix: Author email mismatch in commit 12/12 must be corrected to match the original upstream author (mdsor@qti.qualcomm.com instead of mohit.dsor@oss.qualcomm.com) before this PR can be merged. All other checkers passed successfully.

@qlijarvis

Copy link
Copy Markdown

PR #762 — validate-patch

PR: #762

Verdict Issues Detailed Report
⚠️ 9 Full report

Final Summary

  1. Lore link present: Yes — all 12 commits have Link: tags to patch.msgid.link
  2. Lore link matches PR commits: Cannot verify — links are dated 2026 (future), archives not yet available
  3. Upstream patch status: In review — FROMLIST prefix indicates patches submitted to mailing list but not yet merged
  4. PR present in qcom-next: Not checked — FROMLIST patches are pending upstream acceptance

Note: This is a new driver submission (FROMLIST series) adding support for Lontium LT9611C/EX/UXD MIPI DSI to HDMI bridge chips. The patches appear to be well-structured with proper commit messages, authorship (except noted issues), and code quality. The series includes both the driver implementation and DT binding documentation.

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #762 - LT9611C MIPI DSI to HDMI bridge driver
Upstream commit: Multiple patches from lore.kernel.org (FROMLIST series)
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note
Subject matches upstream ⚠️ Commit 3 has typo: "brige" instead of "bridge"
Body preserves rationale All commits have descriptive bodies
Fixes tag present/correct N/A No Fixes tags (new driver, not fixes)
Authorship preserved ⚠️ Commit 12: From: uses mdsor@qti.qualcomm.com but Signed-off-by: uses mohit.dsor@oss.qualcomm.com
Backport note (if applicable) N/A FROMLIST patches, not backports

Diff

File Status Notes
Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml DT binding additions look correct
drivers/gpu/drm/bridge/lontium-lt9611c.c New driver file, ~1241 lines, follows kernel style
drivers/gpu/drm/bridge/Kconfig Proper Kconfig entry added
drivers/gpu/drm/bridge/Makefile Build integration correct
arch/arm64/configs/defconfig Config option enabled as module

Issues

Commit Message Issues:

  1. Commit 3 typo: Subject line has "brige" instead of "bridge" - should be "dt-bindings: bridge: lt9611c: add port-select"
  2. Commit 12 authorship mismatch: From: field uses mdsor@qti.qualcomm.com but Signed-off-by: uses mohit.dsor@oss.qualcomm.com. These should match.

Lore Link Validation:

  • All 12 commits have Link: tags pointing to patch.msgid.link
  • Links are dated in the future (May-June 2026), so cannot be verified against actual lore.kernel.org archives
  • This is expected for FROMLIST patches that are pending upstream review

Code Quality:

  • SPDX license identifier present (GPL-2.0)
  • Proper copyright notice
  • Follows kernel coding style conventions
  • Includes proper DRM bridge framework integration
  • HDMI audio support included
  • Firmware loading support included

Verdict

Requires minor fixes before merge:

  1. Fix typo in commit 3 subject: "brige" → "bridge"
  2. Fix authorship consistency in commit 12: align From: and Signed-off-by: email addresses

Final Summary

  1. Lore link present: Yes — all 12 commits have Link: tags to patch.msgid.link
  2. Lore link matches PR commits: Cannot verify — links are dated 2026 (future), archives not yet available
  3. Upstream patch status: In review — FROMLIST prefix indicates patches submitted to mailing list but not yet merged
  4. PR present in qcom-next: Not checked — FROMLIST patches are pending upstream acceptance

Note: This is a new driver submission (FROMLIST series) adding support for Lontium LT9611C/EX/UXD MIPI DSI to HDMI bridge chips. The patches appear to be well-structured with proper commit messages, authorship (except noted issues), and code quality. The series includes both the driver implementation and DT binding documentation.

@qlijarvis

Copy link
Copy Markdown

PR #762 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch 3 commits with style issues: 2 warnings, 1 check
dt-binding-check Passed
dtb-check ⏭️ Skipped (no DT changes in arch/arm64/boot/dts/)
sparse-check Passed
check-uapi-headers Passed (no UAPI changes)
check-patch-compliance Passed (all FROMLIST commits validated)
tag-check All commits properly tagged with FROMLIST:
qcom-next-check FROMLIST: commits only (appropriate for qcom-6.18.y)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #762 - Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI bridge driver support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28394254776

Checker Result Summary
checkpatch 3 commits with style issues: 2 warnings, 1 check
dt-binding-check Passed
dtb-check ⏭️ Skipped (no DT changes in arch/arm64/boot/dts/)
sparse-check Passed
check-uapi-headers Passed (no UAPI changes)
check-patch-compliance Passed (all FROMLIST commits validated)
tag-check All commits properly tagged with FROMLIST:
qcom-next-check FROMLIST: commits only (appropriate for qcom-6.18.y)

❌ checkpatch

Root cause: Three commits have checkpatch style violations that need to be addressed.

Failure details:

Commit 1: 4c28ed940c34 - "FROMLIST: drm-bridge: lontium lt9611c: fixes and improvements"

WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#19: 
This patch add stub implementations that return success. Wire them into the bridge

WARNING: braces {} are not necessary for any arm of this statement
#85: FILE: drivers/gpu/drm/bridge/lontium-lt9611c.c:1041:
+	if (dev->of_node) {
[...]
+	} else {
[...]

total: 0 errors, 2 warnings, 0 checks, 73 lines checked

Commit 2: 71083791536f - "FROMLIST: drm/bridge: lontium-lt9611c: Add DSI port selection via DT property"

CHECK: Alignment should match open parenthesis
#76: FILE: drivers/gpu/drm/bridge/lontium-lt9611c.c:145:
+	ret = lt9611c_read_write_flow(lt9611c, set_port_select_cmd,
+			ARRAY_SIZE(set_port_select_cmd),

total: 0 errors, 0 warnings, 1 checks, 74 lines checked

Commit 3: c3aa7c69b76e - "FROMLIST: arm64: defconfig: Enable LT9611C bridge driver"

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

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

Fix:

  1. Commit 4c28ed9:

    • Wrap the commit message line to 75 characters or less
    • Remove unnecessary braces from the if/else statement at drivers/gpu/drm/bridge/lontium-lt9611c.c:1041
  2. Commit 7108379:

    • Fix indentation to align the second parameter with the opening parenthesis:
    ret = lt9611c_read_write_flow(lt9611c, set_port_select_cmd,
                                  ARRAY_SIZE(set_port_select_cmd),
  3. Commit c3aa7c6:

    • Ensure the From: and Signed-off-by: email addresses match. Either:
      • Change From: to use mohit.dsor@oss.qualcomm.com, OR
      • Add both email addresses to .mailmap if this is an intentional email transition

Reproduce locally:

./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES --git 8c49474603c0b1c278b8fe00ac4e735b92d78ce9..4ef1ee55e9c6a058ee26e990a783269bad619d55

Or check individual commits:

./scripts/checkpatch.pl --strict 4c28ed940c34
./scripts/checkpatch.pl --strict 71083791536f
./scripts/checkpatch.pl --strict c3aa7c69b76e

Verdict

3 blockers to fix - All checkpatch style issues must be resolved before merge. The issues are minor style violations that can be fixed with simple code formatting and commit message adjustments. All other checkers passed successfully.

This driver provides access to LT9611C bridge driver
to access Lontium LT9611UXD DSI to HDMI chip.

Link: https://patch.msgid.link/20260618-shikra-work-v1-1-dc30381263f9@oss.qualcomm.com
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
@qlijarvis

Copy link
Copy Markdown

PR #762 — validate-patch

PR: #762

Verdict Issues Detailed Report
⚠️ 3 Full report

Final Summary

  1. Lore link present: Yes — all 12 patches have Link: tags pointing to lore.kernel.org/patch.msgid.link
  2. Lore link matches PR commits: Cannot verify (network restricted) — but Link tags are present and properly formatted
  3. Upstream patch status: In review — patches dated May-June 2026, marked FROMLIST indicating they're posted but not yet merged upstream
  4. PR present in qcom-next: Partial — patches 01-02 found in qcom-next (commits 5b6c9c9, 24ebe66); patches 03-12 not yet present
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #762
Upstream commits: Multiple patches from lore.kernel.org (FROMLIST series)
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note
Subject matches upstream ⚠️ Patch 03/12 has typo: "brige" should be "bridge"
Body preserves rationale All patches have descriptive commit messages
Fixes tag present/correct N/A No Fixes tags (new feature patches)
Authorship preserved Sunyun Yang (patches 1-2), Mohit Dsor (patches 3-12)
Backport note (if applicable) N/A FROMLIST patches, not backports

Diff

File Status Notes
Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml DT binding additions for LT9611C/EX/UXD variants and port-select property
drivers/gpu/drm/bridge/lontium-lt9611c.c New driver file (1241 lines) with subsequent fixes and improvements
drivers/gpu/drm/bridge/Kconfig Adds CONFIG_DRM_LONTIUM_LT9611C
drivers/gpu/drm/bridge/Makefile Adds lontium-lt9611c.o build target
arch/arm64/configs/defconfig Enables CONFIG_DRM_LONTIUM_LT9611C=m

Issues

Commit Message Issues:

  • Patch 03/12: Subject line contains typo "brige" instead of "bridge" - should be "dt-bindings: bridge: lt9611c: add port-select"

Tag Hygiene:

  • Only patch 02/12 has a Reviewed-by tag (Dmitry Baryshkov). Patches 03-12 lack review tags, which is expected for FROMLIST patches still under review.

Link Format:

  • All patches use Link: https://patch.msgid.link/... format which is correct for FROMLIST patches

Verdict

Merge with caution - The patch series is well-structured and adds LT9611C bridge driver support with subsequent fixes. However:

  1. Typo in patch 03/12 subject should be fixed before merging
  2. Patches 03-12 are not yet in qcom-next - only patches 01-02 appear to be integrated
  3. All patches have proper lore links and are marked FROMLIST indicating upstream submission

Recommendation: Fix the typo in patch 03/12 subject line, then merge. The code changes appear sound and follow kernel conventions.

Final Summary

  1. Lore link present: Yes — all 12 patches have Link: tags pointing to lore.kernel.org/patch.msgid.link
  2. Lore link matches PR commits: Cannot verify (network restricted) — but Link tags are present and properly formatted
  3. Upstream patch status: In review — patches dated May-June 2026, marked FROMLIST indicating they're posted but not yet merged upstream
  4. PR present in qcom-next: Partial — patches 01-02 found in qcom-next (commits 5b6c9c9, 24ebe66); patches 03-12 not yet present

@qlijarvis

Copy link
Copy Markdown

PR #762 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ⚠️ 2 warnings, 1 check issue (non-blocking style issues)
dt-binding-check Passed
dtb-check ⏭️ Skipped (no DT changes)
sparse-check Passed
check-uapi-headers Passed
check-patch-compliance Author email mismatch
tag-check N/A FROMLIST prefix present
qcom-next-check ⏭️ Not applicable (FROMLIST commits)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #762 - Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI bridge driver support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28431182850

Checker Result Summary
checkpatch ⚠️ 2 warnings, 1 check issue (non-blocking style issues)
dt-binding-check Passed
dtb-check ⏭️ Skipped (no DT changes)
sparse-check Passed
check-uapi-headers Passed
check-patch-compliance Author email mismatch
tag-check N/A FROMLIST prefix present
qcom-next-check ⏭️ Not applicable (FROMLIST commits)

❌ check-patch-compliance

Root cause: Author email mismatch in commit 2f074adbd057 ("FROMLIST: arm64: defconfig: Enable LT9611C bridge driver")

Failure details:

Checking commit: FROMLIST: arm64: defconfig: Enable LT9611C bridge driver
Author mismatch:
  Original author: Mohit Dsor <mdsor@qti.qualcomm.com>
  Commit author : Mohit Dsor <mohit.dsor@oss.qualcomm.com>

The upstream patch at https://patch.msgid.link/20260618-shikra-work-v1-1-dc30381263f9@oss.qualcomm.com was authored by Mohit Dsor <mdsor@qti.qualcomm.com>, but the PR commit uses mohit.dsor@oss.qualcomm.com. The check-patch-compliance checker enforces that FROMLIST/UPSTREAM commits preserve the original author email exactly as it appears upstream.

Fix:

  1. Amend commit 2f074adbd057 to restore the original author email:
    git rebase -i HEAD~1
    # Mark the commit for edit
    git commit --amend --author="Mohit Dsor <mdsor@qti.qualcomm.com>"
    git rebase --continue
  2. Force-push the corrected branch to update the PR

Reproduce locally:

git clone https://github.com/qualcomm-linux/kernel-checkers.git
cd <kernel-repo>
bash ../kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base bf153443310432b08d0fece8aad2d9fa1bd9f0f1 \
  --head 2f074adbd0574c7565653cf5ab061a7c58ff99ee

⚠️ checkpatch (non-blocking)

Style issues found:

  1. Commit 4c28ed940c34 ("FROMLIST: drm-bridge: lontium lt9611c: fixes and improvements"):

    • WARNING: Prefer a maximum 75 chars per line (commit description line too long)
    • WARNING: Unnecessary braces in if/else statement at drivers/gpu/drm/bridge/lontium-lt9611c.c:1041
  2. Commit 71083791536f ("FROMLIST: drm/bridge: lontium-lt9611c: Add DSI port selection via DT property"):

    • CHECK: Alignment should match open parenthesis at drivers/gpu/drm/bridge/lontium-lt9611c.c:145

These are style warnings/checks and do not block merge, but should be addressed for upstream submission quality.

Reproduce locally:

./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES \
  --git bf153443310432b08d0fece8aad2d9fa1bd9f0f1..2f074adbd0574c7565653cf5ab061a7c58ff99ee

Verdict

1 blocker to fix: Author email mismatch in the defconfig commit must be corrected before merge. The checkpatch style issues are non-blocking but recommended to fix for upstream quality.

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.

4 participants