dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Melissa Wen <mwen@igalia.com>
To: Pekka Paalanen <ppaalanen@gmail.com>
Cc: "xaver.hugl@gmail.com" <xaver.hugl@gmail.com>,
	"DRI Development" <dri-devel@lists.freedesktop.org>,
	wayland-devel <wayland-devel@lists.freedesktop.org>,
	"Victoria Brekenfeld" <victoria@system76.com>,
	"Jonas Ådahl" <jadahl@redhat.com>,
	"Uma Shankar" <uma.shankar@intel.com>,
	"Joshua Ashton" <joshua@froggi.es>,
	"Michel Dänzer" <mdaenzer@redhat.com>,
	"Aleix Pol" <aleixpol@kde.org>,
	"Sebastian Wick" <sebastian.wick@redhat.com>
Subject: Re: [RFC] Plane color pipeline KMS uAPI
Date: Tue, 9 May 2023 16:01:02 -0100	[thread overview]
Message-ID: <20230509170102.d2iec32gxn5lur72@mail.igalia.com> (raw)
In-Reply-To: <20230509144717.7c85443d@eldfell>

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

On 05/09, Pekka Paalanen wrote:
> On Tue, 9 May 2023 10:23:49 -0100
> Melissa Wen <mwen@igalia.com> wrote:
> 
> > On 05/05, Joshua Ashton wrote:
> > > Some corrections and replies inline.
> > > 
> > > On Fri, 5 May 2023 at 12:42, Pekka Paalanen <ppaalanen@gmail.com> wrote:  
> > > >
> > > > On Thu, 04 May 2023 15:22:59 +0000
> > > > Simon Ser <contact@emersion.fr> wrote:
> > > >  
> 
> ...
> 
> > > > >     Color operation 47 (3D LUT RAM)
> > > > >     └─ "lut_data" = Gamut mapping + tone mapping + night mode
> > > > >     Color operation 48 (blend gamma)
> > > > >     └─ "1d_curve_type" = PQ  
> > > 
> > > ^
> > > This is wrong, this should be Display Native -> Linearized Display Referred  
> > 
> > This is a good point to discuss. I understand for the HDR10 case that we
> > are just setting an enumerated TF (that is PQ for this case - correct me
> > if I got it wrong) but, unlike when we use a user-LUT, we don't know
> > from the API that this enumerated TF value with an empty LUT is used for
> > linearizing/degamma. Perhaps this could come as a pair? Any idea?
> 
> PQ curve is an EOTF, so it's always from electrical to optical.
> 
> Are you asking for something like
> 
> "1d_curve_type" = "PQ EOTF"
> 
> vs.
> 
> "1d_curve_type" = "inverse PQ EOTF"?
> 
> I think that's how it should work. It's not a given that if a
> hardware block can do a curve, it can also do its inverse. They need to
> be advertised explicitly.

Sounds good and clear to me.

Thanks!

Melissa

> 
> 
> Thanks,
> pq
> 
> ps. I picked my nick in the 90s. Any resemblance to Perceptual
> Quantizer is unintended. ;-)

:D

> 
> 
> > > >
> > > > You cannot do a TF with a matrix, and a gamut remap with a matrix on
> > > > electrical values is certainly surprising, so the example here is a
> > > > bit odd, but I don't think that hurts the intention of demonstration.  
> > > 
> > > I have done some corrections inline.
> > > 
> > > You can see our fully correct color pipeline here:
> > > https://raw.githubusercontent.com/ValveSoftware/gamescope/master/src/docs/Steam%20Deck%20Display%20Pipeline.png
> > > 
> > > Please let me know if you have any more questions about our color pipeline.



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

  reply	other threads:[~2023-05-09 17:01 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 [this message]
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
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=20230509170102.d2iec32gxn5lur72@mail.igalia.com \
    --to=mwen@igalia.com \
    --cc=aleixpol@kde.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jadahl@redhat.com \
    --cc=joshua@froggi.es \
    --cc=mdaenzer@redhat.com \
    --cc=ppaalanen@gmail.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).