public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Re: [PATCH v3 0/2] Add LT9611C(EX/UXD) DRM bridge driver and device tree
Date: Thu, 23 Apr 2026 10:19:49 +1000	[thread overview]
Message-ID: <review-overall-CAO9ioeVFHn3ARCqL0NJ9jRCJV2P9-Ky2c105iF7EwLUG-cV-QQ@mail.gmail.com> (raw)
In-Reply-To: <CAO9ioeVFHn3ARCqL0NJ9jRCJV2P9-Ky2c105iF7EwLUG-cV-QQ@mail.gmail.com>

Overall Series Review

Subject: Re: [PATCH v3 0/2] Add LT9611C(EX/UXD) DRM bridge driver and device tree
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Patches: 17
Reviewed: 2026-04-23T10:19:49.194403

---

This series adds a DRM bridge driver for the Lontium LT9611C/EX/UXD MIPI DSI-to-HDMI converter chips, along with a dt-bindings update. The driver uses an interesting architecture where commands are sent to an on-chip MCU via a read/write flow protocol rather than directly programming hardware registers. The v3 changelog shows good progress incorporating review feedback (using `devm_drm_bridge_alloc`, HDMI audio helpers, CRC8 library, etc.).

However, there are several significant issues that need to be addressed before this can be merged:

1. **Missing `DRM_BRIDGE_OP_HDMI` flag** — The driver implements AVI, HDMI, and SPD infoframe callbacks but does not set `DRM_BRIDGE_OP_HDMI` (or `DRM_BRIDGE_OP_HDMI_SPD_INFOFRAME`) in `bridge.ops`. Without these flags, the framework will never call those callbacks. The existing lt9611 driver sets these correctly. This also means `vendor`, `product`, `supported_formats`, and `max_bpc` must be set on the bridge.
2. **Buffer overflow in infoframe write functions** — The infoframe callbacks copy `len` bytes from `buffer` into a fixed 16-byte command array without bounds checking. An infoframe can be up to ~31 bytes, overflowing the stack buffer.
3. **Improper error returns** — Several functions return magic values like `-1` or `-2` instead of proper errno codes.
4. **dt-bindings patch uses fullwidth punctuation** and has formatting issues.
5. **`SET_SYSTEM_SLEEP_PM_OPS` is deprecated** — should use `DEFINE_SIMPLE_DEV_PM_OPS`.
6. **Missing `atomic_duplicate_state`/`atomic_reset`** bridge callbacks.
7. **Sysfs firmware upgrade interface** is unusual and needs better justification.

---

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-04-23  0:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20  6:16 [PATCH v3 0/2] Add LT9611C(EX/UXD) DRM bridge driver and device tree syyang
2026-04-20  6:16 ` [PATCH v3 1/2] dt-bindings: bridge: This patch adds new content to the lontium, lt9611.yaml binding file syyang
2026-04-20 11:33   ` [PATCH v3 1/2] dt-bindings: bridge: This patch adds new content to the lontium,lt9611.yaml " Krzysztof Kozlowski
2026-04-20 14:15     ` Krzysztof Kozlowski
2026-04-20 14:18       ` Krzysztof Kozlowski
2026-04-21  3:39         ` 杨孙运
2026-04-23  0:19     ` Claude review: " Claude Code Review Bot
2026-04-20  6:16 ` [PATCH v3 2/2] drm/bridge: This patch add new DRM bridge driver for LT9611C(EX/UXD) chip syyang
2026-04-20 12:18   ` Dmitry Baryshkov
2026-04-21  7:37     ` 杨孙运
2026-04-21 10:48       ` Dmitry Baryshkov
2026-04-22  4:41         ` 杨孙运
2026-04-22 18:56           ` Dmitry Baryshkov
2026-04-23  0:19     ` Claude review: " Claude Code Review Bot
2026-04-20 10:45 ` [PATCH v3 0/2] Add LT9611C(EX/UXD) DRM bridge driver and device tree Dmitry Baryshkov
2026-04-20 11:05   ` 杨孙运
2026-04-21 10:49     ` Dmitry Baryshkov
2026-04-23  0:19   ` Claude Code Review Bot [this message]
2026-04-21  5:09 ` Jingyi Wang
2026-04-21  5:49   ` 杨孙运

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-CAO9ioeVFHn3ARCqL0NJ9jRCJV2P9-Ky2c105iF7EwLUG-cV-QQ@mail.gmail.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