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: drm/bridge: Implement generic USB Type-C DP HPD bridge
Date: Mon, 25 May 2026 21:00:52 +1000	[thread overview]
Message-ID: <review-overall-20260521032854.103-1-kernel@airkyi.com> (raw)
In-Reply-To: <20260521032854.103-1-kernel@airkyi.com>

Overall Series Review

Subject: drm/bridge: Implement generic USB Type-C DP HPD bridge
Author: Chaoyi Chen <kernel@airkyi.com>
Patches: 7
Reviewed: 2026-05-25T21:00:52.011314

---

This series implements a generic USB Type-C DP HPD bridge infrastructure and refactors the Rockchip CDN-DP controller to support multiple bridge/PHY port selection without depending on extcon. The design goal is sound: decouple DP hotplug detection from specific USB-C controller drivers, and allow the CDN-DP controller to work with either of the two combo PHYs on RK3399.

The series has already collected Reviewed-by tags from Heikki Krogerus, Neil Armstrong, Luca Ceresoli, and Heiko Stuebner. The architecture is reasonable, but there are several correctness issues, most notably an **uninitialized variable bug** in patch 5 that could cause a kernel crash, and some logic concerns around the multi-bridge HPD/EDID switching path.

**Key concerns:**
1. Patch 5: `prev_port` used uninitialized — potential NULL-pointer dereference or use of garbage pointer
2. Patch 5: `cdn_dp_switch_port` sets `dp->active = true` but is called from EDID read context, which could leave stale state
3. Patch 5: `cdn_dp_connected_port` changes semantics — the old non-`next_bridge_valid` path now falls through to the `next_bridge_valid` block
4. Patch 1: No error handling for `drm_dp_hpd_bridge_register` failure in bus notifier
5. Patch 4: Condition change in `cdn_dp_probe` may inadvertently filter out valid port configurations

---

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-05-25 11:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  3:28 [PATCH 0/5] drm/bridge: Implement generic USB Type-C DP HPD bridge Chaoyi Chen
2026-05-21  3:28 ` [PATCH 1/5] " Chaoyi Chen
2026-05-25 11:00   ` Claude review: " Claude Code Review Bot
2026-05-21  3:28 ` [PATCH 2/5] drm/bridge: aux: Add drm_aux_bridge_register_from_node() Chaoyi Chen
2026-05-25 11:00   ` Claude review: " Claude Code Review Bot
2026-05-21  3:28 ` [PATCH 3/5] phy: rockchip: phy-rockchip-typec: Add DRM AUX bridge Chaoyi Chen
2026-05-21  9:06   ` Heiko Stuebner
2026-05-25 11:00   ` Claude review: " Claude Code Review Bot
2026-05-21  3:28 ` [PATCH 4/5] drm/rockchip: cdn-dp: Support handle lane info without extcon Chaoyi Chen
2026-05-25 11:00   ` Claude review: " Claude Code Review Bot
2026-05-21  3:28 ` [PATCH 5/5] drm/rockchip: cdn-dp: Add multiple bridges to support PHY port selection Chaoyi Chen
2026-05-25 11:00   ` Claude review: " Claude Code Review Bot
2026-05-25 11:00 ` Claude Code Review Bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-04  9:41 [PATCH v15 0/9] Add Type-C DP support for RK3399 EVB IND board Chaoyi Chen
2026-03-04  9:41 ` [PATCH v15 1/9] drm/bridge: Implement generic USB Type-C DP HPD bridge Chaoyi Chen
2026-03-05  3:37   ` 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-20260521032854.103-1-kernel@airkyi.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