From: Melissa Wen <mwen@igalia.com>
To: Dave Airlie <airlied@redhat.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
Harry Wentland <harry.wentland@amd.com>,
sunpeng.li@amd.com, siqueira@igalia.com,
christian.koenig@amd.com, airlied@gmail.com, simona@ffwll.ch,
kernel-dev@igalia.com, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
Maxime Ripard <mripard@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH] drm/amd/display: use plane color_mgmt_changed to track colorop changes
Date: Thu, 27 Aug 2026 12:24:17 +0200 [thread overview]
Message-ID: <22a3be63-ebe9-4334-9f42-73e62f123277@igalia.com> (raw)
In-Reply-To: <CADnq5_OxnaEdNUpC1VQsCgensRYAgFCMeGy3uL5n6mYXqOHV-g@mail.gmail.com>
On 10/08/2026 20:40, Alex Deucher wrote:
> On Fri, Aug 7, 2026 at 8:08 AM Melissa Wen <mwen@igalia.com> wrote:
>> This is a resubmission of d79716401a95 ("drm/amd/display: use plane
>> color_mgmt_changed to track colorop changes") whose change was reverted
>> by 0461ba9a7994 ("Merge tag 'amd-drm-next-7.3-2026-07-02' of
>> https://gitlab.freedesktop.org/agd5f/linux into drm-next") during a
>> merge conflict resolution.
>>
>> Original commit message:
>>
>> ```
>> Ensure the driver tracks changes in any colorop property of a plane
>> color pipeline by using the same mechanism of CRTC color management and
>> update plane color blocks when any colorop property changes. It fixes an
>> issue observed on gamescope settings for night mode which is done via
>> shaper/3D-LUT updates.
>> ```
>>
>> Fixes: 0461ba9a7994 ("Merge tag 'amd-drm-next-7.3-2026-07-02' of https://gitlab.freedesktop.org/agd5f/linux into drm-next")
>> Signed-off-by: Melissa Wen <mwen@igalia.com>
>>
> Acked-by: Alex Deucher <alexander.deucher@amd.com>
Hey Dave,
Can you apply it to drm-next?
This a regression from
https://lists.freedesktop.org/archives/amd-gfx/2026-July/148126.html
And AFAIU drm-misc's branches are not the right place.
Best Regards,
Melissa
>
>
>> ---
>>
>> Hey,
>>
>> I noticed this problem in the resolution of a merge conflict after
>> testing drm-misc-next on SteamDeck with KMS colorop API support and
>> verifying the issue of missing updates in nightlight-mode was back.
>>
>> Let me know what are the right steps to address it.
>>
>> Thanks,
>>
>> Melissa
>>
>> ---
>> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
>> index 67b825cbb88f..d0e612371c8f 100644
>> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
>> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
>> @@ -4202,7 +4202,7 @@ static void amdgpu_dm_commit_planes(struct drm_atomic_commit *state,
>> continue;
>>
>> bundle->surface_updates[planes_count].surface = dc_plane;
>> - if (new_pcrtc_state->color_mgmt_changed) {
>> + if (new_pcrtc_state->color_mgmt_changed || new_plane_state->color_mgmt_changed) {
>> bundle->surface_updates[planes_count].gamma = &dc_plane->gamma_correction;
>> bundle->surface_updates[planes_count].in_transfer_func = &dc_plane->in_transfer_func;
>> bundle->surface_updates[planes_count].gamut_remap_matrix = &dc_plane->gamut_remap_matrix;
>> @@ -6012,6 +6012,10 @@ static bool should_reset_plane(struct drm_atomic_commit *state,
>> if (new_crtc_state->color_mgmt_changed)
>> return true;
>>
>> + /* Plane color pipeline or its colorop changes. */
>> + if (new_plane_state->color_mgmt_changed)
>> + return true;
>> +
>> /*
>> * On zpos change, planes need to be reordered by removing and re-adding
>> * them one by one to the dc state, in order of descending zpos.
>> --
>> 2.53.0
>>
prev parent reply other threads:[~2026-08-27 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 11:56 [PATCH] drm/amd/display: use plane color_mgmt_changed to track colorop changes Melissa Wen
2026-08-07 12:12 ` sashiko-bot
2026-08-10 18:40 ` Alex Deucher
2026-08-27 10:24 ` Melissa Wen [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=22a3be63-ebe9-4334-9f42-73e62f123277@igalia.com \
--to=mwen@igalia.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=kernel-dev@igalia.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@amd.com \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.