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 19:24:23 +1000 [thread overview]
Message-ID: <review-overall-20260522015735.2833-1-syyang@lontium.com> (raw)
In-Reply-To: <20260522015735.2833-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-25T19:24:23.492649
---
This is v11 of a 2-patch series adding a DRM bridge driver for the Lontium LT7911EXC eDP-to-MIPI-DSI bridge chip. The DT binding (patch 1) has a `Reviewed-by` from Krzysztof Kozlowski and looks clean. The driver (patch 2) has been through significant rework over 11 revisions, with many bug fixes driven by automated review. The overall structure is reasonable, but there are still several issues ranging from correctness bugs to locking concerns and API usage problems that should be addressed before merging.
**Key concerns:**
1. Firmware upgrade worker has error-path goto ordering bugs leading to firmware leaks and use-after-free of `fw` pointer.
2. The `lt7911exc_write_data` function writes through the raw `fw` pointer but the firmware was padded and CRC'd from a copy in `buffer` — the data written to the chip does not match the CRC if `fw->size < FW_SIZE - 4`.
3. Multiple regmap write calls have unchecked return values in the flash programming paths.
4. Locking design has holes — the `upgrade_lock` is released before the erase/write sequence finishes in the sysfs store path, so a concurrent store can race.
5. The sysfs attribute naming violates kernel conventions (should not include the driver name prefix).
6. Use of `drm_bridge_add`/`drm_bridge_remove` instead of `devm_drm_bridge_add`.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-25 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 1:57 [PATCH v11 0/2] Add Lontium LT7911EXC eDP to MIPI DSI bridge syyang
2026-05-22 1:57 ` [PATCH v11 1/2] dt-bindings: bridge: " syyang
2026-05-25 9:24 ` Claude review: " Claude Code Review Bot
2026-05-22 1:57 ` [PATCH v11 2/2] drm/bridge: " syyang
2026-05-25 9:24 ` Claude review: " Claude Code Review Bot
2026-05-25 9:24 ` 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-19 13:58 [PATCH v10 0/2] " syyang
2026-05-25 12:53 ` 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-20260522015735.2833-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