dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Hung <alex.hung@amd.com>
To: Pekka Paalanen <pekka.paalanen@collabora.com>,
	Melissa Wen <mwen@igalia.com>
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
	contact@emersion.fr, harry.wentland@amd.com,
	sebastian.wick@redhat.com, daniels@collabora.com,
	chaitanya.kumar.borah@intel.com, dri-devel@lists.freedesktop.org,
	Xaver Hugl <xaver.hugl@gmail.com>
Subject: Re: [PATCH] drm/colorop: Mark interpolation properties as immutable and atomic
Date: Wed, 1 Apr 2026 18:53:56 -0600	[thread overview]
Message-ID: <f7465d35-5d2a-4f1a-be6c-46321d5bb16e@amd.com> (raw)
In-Reply-To: <20260331151919.21f972cb@fluorite>



On 3/31/26 06:19, Pekka Paalanen wrote:
> On Mon, 30 Mar 2026 09:33:53 -0300
> Melissa Wen <mwen@igalia.com> wrote:
> 
>> On 26/03/2026 21:39, Alex Hung wrote:
>>> LUT1D_INTERPOLATION and LUT3D_INTERPOLATION are read-only properties but
>>> were missing DRM_MODE_PROP_IMMUTABLE and DRM_MODE_PROP_ATOMIC flags.
>> + Xaver
>>
>> So, I double checked previous conversation about these two interpolation
>> properties.
>> AFAIU, we agreed (?) on not making it immutable because it could become
>> mutable if a HW allows it.
>> -
>> https://lore.kernel.org/dri-devel/CAFZQkGyj7=N2UcbBnjv7Az3oHSD2LXaAx5wzccpSt_UEhH3NZw@mail.gmail.com/
> 
> Simon's rationale there makes sense to me.

Yes this makes sense and I forgot that we discussed it before. Thanks 
Melissa and pekka

> 
>> So, what's the best approach to inform userspace that they cannot change
>> this property?
>> Perhaps the driver has to reject if in the end the property is immutable (?)
> 
> If the enum is exposed with a single value only, then obviously
> userspace cannot program any other value.
> 
> Each driver needs to customize every enum for what they actually
> support, anyway.

As Melissa pointed out in the other thread, the doc said these 
properties are "Read-only" when they are not. Should we update the 
documents, such as below, to avoid confusion?

