From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: Melissa Wen <mwen@igalia.com>, <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>,
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 1/6] drm/atomic: only add colorop state from active color pipeline
Date: Mon, 18 May 2026 17:12:00 +0530 [thread overview]
Message-ID: <9fca1948-d30d-4c7d-8e8b-a0cb8c5b3ce6@intel.com> (raw)
In-Reply-To: <20260506192633.16066-2-mwen@igalia.com>
On 5/7/2026 12:53 AM, Melissa Wen wrote:
> Instead of adding colorop state of all colorops of a given plane, only
> get those from an active color pipeline of this plane.
>
> Signed-off-by: Melissa Wen <mwen@igalia.com>
>
> ---
> v5: fix kernel-doc for plane_state (kernel bot)
> ---
> drivers/gpu/drm/drm_atomic.c | 39 ++++++++++++++---------------
> drivers/gpu/drm/drm_atomic_helper.c | 9 +++----
> include/drm/drm_atomic.h | 2 +-
> 3 files changed, 23 insertions(+), 27 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c
> index 54bab7e9f935..8eb519673fc5 100644
> --- a/drivers/gpu/drm/drm_atomic.c
> +++ b/drivers/gpu/drm/drm_atomic.c
> @@ -1591,26 +1591,25 @@ drm_atomic_add_affected_planes(struct drm_atomic_state *state,
> if (IS_ERR(plane_state))
> return PTR_ERR(plane_state);
>
> - if (plane_state->color_pipeline) {
> - ret = drm_atomic_add_affected_colorops(state, plane);
> - if (ret)
> - return ret;
> - }
> + ret = drm_atomic_add_affected_colorops(plane_state, plane);
> + if (ret)
> + return ret;
> }
> return 0;
> }
> EXPORT_SYMBOL(drm_atomic_add_affected_planes);
>
> /**
> - * drm_atomic_add_affected_colorops - add colorops for plane
> - * @state: atomic state
> + * drm_atomic_add_affected_colorops - add active colorops for plane
> + * @plane_state: DRM plane state
> * @plane: DRM plane
> *
> * This function walks the current configuration and adds all colorops
> - * currently used by @plane to the atomic configuration @state. This is useful
> - * when an atomic commit also needs to check all currently enabled colorop on
> - * @plane, e.g. when changing the mode. It's also useful when re-enabling a plane
> - * to avoid special code to force-enable all colorops.
> + * currently used by an active color pipeline set for a @plane to the atomic
> + * configuration @state.
nit: The documention sounds a bit wonky to me.
Also s/@state/@plane_state
This is useful when an atomic commit also needs to
> + * check all currently enabled colorop on @plane, e.g. when changing the mode.
> + * It's also useful when re-enabling a plane to avoid special code to
> + * force-enable all colorops.
> *
> * Since acquiring a colorop state will always also acquire the w/w mutex of the
> * current plane for that colorop (if there is any) adding all the colorop states for
> @@ -1622,23 +1621,23 @@ EXPORT_SYMBOL(drm_atomic_add_affected_planes);
> * sequence must be restarted. All other errors are fatal.
> */
> int
> -drm_atomic_add_affected_colorops(struct drm_atomic_state *state,
> +drm_atomic_add_affected_colorops(struct drm_plane_state *plane_state,
> struct drm_plane *plane)
> {
> struct drm_colorop *colorop;
> struct drm_colorop_state *colorop_state;
>
> - WARN_ON(!drm_atomic_get_new_plane_state(state, plane));
> + if (!plane_state || !plane_state->color_pipeline)
> + return 0;
>
> drm_dbg_atomic(plane->dev,
> - "Adding all current colorops for [PLANE:%d:%s] to %p\n",
> - plane->base.id, plane->name, state);
> + "Adding all current active colorops for [PLANE:%d:%s] to %p\n",
> + plane->base.id, plane->name, plane_state->state);
>
> - drm_for_each_colorop(colorop, plane->dev) {
> - if (colorop->plane != plane)
> - continue;
> -
> - colorop_state = drm_atomic_get_colorop_state(state, colorop);
> + for (colorop = plane_state->color_pipeline;
> + colorop;
> + colorop = colorop->next) {
> + colorop_state = drm_atomic_get_colorop_state(plane_state->state, colorop);
> if (IS_ERR(colorop_state))
> return PTR_ERR(colorop_state);
> }
> diff --git a/drivers/gpu/drm/drm_atomic_helper.c b/drivers/gpu/drm/drm_atomic_helper.c
> index a768398a1884..c8dadbf5c319 100644
> --- a/drivers/gpu/drm/drm_atomic_helper.c
> +++ b/drivers/gpu/drm/drm_atomic_helper.c
> @@ -3752,12 +3752,9 @@ drm_atomic_helper_duplicate_state(struct drm_device *dev,
> goto free;
> }
>
> - if (plane_state->color_pipeline) {
> - err = drm_atomic_add_affected_colorops(state, plane);
> - if (err)
> - goto free;
> - }
> -
> + err = drm_atomic_add_affected_colorops(plane_state, plane);
> + if (err)
> + goto free;
> }
>
> drm_connector_list_iter_begin(dev, &conn_iter);
> diff --git a/include/drm/drm_atomic.h b/include/drm/drm_atomic.h
> index 8883290cd014..8916923f32b8 100644
> --- a/include/drm/drm_atomic.h
> +++ b/include/drm/drm_atomic.h
> @@ -919,7 +919,7 @@ int __must_check
> drm_atomic_add_affected_planes(struct drm_atomic_state *state,
> struct drm_crtc *crtc);
> int __must_check
> -drm_atomic_add_affected_colorops(struct drm_atomic_state *state,
> +drm_atomic_add_affected_colorops(struct drm_plane_state *state,
s/state/plane_state
Otherwise, LGTM. (needs a rebase though)
Reviewed-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
> struct drm_plane *plane);
>
> int __must_check drm_atomic_check_only(struct drm_atomic_state *state);
next prev parent reply other threads:[~2026-05-18 11:42 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 [this message]
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 ` [PATCH v5 0/6] drm/atomic: track individual colorop updates Melissa Wen
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=9fca1948-d30d-4c7d-8e8b-a0cb8c5b3ce6@intel.com \
--to=chaitanya.kumar.borah@intel.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=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=mwen@igalia.com \
--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