From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/rockchip: dw_hdmi_qp: Add support for HDMI overscan compensation
Date: Thu, 04 Jun 2026 12:35:00 +1000 [thread overview]
Message-ID: <review-overall-20260602-hdmi-overscan-v1-0-31f71b817c80@flipper.net> (raw)
In-Reply-To: <20260602-hdmi-overscan-v1-0-31f71b817c80@flipper.net>
Overall Series Review
Subject: drm/rockchip: dw_hdmi_qp: Add support for HDMI overscan compensation
Author: Alexey Charkov <alchark@flipper.net>
Patches: 6
Reviewed: 2026-06-04T12:35:00.723614
---
This is a 2-patch series adding HDMI overscan compensation to the Rockchip dw_hdmi_qp driver. The approach is: (1) plumb pixel margins through `rockchip_crtc_state` so the VOP2 post-compositor scaler can use them instead of hard-coded 100% values, and (2) expose the standard DRM "overscan" TV property on the HDMI connector and convert the single percentage into per-side pixel margins in `atomic_check`.
The overall approach is reasonable and the code is small. There are several issues worth addressing:
**Major concern:** The use of `drm_mode_create_tv_properties_legacy()` is explicitly deprecated. The docstring in the kernel says *"New drivers must use drm_mode_create_tv_properties() instead."* This driver doesn't need analog TV mode selection, so calling the legacy function just to get the overscan property creates a bunch of unnecessary and misleading properties (subconnector, brightness, contrast, flicker reduction, saturation, hue, and the legacy mode selector). Only the overscan property is wanted.
**Moderate concern:** The early-return logic in `atomic_check` has a subtle interaction with margin changes. If the user changes the overscan percentage but the TMDS rate and BPC stay the same, the margins are computed and written to `s->tv_margins`, but `atomic_check` returns 0 without setting `s->output_mode`, `s->output_type`, or `s->output_bpc`. This works because those fields are preserved across state duplicates, but it means the CRTC state is modified without the function explicitly signaling that a modeset-level change occurred. The margins should probably also trigger a mode change to ensure the CRTC re-programs the post-scaler, though in practice `vop2_post_config` may be called on every commit regardless.
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-06-04 2:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 17:00 [PATCH 0/2] drm/rockchip: dw_hdmi_qp: Add support for HDMI overscan compensation Alexey Charkov
2026-06-02 17:00 ` [PATCH 1/2] drm/rockchip: vop2: honor TV margins from CRTC state for " Alexey Charkov
2026-06-04 2:35 ` Claude review: " Claude Code Review Bot
2026-06-02 17:00 ` [PATCH 2/2] drm/rockchip: dw_hdmi_qp: expose "overscan" property Alexey Charkov
2026-06-03 7:55 ` Maxime Ripard
2026-06-03 8:15 ` Alexey Charkov
2026-06-03 13:11 ` Andy Yan
2026-06-04 2:35 ` Claude review: " Claude Code Review Bot
2026-06-04 2:35 ` Claude Code Review Bot [this message]
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-20260602-hdmi-overscan-v1-0-31f71b817c80@flipper.net \
--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