From: Simon Ser <contact@emersion.fr>
To: Joshua Ashton <joshua@froggi.es>
Cc: "Sebastian Wick" <sebastian.wick@redhat.com>,
"Pekka Paalanen" <pekka.paalanen@collabora.com>,
"Karol Herbst" <kherbst@redhat.com>,
"Aleix Pol" <aleixpol@kde.org>,
"DRI Development" <dri-devel@lists.freedesktop.org>,
"xaver.hugl@gmail.com" <xaver.hugl@gmail.com>,
"Melissa Wen" <mwen@igalia.com>,
"Jonas Ådahl" <jadahl@redhat.com>,
"Uma Shankar" <uma.shankar@intel.com>,
"Victoria Brekenfeld" <victoria@system76.com>,
"Michel Dänzer" <mdaenzer@redhat.com>,
wayland-devel <wayland-devel@lists.freedesktop.org>
Subject: Re: [RFC] Plane color pipeline KMS uAPI
Date: Thu, 11 May 2023 19:29:27 +0000 [thread overview]
Message-ID: <k6yN8_WlW_AoQ7bxsopuqRsCxAbjFJ_vpM3iJjy_st--rHf305SsBVubqMbNDkSm4ez1ygoPH2Dc7VffRQjlZBk4fyKFpcZpQGpSA5vA6G0=@emersion.fr> (raw)
In-Reply-To: <CAEZNXZCCn7ZFgyy-NzpSEp0wB0L7PZ-jheHmMWkgQq5pQ+930A@mail.gmail.com>
On Thursday, May 11th, 2023 at 18:56, Joshua Ashton <joshua@froggi.es> wrote:
> When we are talking about being 'prescriptive' in the API, are we
> outright saying we don't want to support arbitrary 3D LUTs, or are we
> just offering certain algorithms to be 'executed' for a plane/crtc/etc
> in the atomic API? I am confused...
From a kernel PoV:
- Prescriptive = here are the available hardware blocks, feel free to
configure each as you like
- Descriptive = give me the source and destination color-spaces and I
take care of everything
This proposal is a prescriptive API. We haven't explored _that_ much
how a descriptive API would look like, probably it can include some way
to do Night Light and similar features but not sure how high-level
they'd look like. A descriptive API is inherently more restrictive than
a prescriptive API.
next prev parent reply other threads:[~2023-05-11 19:29 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 15:22 [RFC] Plane color pipeline KMS uAPI Simon Ser
2023-05-04 21:10 ` Harry Wentland
2023-05-05 11:41 ` Pekka Paalanen
2023-05-05 13:30 ` Joshua Ashton
2023-05-05 14:16 ` Pekka Paalanen
2023-05-05 17:01 ` Joshua Ashton
2023-05-09 11:23 ` Melissa Wen
2023-05-09 11:47 ` Pekka Paalanen
2023-05-09 17:01 ` Melissa Wen
2023-05-11 21:21 ` Simon Ser
2023-05-05 15:28 ` Daniel Vetter
2023-05-05 15:57 ` Sebastian Wick
2023-05-05 19:51 ` Daniel Vetter
2023-05-08 8:24 ` Pekka Paalanen
2023-05-08 9:00 ` Daniel Vetter
2023-05-05 16:06 ` Simon Ser
2023-05-05 19:53 ` Daniel Vetter
2023-05-08 8:58 ` Simon Ser
2023-05-08 9:18 ` Daniel Vetter
2023-05-08 18:10 ` Harry Wentland
[not found] ` <20230508185409.07501f40@n2pa>
2023-05-09 8:17 ` Pekka Paalanen
2023-05-05 20:40 ` Dave Airlie
2023-05-05 22:20 ` Sebastian Wick
2023-05-07 23:14 ` Dave Airlie
2023-05-08 9:37 ` Pekka Paalanen
2023-05-08 10:03 ` Jonas Ådahl
2023-05-09 14:31 ` Harry Wentland
2023-05-09 19:53 ` Dave Airlie
2023-05-09 20:22 ` Simon Ser
2023-05-10 7:59 ` Jonas Ådahl
2023-05-10 8:59 ` Pekka Paalanen
2023-05-11 9:51 ` Karol Herbst
2023-05-11 16:56 ` Joshua Ashton
2023-05-11 18:56 ` Jonas Ådahl
2023-05-11 19:29 ` Simon Ser [this message]
2023-05-12 7:24 ` Pekka Paalanen
2023-05-10 8:48 ` Pekka Paalanen
[not found] ` <20230505160435.6e3ffa4a@n2pa>
2023-05-08 8:49 ` Pekka Paalanen
2023-05-09 8:04 ` Pekka Paalanen
[not found] ` <4341dac6-ada1-2a75-1c22-086d96408a85@quicinc.com>
2023-06-09 15:52 ` Christopher Braga
2023-06-09 16:30 ` Simon Ser
2023-06-09 23:11 ` Christopher Braga
2023-06-12 9:21 ` Pekka Paalanen
2023-06-12 16:56 ` Christopher Braga
2023-06-13 8:23 ` Pekka Paalanen
2023-06-13 16:29 ` Christopher Braga
2023-06-14 9:00 ` Pekka Paalanen
2023-06-15 21:44 ` Christopher Braga
2023-06-16 7:59 ` 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='k6yN8_WlW_AoQ7bxsopuqRsCxAbjFJ_vpM3iJjy_st--rHf305SsBVubqMbNDkSm4ez1ygoPH2Dc7VffRQjlZBk4fyKFpcZpQGpSA5vA6G0=@emersion.fr' \
--to=contact@emersion.fr \
--cc=aleixpol@kde.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jadahl@redhat.com \
--cc=joshua@froggi.es \
--cc=kherbst@redhat.com \
--cc=mdaenzer@redhat.com \
--cc=mwen@igalia.com \
--cc=pekka.paalanen@collabora.com \
--cc=sebastian.wick@redhat.com \
--cc=uma.shankar@intel.com \
--cc=victoria@system76.com \
--cc=wayland-devel@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).