From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/rockchip: dw_dp: Implement out-of-band HPD handling
Date: Tue, 05 May 2026 09:49:47 +1000 [thread overview]
Message-ID: <review-patch7-20260501-synopsys-dw-dp-improvements-v2-7-d7e7f6bac77f@collabora.com> (raw)
In-Reply-To: <20260501-synopsys-dw-dp-improvements-v2-7-d7e7f6bac77f@collabora.com>
Patch Review
This is the largest patch in the series and significantly reworks `dw_dp-rockchip.c`.
**Issue — hardcoded IO addresses for controller identification:**
```c
+static const struct rockchip_dw_dp_plat_data rk3588_dp_plat_data = {
+ .ctrl_ids = {0xfde50000, 0xfde60000},
```
The controller ID is determined by matching the platform resource start address against hardcoded values. This works but is fragile — it should ideally come from the DT (e.g., a `reg` index or an explicit property). This pattern appears in some other Rockchip drivers but is generally considered suboptimal.
**Issue — `dp_dp_rockchip_get_vo_grf()` is a workaround:**
```c
+ /*
+ * Limit this workaround to RK3576 and RK3588, new platforms should
+ * add a VO GRF phandle in the DisplayPort DT node.
+ */
```
The code navigates from the DP node → PHY phandle → PHY's `rockchip,vo-grf` to find the VO GRF. The comment acknowledges this is a workaround. This is acceptable for existing DTs but the DT binding should be updated to add a direct `rockchip,vo-grf` property for future platforms.
**Minor — `#include <linux/hw_bitfield.h>`:** This is a relatively new header. The `FIELD_PREP_WM16_CONST` usage is correct for Rockchip's write-masked GRF registers.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-04 23:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 22:20 [PATCH v2 00/12] Synopsys DisplayPort Controller improvements for Rockchip platforms Sebastian Reichel
2026-04-30 22:20 ` [PATCH v2 01/12] drm/bridge: synopsys: dw-dp: Support unregistering the AUX channel Sebastian Reichel
2026-05-04 23:49 ` Claude review: " Claude Code Review Bot
2026-04-30 22:20 ` [PATCH v2 02/12] drm/rockchip: dw_dp: Release core resources Sebastian Reichel
2026-05-04 23:49 ` Claude review: " Claude Code Review Bot
2026-04-30 22:20 ` [PATCH v2 03/12] drm/bridge: synopsys: dw-dp: Simplify driver data setting Sebastian Reichel
2026-05-04 23:49 ` Claude review: " Claude Code Review Bot
2026-04-30 22:20 ` [PATCH v2 04/12] drm/bridge: synopsys: dw-dp: Support MEDIA_BUS_FMT_FIXED Sebastian Reichel
2026-05-04 23:49 ` Claude review: " Claude Code Review Bot
2026-04-30 22:20 ` [PATCH v2 05/12] drm/bridge: synopsys: dw-dp: Add follow-up bridge support Sebastian Reichel
2026-05-04 23:49 ` Claude review: " Claude Code Review Bot
2026-04-30 22:20 ` [PATCH v2 06/12] drm/bridge: Add out-of-band HPD notify handler Sebastian Reichel
2026-05-04 23:49 ` Claude review: " Claude Code Review Bot
2026-04-30 22:20 ` [PATCH v2 07/12] drm/rockchip: dw_dp: Implement out-of-band HPD handling Sebastian Reichel
2026-05-04 23:49 ` Claude Code Review Bot [this message]
2026-04-30 22:20 ` [PATCH v2 08/12] drm/bridge: synopsys: dw-dp: Support software triggered OOB HPD Sebastian Reichel
2026-05-04 23:49 ` Claude review: " Claude Code Review Bot
2026-04-30 22:20 ` [PATCH v2 09/12] drm/bridge: synopsys: dw-dp: Add Runtime PM support Sebastian Reichel
2026-05-04 23:49 ` Claude review: " Claude Code Review Bot
2026-04-30 22:20 ` [PATCH v2 10/12] drm/rockchip: dw_dp: Add runtime " Sebastian Reichel
2026-05-04 23:49 ` Claude review: " Claude Code Review Bot
2026-04-30 22:20 ` [PATCH RFC v2 11/12] dt-bindings: display: rockchip: dw-dp: fix sound DAI cells Sebastian Reichel
2026-05-04 23:49 ` Claude review: " Claude Code Review Bot
2026-04-30 22:20 ` [PATCH v2 12/12] drm/bridge: synopsys: dw-dp: Add audio support Sebastian Reichel
2026-05-04 23:49 ` Claude review: " Claude Code Review Bot
2026-05-04 23:49 ` Claude review: Synopsys DisplayPort Controller improvements for Rockchip platforms 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-patch7-20260501-synopsys-dw-dp-improvements-v2-7-d7e7f6bac77f@collabora.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