From: Melissa Wen <mwen@igalia.com>
To: airlied@gmail.com, alexander.deucher@amd.com,
christian.koenig@amd.com, harry.wentland@amd.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
simona@ffwll.ch, siqueira@igalia.com, sunpeng.li@amd.com,
tzimmermann@suse.de
Cc: Alex Hung <alex.hung@amd.com>, Simon Ser <contact@emersion.fr>,
Uma Shankar <uma.shankar@intel.com>,
Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>,
Xaver Hugl <xaver.hugl@kde.org>,
Pekka Paalanen <pekka.paalanen@collabora.com>,
Louis Chauvet <louis.chauvet@bootlin.com>,
Matthew Schwartz <matthew.schwartz@linux.dev>,
amd-gfx@lists.freedesktop.org, kernel-dev@igalia.com,
Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Jessica Zhang <jesszhan0024@gmail.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v5 0/6] drm/atomic: track individual colorop updates
Date: Mon, 18 May 2026 13:06:53 +0200 [thread overview]
Message-ID: <4fba5085-07b4-4ccd-b2d3-256b65bef159@igalia.com> (raw)
In-Reply-To: <20260506192633.16066-1-mwen@igalia.com>
On 06/05/2026 21:23, Melissa Wen wrote:
> This series aims to track updates for each individual color operation,
> allowing the driver to react accordingly.
>
> - Patches 1 and 2 make colorop update process more consistent and
> optimized by only keeping colorop states from active color pipelines.
>
> - Patches 3 and 4 make lut1d_interpolation and lut3d_interpolation
> colorops correctly behave as mutable, handling their changes via
> drm_colorop_state.
>
> - Finally, patches 5 and 6 track colorop updates of a given plane color
> pipeline by setting plane `color_mgmt_changed` flag, similar to what
> is done for tracking CRTC color mgmt property changes with CRTC
> `color_mgmt_changed` flag. The flag also tracks when a different color
> pipeline is set to a given plane. That way, the driver can react
> accordingly and update their color blocks.
>
> It also fixes shaper/3D LUT updates when changing night mode settings on
> gamescope with a custom branch that supports `COLOR_PIPELINE`:
> - https://github.com/ValveSoftware/gamescope/pull/2113
Hey, Chaitanya, Alex H. and Harry,
Would you have some time to review this series?
I kept r-b from Harry in the last two patches that fix night mode
persistence on AMD, but they depend on the first four patches that
address Chaitanya's suggestions for optimizing colorop updates by active
pipeline and also make LUT interpolation properties correctly behave as
mutable.
Thanks in advance,
Melissa
>
> v1: https://lore.kernel.org/dri-devel/20260318162348.299807-1-mwen@igalia.com/
> Changes:
> - include linux types for function's bool return type (kernel bot on MSM
> driver)
> - add Harry's r-b tags
>
> v2: https://lore.kernel.org/dri-devel/20260323131942.494217-1-mwen@igalia.com/
> Changes:
> - [NEW] two patches to only consider colorop updates from active color
> pipelines (Chaitanya)
> - [NEW] make lut interpolation properties mutable + Alex H patch for
> kernel docs
> - track lut(1/3)d_interpolation updates (Chaitanya)
> - rebase changes according to new patches
>
> v3: https://lore.kernel.org/dri-devel/20260403135909.214378-1-mwen@igalia.com/
> Changes: rebase on drm-misc-next
>
> v4: https://lore.kernel.org/dri-devel/20260501132527.522320-1-mwen@igalia.com/
> Changes: fix kernel doc (kernel bot)
>
> Melissa Wen
>
> Alex Hung (1):
> drm/colorop: Remove read-only comments from interpolation fields
>
> Melissa Wen (5):
> drm/atomic: only add colorop state from active color pipeline
> drm/atomic: don't set colorop properties of inactive color pipelines
> drm/colorop: make lut(1/3)d_interpolation mutable
> drm/atomic: track individual colorop updates
> drm/amd/display: use plane color_mgmt_changed to track colorop changes
>
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 6 +-
> drivers/gpu/drm/drm_atomic.c | 43 +++++----
> drivers/gpu/drm/drm_atomic_helper.c | 9 +-
> drivers/gpu/drm/drm_atomic_uapi.c | 93 +++++++++++++++----
> drivers/gpu/drm/drm_colorop.c | 16 +++-
> include/drm/drm_atomic.h | 2 +-
> include/drm/drm_atomic_uapi.h | 4 +-
> include/drm/drm_colorop.h | 34 ++++---
> 8 files changed, 136 insertions(+), 71 deletions(-)
>
prev parent reply other threads:[~2026-05-18 11:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 19:23 [PATCH v5 0/6] drm/atomic: track individual colorop updates Melissa Wen
2026-05-06 19:23 ` [PATCH v5 1/6] drm/atomic: only add colorop state from active color pipeline Melissa Wen
2026-05-18 11:42 ` Borah, Chaitanya Kumar
2026-05-06 19:23 ` [PATCH v5 2/6] drm/atomic: don't set colorop properties of inactive color pipelines Melissa Wen
2026-05-18 11:42 ` Borah, Chaitanya Kumar
2026-05-19 12:50 ` Melissa Wen
2026-05-06 19:23 ` [PATCH v5 3/6] drm/colorop: Remove read-only comments from interpolation fields Melissa Wen
2026-05-18 11:42 ` Borah, Chaitanya Kumar
2026-05-06 19:23 ` [PATCH v5 4/6] drm/colorop: make lut(1/3)d_interpolation mutable Melissa Wen
2026-05-18 11:43 ` Borah, Chaitanya Kumar
2026-05-06 19:23 ` [PATCH v5 5/6] drm/atomic: track individual colorop updates Melissa Wen
2026-05-18 11:44 ` Borah, Chaitanya Kumar
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-18 11:06 ` 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=4fba5085-07b4-4ccd-b2d3-256b65bef159@igalia.com \
--to=mwen@igalia.com \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=chaitanya.kumar.borah@intel.com \
--cc=christian.koenig@amd.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=jesszhan0024@gmail.com \
--cc=kernel-dev@igalia.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=louis.chauvet@bootlin.com \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=matthew.schwartz@linux.dev \
--cc=mripard@kernel.org \
--cc=pekka.paalanen@collabora.com \
--cc=robin.clark@oss.qualcomm.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@amd.com \
--cc=tzimmermann@suse.de \
--cc=uma.shankar@intel.com \
--cc=xaver.hugl@kde.org \
/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