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/amd/display: use plane color_mgmt_changed to track colorop changes
Date: Thu, 04 Jun 2026 12:16:44 +1000	[thread overview]
Message-ID: <review-patch4-20260602215743.914265-5-mwen@igalia.com> (raw)
In-Reply-To: <20260602215743.914265-5-mwen@igalia.com>

Patch Review

**Author:** Melissa Wen

Wires up the new `plane_state->color_mgmt_changed` flag in AMD's display driver, at two critical decision points:

1. **`amdgpu_dm_commit_planes()`** (line 10218): The condition for sending color surface updates to DC now checks `new_plane_state->color_mgmt_changed` in addition to `new_pcrtc_state->color_mgmt_changed`:

   ```c
   if (new_pcrtc_state->color_mgmt_changed || new_plane_state->color_mgmt_changed) {
   ```

   This ensures that when a colorop property changes (e.g., shaper/3D-LUT update for gamescope night mode), the driver actually sends the updated gamma, transfer functions, gamut remap, HDR mult, shaper, 3D LUT, and blend TF to DC.

2. **`should_reset_plane()`** (line 12060–12062): Returns `true` when `new_plane_state->color_mgmt_changed` is set, causing the plane to be removed from and re-added to the DC state. This is the same behavior already triggered by `new_crtc_state->color_mgmt_changed`.

**Verdict:** Correct, minimal, and directly fixes the reported gamescope issue. No issues.

---
Generated by Claude Code Patch Reviewer

  reply	other threads:[~2026-06-04  2:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 21:53 [PATCH v8 0/4] drm/atomic: track individual colorop updates Melissa Wen
2026-06-02 21:53 ` [PATCH v8 1/4] drm/colorop: Remove read-only comments from interpolation fields Melissa Wen
2026-06-04  2:16   ` Claude review: " Claude Code Review Bot
2026-06-02 21:53 ` [PATCH v8 2/4] drm/colorop: make lut(1/3)d_interpolation props correctly behave as mutable Melissa Wen
2026-06-04  2:16   ` Claude review: " Claude Code Review Bot
2026-06-02 21:53 ` [PATCH v8 3/4] drm/atomic: track individual colorop updates Melissa Wen
2026-06-04  2:16   ` Claude review: " Claude Code Review Bot
2026-06-02 21:53 ` [PATCH v8 4/4] drm/amd/display: use plane color_mgmt_changed to track colorop changes Melissa Wen
2026-06-04  2:16   ` Claude Code Review Bot [this message]
2026-06-04  2:16 ` Claude review: drm/atomic: track individual colorop updates Claude Code Review Bot
  -- strict thread matches above, loose matches on Subject: below --
2026-05-25  9:49 [PATCH v7 0/4] " Melissa Wen
2026-05-25  9:50 ` [PATCH v7 4/4] drm/amd/display: use plane color_mgmt_changed to track colorop changes Melissa Wen
2026-05-25 21:18   ` Claude review: " Claude Code Review Bot
2026-05-19 21:09 [PATCH v6 0/6] drm/atomic: track individual colorop updates Melissa Wen
2026-05-19 21:09 ` [PATCH v6 6/6] drm/amd/display: use plane color_mgmt_changed to track colorop changes Melissa Wen
2026-05-25 12:24   ` Claude review: " Claude Code Review Bot
2026-05-06 19:23 [PATCH v5 0/6] drm/atomic: track individual colorop updates Melissa Wen
2026-05-06 19:23 ` [PATCH v5 6/6] drm/amd/display: use plane color_mgmt_changed to track colorop changes Melissa Wen
2026-05-07  3:05   ` Claude review: " Claude Code Review Bot
2026-05-01 13:06 [PATCH v4 0/6] drm/atomic: track colorop changes of a given plane Melissa Wen
2026-05-01 13:06 ` [PATCH v4 6/6] drm/amd/display: use plane color_mgmt_changed to track colorop changes Melissa Wen
2026-05-04 23:26   ` Claude review: " Claude Code Review Bot
2026-03-23 13:15 [PATCH v2 0/2] drm/atomic: track colorop changes of a given plane Melissa Wen
2026-03-23 13:15 ` [PATCH v2 2/2] drm/amd/display: use plane color_mgmt_changed to track colorop changes Melissa Wen
2026-03-24 21: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-patch4-20260602215743.914265-5-mwen@igalia.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