dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Paalanen <pekka.paalanen@collabora.com>
To: Alex Hung <alex.hung@amd.com>
Cc: Melissa Wen <mwen@igalia.com>,
	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: Thu, 2 Apr 2026 14:00:29 +0300	[thread overview]
Message-ID: <20260402140029.307b9c8c@fluorite> (raw)
In-Reply-To: <f7465d35-5d2a-4f1a-be6c-46321d5bb16e@amd.com>

[-- Attachment #1: Type: text/plain, Size: 2319 bytes --]

On Wed, 1 Apr 2026 18:53:56 -0600
Alex Hung <alex.hung@amd.com> wrote:

> 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?

Yes, please!


Thanks,
pq


> 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;
> 

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-04-02 11:00 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
2026-04-02 11:00       ` Pekka Paalanen [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=20260402140029.307b9c8c@fluorite \
    --to=pekka.paalanen@collabora.com \
    --cc=airlied@gmail.com \
    --cc=alex.hung@amd.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=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