From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/i915/dp: Fix link retrain loop on pre-gen8 platforms with DP adapters
Date: Tue, 05 May 2026 10:51:24 +1000 [thread overview]
Message-ID: <review-overall-20260430030846.29373-1-s.mavlenkov@mail.ru> (raw)
In-Reply-To: <20260430030846.29373-1-s.mavlenkov@mail.ru>
Overall Series Review
Subject: drm/i915/dp: Fix link retrain loop on pre-gen8 platforms with DP adapters
Author: bitey <s.mavlenkov@mail.ru>
Patches: 2
Reviewed: 2026-05-05T10:51:24.766213
---
This is a single patch attempting to fix an infinite link retrain loop on pre-gen8 i915 platforms when using DP-to-HDMI protocol converters (specifically a Chrontel CH73111). The commit message is well-written and clearly identifies three contributing root causes in the modern DP link training path. However, the patch has a **critical build-breaking error** and several design-level concerns.
**Severity: The patch will not compile as submitted.**
The approach of gating all three code paths behind `DISPLAY_VER(display) >= 8` is a broad workaround rather than a targeted fix. It effectively disables post-training link monitoring and short-HPD link checks for all pre-gen8 platforms, not just the ones affected by misbehaving adapters. A more surgical fix (e.g., quirking the specific adapter, or using DPCD revision for the `short_pulse` change) would be preferable.
Additionally, the `Signed-off-by` uses the handle "bitey" rather than a real name, which does not satisfy the DCO (Developer Certificate of Origin) requirements for kernel contributions.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-05 0:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 3:08 [PATCH] drm/i915/dp: Fix link retrain loop on pre-gen8 platforms with DP adapters bitey
2026-04-30 7:45 ` Jani Nikula
2026-05-05 0:51 ` Claude Code Review Bot [this message]
2026-05-05 0:51 ` 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-20260430030846.29373-1-s.mavlenkov@mail.ru \
--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