diff --git include/drm/drm_colorop.h include/drm/drm_colorop.h
index a3a32f9f918c..86d75babe30d 100644
--- include/drm/drm_colorop.h
+++ include/drm/drm_colorop.h
@@ -312,7 +312,7 @@ struct drm_colorop {
  	/**
  	 * @lut1d_interpolation_property:
  	 *
-	 * Read-only property for DRM_COLOROP_1D_LUT interpolation
+	 * Property for DRM_COLOROP_1D_LUT interpolation
  	 */
  	struct drm_property *lut1d_interpolation_property;

@@ -340,7 +340,7 @@ struct drm_colorop {
  	/**
  	 * @lut3d_interpolation_property:
  	 *
-	 * Read-only property for DRM_COLOROP_3D_LUT interpolation
+	 * Property for DRM_COLOROP_3D_LUT interpolation
  	 */
  	struct drm_property *lut3d_interpolation_property;


> 
> 
> Thanks,
> pq
> 
>>
>> Melissa
>>>
>>> Add the correct flags and remove the now-unreachable set_property
>>> handlers in drm_atomic_colorop_set_property().
>>>
>>> Link: https://lore.kernel.org/amd-gfx/dbb27ec4-cdc6-4ead-9daf-664d97e86cd0@intel.com/
>>> Fixes: 7fa3ee8c0a79 ("drm/colorop: Define LUT_1D interpolation")
>>> Fixes: db971856bbe0 ("drm/colorop: Add 3D LUT support to color pipeline")
>>> Suggested-by: Melissa Wen <mwen@igalia.com>
>>> Suggested-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
>>> Signed-off-by: Alex Hung <alex.hung@amd.com>
>>> ---
>>>    drivers/gpu/drm/drm_atomic_uapi.c | 4 ----
>>>    drivers/gpu/drm/drm_colorop.c     | 6 ++++--
>>>    2 files changed, 4 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/drm_atomic_uapi.c b/drivers/gpu/drm/drm_atomic_uapi.c
>>> index 713fa9e81732..e831894d5a51 100644
>>> --- a/drivers/gpu/drm/drm_atomic_uapi.c
>>> +++ b/drivers/gpu/drm/drm_atomic_uapi.c
>>> @@ -758,8 +758,6 @@ static int drm_atomic_colorop_set_property(struct drm_colorop *colorop,
>>>    			state->bypass = val;
>>>    			*replaced = true;
>>>    		}
>>> -	} else if (property == colorop->lut1d_interpolation_property) {
>>> -		colorop->lut1d_interpolation = val;
>>>    	} else if (property == colorop->curve_1d_type_property) {
>>>    		if (state->curve_1d_type != val) {
>>>    			state->curve_1d_type = val;
>>> @@ -770,8 +768,6 @@ static int drm_atomic_colorop_set_property(struct drm_colorop *colorop,
>>>    			state->multiplier = val;
>>>    			*replaced = true;
>>>    		}
>>> -	} else if (property == colorop->lut3d_interpolation_property) {
>>> -		colorop->lut3d_interpolation = val;
>>>    	} else if (property == colorop->data_property) {
>>>    		return drm_atomic_color_set_data_property(colorop, state,
>>>    							  property, val,
>>> diff --git a/drivers/gpu/drm/drm_colorop.c b/drivers/gpu/drm/drm_colorop.c
>>> index 398cc81ae588..34998f393f2e 100644
>>> --- a/drivers/gpu/drm/drm_colorop.c
>>> +++ b/drivers/gpu/drm/drm_colorop.c
>>> @@ -317,7 +317,8 @@ int drm_plane_colorop_curve_1d_lut_init(struct drm_device *dev, struct drm_color
>>>    	colorop->size = lut_size;
>>>    
>>>    	/* interpolation */
>>> -	prop = drm_property_create_enum(dev, 0, "LUT1D_INTERPOLATION",
>>> +	prop = drm_property_create_enum(dev, DRM_MODE_PROP_ATOMIC | DRM_MODE_PROP_IMMUTABLE,
>>> +					"LUT1D_INTERPOLATION",
>>>    					drm_colorop_lut1d_interpolation_list,
>>>    					ARRAY_SIZE(drm_colorop_lut1d_interpolation_list));
>>>    	if (!prop)
>>> @@ -413,7 +414,8 @@ int drm_plane_colorop_3dlut_init(struct drm_device *dev, struct drm_colorop *col
>>>    	colorop->size = lut_size;
>>>    
>>>    	/* interpolation */
>>> -	prop = drm_property_create_enum(dev, 0, "LUT3D_INTERPOLATION",
>>> +	prop = drm_property_create_enum(dev, DRM_MODE_PROP_ATOMIC | DRM_MODE_PROP_IMMUTABLE,
>>> +					"LUT3D_INTERPOLATION",
>>>    					drm_colorop_lut3d_interpolation_list,
>>>    					ARRAY_SIZE(drm_colorop_lut3d_interpolation_list));
>>>    	if (!prop)
>>
> 


  reply	other threads:[~2026-04-02  0:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27  0:39 [PATCH] drm/colorop: Mark interpolation properties as immutable and atomic Alex Hung
2026-03-30 12:33 ` Melissa Wen
2026-03-31 12:19   ` Pekka Paalanen
2026-04-02  0:53     ` Alex Hung [this message]
2026-04-02 11:00       ` Pekka Paalanen

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=f7465d35-5d2a-4f1a-be6c-46321d5bb16e@amd.com \
    --to=alex.hung@amd.com \
    --cc=airlied@gmail.com \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=contact@emersion.fr \
    --cc=daniels@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=mwen@igalia.com \
    --cc=pekka.paalanen@collabora.com \
    --cc=sebastian.wick@redhat.com \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --cc=xaver.hugl@gmail.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