From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/amd/display: Refactor amdgpu_dm_crtc_set_vblank
Date: Wed, 25 Mar 2026 07:22:02 +1000 [thread overview]
Message-ID: <review-patch3-20260323202755.315929-4-sunpeng.li@amd.com> (raw)
In-Reply-To: <20260323202755.315929-4-sunpeng.li@amd.com>
Patch Review
Clean refactoring. The split is logical: `amdgpu_dm_crtc_set_vblank()` does the HW interrupt work, `amdgpu_dm_crtc_queue_vblank_work()` handles the PSR/panel optimization work, and the enable/disable wrappers tie them together.
One minor issue: in `amdgpu_dm_crtc_set_vblank()`, the condition changed from `if (enable)` to `if (enable && crtc->enabled)`, but the `crtc->enabled` check was moved to `amdgpu_dm_crtc_enable_vblank()` which returns `-EINVAL` early. So in the non-deferred path, `amdgpu_dm_crtc_set_vblank()` should never be called with `enable=true` and `!crtc->enabled`. But patch 4 calls `amdgpu_dm_crtc_set_vblank(crtc, true)` from `amdgpu_dm_crtc_deferred_enable_vblank()` *without* the `crtc->enabled` guard. That means the `enable && crtc->enabled` check inside `set_vblank` becomes the only guard for the deferred path, which is fine — but it means a deferred enable on an unconfigured CRTC silently succeeds (returns 0) without actually enabling anything. That seems fragile; it might be better to return an error.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-24 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 20:27 [PATCH v2 0/5] drm/vblank: Deferred Enable and Disable sunpeng.li
2026-03-23 20:27 ` [PATCH v2 1/5] drm/vblank: Add drm_crtc_vblank_is_off() helper sunpeng.li
2026-03-24 20:20 ` Mario Limonciello
2026-03-24 21:22 ` Claude review: " Claude Code Review Bot
2026-03-23 20:27 ` [PATCH v2 2/5] drm/vblank: Introduce deferred vblank enable/disable sunpeng.li
2026-03-24 21:22 ` Claude review: " Claude Code Review Bot
2026-03-23 20:27 ` [PATCH v2 3/5] drm/amd/display: Refactor amdgpu_dm_crtc_set_vblank sunpeng.li
2026-03-24 21:22 ` Claude Code Review Bot [this message]
2026-03-23 20:27 ` [PATCH v2 4/5] drm/amd/display: Implement deferred vblanks on IPS platforms sunpeng.li
2026-03-24 21:22 ` Claude review: " Claude Code Review Bot
2026-03-23 20:27 ` [PATCH v2 5/5] drm/vblank: Add some debugging trace events sunpeng.li
2026-03-24 21:22 ` Claude review: " Claude Code Review Bot
2026-03-24 21:22 ` Claude review: drm/vblank: Deferred Enable and Disable Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-02-24 21:26 [PATCH 0/5] " sunpeng.li
2026-02-24 21:26 ` [PATCH 3/5] drm/amd/display: Refactor amdgpu_dm_crtc_set_vblank sunpeng.li
2026-02-27 4:40 ` 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-patch3-20260323202755.315929-4-sunpeng.li@amd.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