From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/bridge: it66121: Fix display output on DVI monitors
Date: Sat, 16 May 2026 13:19:45 +1000 [thread overview]
Message-ID: <review-overall-20260512132232.333654-1-javierm@redhat.com> (raw)
In-Reply-To: <20260512132232.333654-1-javierm@redhat.com>
Overall Series Review
Subject: drm/bridge: it66121: Fix display output on DVI monitors
Author: Javier Martinez Canillas <javierm@redhat.com>
Patches: 7
Reviewed: 2026-05-16T13:19:45.709854
---
This is a well-motivated 2-patch series fixing a real bug: the it66121 bridge driver unconditionally sets HDMI TX mode and enables AVI infoframes, which breaks display output on DVI monitors. The approach is sound — patch 1 moves the TX mode/infoframe configuration from `.mode_set` to `.atomic_enable` (where `ctx->connector` is available), and patch 2 makes the configuration conditional on `display_info.is_hdmi`.
However, there is a significant issue: **patch 1 does not remove the existing TX mode and AVI infoframe writes from `.mode_set`**. The new `it66121_set_tx_mode()` function added in `.atomic_enable` duplicates the `IT66121_HDMI_MODE_REG` and `IT66121_AVI_INFO_PKT_REG` writes that remain in `it66121_bridge_mode_set()` (lines 796-803 of the current tree). This means both callbacks write these registers, and the `.mode_set` write (which runs first) still unconditionally sets HDMI mode. The fix in patch 2 only changes the new function in `.atomic_enable`, so the `.mode_set` code will still force HDMI mode before `.atomic_enable` overrides it with the correct value. While the final state should be correct (`.atomic_enable` runs after `.mode_set`), this is confusing and fragile — the duplicate writes should be cleaned up.
The series is otherwise clean and correctly addresses the v2 feedback from Maxime.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-16 3:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 13:22 [PATCH v3 0/2] drm/bridge: it66121: Fix display output on DVI monitors Javier Martinez Canillas
2026-05-12 13:22 ` [PATCH v3 1/2] drm/bridge: ite-it66121: Set TX mode in the .atomic_enable callback Javier Martinez Canillas
2026-05-12 14:07 ` Maxime Ripard
2026-05-12 18:54 ` Javier Martinez Canillas
2026-05-13 11:55 ` Maxime Ripard
2026-05-13 12:38 ` Javier Martinez Canillas
2026-05-16 3:19 ` Claude review: " Claude Code Review Bot
2026-05-12 13:22 ` [PATCH v3 2/2] drm/bridge: ite-it66121: Select HDMI or DVI mode based on sink type Javier Martinez Canillas
2026-05-16 3:19 ` Claude review: " Claude Code Review Bot
2026-05-16 3:19 ` Claude Code Review Bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-10 19:14 [PATCH 0/3] drm/bridge: it66121: Fix display output on DVI monitors Javier Martinez Canillas
2026-05-16 6:11 ` 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-20260512132232.333654-1-javierm@redhat.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