From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: "Shankar, Uma" <uma.shankar@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "contact@emersion.fr" <contact@emersion.fr>,
"alex.hung@amd.com" <alex.hung@amd.com>,
"harry.wentland@amd.com" <harry.wentland@amd.com>,
"daniels@collabora.com" <daniels@collabora.com>,
"mwen@igalia.com" <mwen@igalia.com>,
"sebastian.wick@redhat.com" <sebastian.wick@redhat.com>,
"ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"Nikula, Jani" <jani.nikula@intel.com>,
"louis.chauvet@bootlin.com" <louis.chauvet@bootlin.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 2/2] drm/atomic: Add affected colorops with affected planes
Date: Wed, 11 Mar 2026 02:37:12 +0530 [thread overview]
Message-ID: <2e6e929e-0586-4724-bb03-a9590dd92b22@intel.com> (raw)
In-Reply-To: <DM4PR11MB6360F90857302E3EE94FAB73F477A@DM4PR11MB6360.namprd11.prod.outlook.com>
On 2/24/2026 2:07 AM, Shankar, Uma wrote:
>> Subject: [PATCH 2/2] drm/atomic: Add affected colorops with affected planes
>>
>> When drm_atomic_add_affected_planes() adds a plane to the atomic state, the
>> associated colorops are not guaranteed to be included.
>> This can leave colorop state out of the transaction when planes are pulled in
>> implicitly (eg. during modeset or internal commits).
>>
>> Also add affected colorops when adding affected planes to keep plane and color
>> pipeline state consistent within the atomic transaction.
> Even though colorop is an object in itself but practically it doesn't have any existence without
> the plane. So to add to state along with plane seems logical. Also its good to handle this in
> drm core than individual drivers.
>
> The change looks good to me.
> Reviewed-by: Uma Shankar<uma.shankar@intel.com>
Thank you, Uma, for the review.
I have sent another version of the patch where the colorops are added
only when pipeline is enabled. This avoids flooding of following logs
when pipeline is disabled.
[drm:drm_atomic_get_colorop_state] Added [COLOROP:288:1]
ffff88810db07240 state to ffff88810e040800
Let me know if this looks good for you.
==
Chaitanya
next prev parent reply other threads:[~2026-03-10 21:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 6:57 [PATCH 0/2] drm/colorop: Keep colorop state consistent across atomic commits Chaitanya Kumar Borah
2026-02-18 6:57 ` [PATCH 1/2] drm/colorop: Preserve bypass value in duplicate_state() Chaitanya Kumar Borah
2026-02-23 20:33 ` Shankar, Uma
2026-02-18 6:57 ` [PATCH 2/2] drm/atomic: Add affected colorops with affected planes Chaitanya Kumar Borah
2026-02-23 20:37 ` Shankar, Uma
2026-03-10 21:07 ` Borah, Chaitanya Kumar [this message]
2026-02-18 7:42 ` ✓ CI.KUnit: success for drm/colorop: Keep colorop state consistent across atomic commits Patchwork
2026-02-18 8:15 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-18 8:32 ` ✓ Xe.CI.FULL: " Patchwork
2026-02-18 10:52 ` ✓ CI.KUnit: success for drm/colorop: Keep colorop state consistent across atomic commits (rev2) Patchwork
2026-02-18 12:23 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-18 13:01 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-23 21:14 ` [PATCH 0/2] drm/colorop: Keep colorop state consistent across atomic commits Harry Wentland
2026-02-24 8:59 ` Shankar, Uma
2026-02-26 5:59 ` Borah, Chaitanya Kumar
2026-03-10 21:00 ` Borah, Chaitanya Kumar
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=2e6e929e-0586-4724-bb03-a9590dd92b22@intel.com \
--to=chaitanya.kumar.borah@intel.com \
--cc=alex.hung@amd.com \
--cc=contact@emersion.fr \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=louis.chauvet@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mwen@igalia.com \
--cc=sebastian.wick@redhat.com \
--cc=stable@vger.kernel.org \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@linux.intel.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