[V7 31/45] drm/colorop: add BT2020/BT709 OETF and Inverse OETF
Pekka Paalanen
pekka.paalanen at haloniitty.fi
Fri Jan 17 09:06:41 UTC 2025
On Thu, 16 Jan 2025 10:56:22 +0200
Pekka Paalanen <pekka.paalanen at haloniitty.fi> wrote:
> On Thu, 19 Dec 2024 21:33:37 -0700
> Alex Hung <alex.hung at amd.com> wrote:
>
> > From: Harry Wentland <harry.wentland at amd.com>
> >
> > The BT.709 and BT.2020 OETFs are the same, the only difference
> > being that the BT.2020 variant is defined with more precision
> > for 10 and 12-bit per color encodings.
> >
> > Both are used as encoding functions for video content, and are
> > therefore defined as OETF (opto-electronic transfer function)
> > instead of as EOTF (electro-optical transfer function).
> >
> > Signed-off-by: Alex Hung <alex.hung at amd.com>
> > Signed-off-by: Harry Wentland <harry.wentland at amd.com>
>
> Hi,
>
> why would a display system ever use BT.2020 or BT.709 OETF or its
> inverse?
Sorry, this is more for my own curiosity, not an argument against the
patch. Since hardware designers decided to incorporate these curves
explicitly, what use was in mind? It's likely something I have
overlooked.
Thanks,
pq
-------------- 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/20250117/9bc7d77a/attachment.sig>
More information about the wayland-devel
mailing list