From: Pekka Paalanen <pekka.paalanen@haloniitty.fi>
To: Xaver Hugl <xaver.hugl@kde.org>
Cc: dri-devel@lists.freedesktop.org, ville.syrjala@linux.intel.com,
contact@emersion.fr, sebastian.wick@redhat.com
Subject: Re: [PATCH] drm: document userspace expectations around the Colorspace connector property
Date: Mon, 12 Feb 2024 10:46:36 +0200 [thread overview]
Message-ID: <20240212104636.5a411226@eldfell> (raw)
In-Reply-To: <20240209165307.29856-1-xaver.hugl@kde.org>
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]
On Fri, 9 Feb 2024 17:53:07 +0100
Xaver Hugl <xaver.hugl@kde.org> wrote:
> Signed-off-by: Xaver Hugl <xaver.hugl@kde.org>
> ---
> drivers/gpu/drm/drm_connector.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
> index b0516505f7ae..01e13984629b 100644
> --- a/drivers/gpu/drm/drm_connector.c
> +++ b/drivers/gpu/drm/drm_connector.c
> @@ -2158,6 +2158,14 @@ EXPORT_SYMBOL(drm_mode_create_aspect_ratio_property);
> * one supported. Sink supported colorspaces should be retrieved by
> * userspace from EDID and driver will not explicitly expose them.
> *
> + * As userspace can't currently know whether or not the output is using
> + * RGB or YCC signalling, the driver must translate properties to their
> + * relevant RGB or YCC counterparts, depending on the actually used
> + * signalling. Property values that are only valid for either YCC or RGB
> + * and have no equivalent for the other signalling type must not be
> + * exposed as supported, unless the driver can guarantee it never uses
> + * the signalling that doesn't match the property.
> + *
> * Basically the expectation from userspace is:
> * - Set up CRTC DEGAMMA/CTM/GAMMA to convert to some sink
> * colorspace
Acked-by: Pekka Paalanen <pekka.paalanen@collabora.com>
Thanks,
pq
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-12 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 16:53 [PATCH] drm: document userspace expectations around the Colorspace connector property Xaver Hugl
2024-02-09 20:36 ` Sebastian Wick
2024-02-12 8:46 ` Pekka Paalanen [this message]
2024-02-12 9:10 ` Pekka Paalanen
2024-02-12 16:50 ` Sebastian Wick
2024-02-13 8:54 ` Pekka Paalanen
2024-02-13 9:26 ` Ville Syrjälä
2024-02-19 13:22 ` Sebastian Wick
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=20240212104636.5a411226@eldfell \
--to=pekka.paalanen@haloniitty.fi \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=sebastian.wick@redhat.com \
--cc=ville.syrjala@linux.intel.com \
--cc=xaver.hugl@kde.org \
/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