[RFC PATCH v4 10/42] drm/colorop: Add TYPE property

Pekka Paalanen pekka.paalanen at collabora.com
Tue Mar 12 15:55:16 UTC 2024

On Tue, 12 Mar 2024 15:15:13 +0000
Simon Ser <contact at emersion.fr> wrote:

> On Tuesday, March 12th, 2024 at 16:02, Pekka Paalanen <pekka.paalanen at collabora.com> wrote:
> > This list here is the list of all values the enum could take, right?
> > Should it not be just the one value it's going to have? It'll never
> > change, and it can never be changed.  
> Listing all possible values is how other properties behave. Example:
>     "type" (immutable): enum {Overlay, Primary, Cursor} = Primary

Yeah, that's weird, now that you pointed it out.

Userspace does nothing with the knowledge of what this specific
object's property "could" be since it's immutable. Only the kernel
internals and UAPI docs need the full list, and userspace needs to
hardcode the full list in general so it can recognize each value. But
on the property instance on a specific object, I see no use for the
full list.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20240312/3072b6d7/attachment.sig>

More information about the wayland-devel mailing list