From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Add Lontium LT7911EXC eDP to MIPI DSI bridge
Date: Mon, 25 May 2026 22:53:57 +1000 [thread overview]
Message-ID: <review-overall-20260519135816.26996-1-syyang@lontium.com> (raw)
In-Reply-To: <20260519135816.26996-1-syyang@lontium.com>
Overall Series Review
Subject: Add Lontium LT7911EXC eDP to MIPI DSI bridge
Author: syyang@lontium.com
Patches: 3
Reviewed: 2026-05-25T22:53:57.625116
---
This is v10 of a 2-patch series adding support for the Lontium LT7911EXC eDP-to-MIPI-DSI bridge chip. The dt-binding patch (1/2) already has Reviewed-by from Krzysztof Kozlowski and looks clean. The driver patch (2/2) has Reviewed-by from Dmitry Baryshkov and is generally well-structured, following patterns from the existing `lontium-lt9611uxc.c` and `lontium-lt8713sx.c` drivers.
The series has been through significant iteration and the major issues from earlier versions (sleeping in atomic context, firmware loading under lock, uninitialized memory leaks in DSI reads) have been addressed. However, several issues remain, ranging from a correctness bug in firmware error paths to minor style concerns.
**Key issues:**
1. **Firmware error path bug**: `lt7911exc_write_data` is called with the original `fw` but `addr=0`, yet earlier the firmware was padded into a temporary `buffer`. The firmware data written is from the original `fw->data`, but the CRC is computed on the padded `buffer`. If `fw->size < total_size`, the CRC will not match what was actually written to flash.
2. **Redundant `dev_set_drvdata` / `i2c_set_clientdata`**: Both set the same underlying drvdata; the driver uses both `dev_get_drvdata` (sysfs) and `i2c_get_clientdata` (remove), so only `i2c_set_clientdata` is needed.
3. **Missing `regmap_noinc_write`**: Writing firmware blocks to a FIFO register should use `regmap_noinc_write`, not `regmap_raw_write`.
4. **Version read without MCU halt**: Departs from the established pattern in other Lontium drivers without adequate justification.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-25 12:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 13:58 [PATCH v10 0/2] Add Lontium LT7911EXC eDP to MIPI DSI bridge syyang
2026-05-19 13:58 ` [PATCH v10 1/2] dt-bindings: bridge: " syyang
2026-05-25 12:53 ` Claude review: " Claude Code Review Bot
2026-05-19 13:58 ` [PATCH v10 2/2] drm/bridge: " syyang
2026-05-25 12:53 ` Claude review: " Claude Code Review Bot
2026-05-25 12:53 ` Claude Code Review Bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-25 1:05 [PATCH v12 0/2] " syyang
2026-05-25 6:53 ` Claude review: " Claude Code Review Bot
2026-05-22 1:57 [PATCH v11 0/2] " syyang
2026-05-25 9:24 ` Claude review: " Claude Code Review Bot
2026-05-15 8:09 [PATCH v8 0/2] " syyang
2026-05-15 23:43 ` Claude review: " Claude Code Review Bot
2026-05-12 6:40 [PATCH v7 0/2] " syyang
2026-05-16 4:16 ` Claude review: " Claude Code Review Bot
2026-04-30 9:46 [PATCH v4 0/2] " syyang
2026-05-05 0:47 ` Claude review: " Claude Code Review Bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=review-overall-20260519135816.26996-1-syyang@lontium.com \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox