From: Marius Vlad <marius.vlad@collabora.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: dri-devel@lists.freedesktop.org, wse@tuxedocomputers.com,
andri@yngvason.is, sebastian.wick@redhat.com,
daniel.stone@collabora.com, jani.nikula@linux.intel.com,
tzimmermann@suse.de, simona.vetter@ffwll.ch,
harry.wentland@amd.com, christian.koenig@amd.com,
derek.foreman@collabora.com
Subject: Re: [PATCH 2/8] hdmi: Add HDMI_COLORSPACE_AUTO enum option
Date: Fri, 12 Sep 2025 21:39:09 +0300 [thread overview]
Message-ID: <aMRoza-hOf29I4OH@xpredator> (raw)
In-Reply-To: <20250912-meaty-caracara-of-potency-ab81e7@penduick>
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
On Fri, Sep 12, 2025 at 05:17:56PM +0200, Maxime Ripard wrote:
> Hi,
Hi Maxime,
>
> On Thu, Sep 11, 2025 at 04:07:33PM +0300, Marius Vlad wrote:
> > diff --git a/drivers/video/hdmi.c b/drivers/video/hdmi.c
> > index 45b42f14a750..74fe925c69a2 100644
> > --- a/drivers/video/hdmi.c
> > +++ b/drivers/video/hdmi.c
> > @@ -1031,8 +1031,8 @@ static const char *hdmi_colorspace_get_name(enum hdmi_colorspace colorspace)
> > return "YCbCr 4:4:4";
> > case HDMI_COLORSPACE_YUV420:
> > return "YCbCr 4:2:0";
> > - case HDMI_COLORSPACE_RESERVED4:
> > - return "Reserved (4)";
> > + case HDMI_COLORSPACE_AUTO:
> > + return "Auto";
> > case HDMI_COLORSPACE_RESERVED5:
> > return "Reserved (5)";
> > case HDMI_COLORSPACE_RESERVED6:
> > diff --git a/include/linux/hdmi.h b/include/linux/hdmi.h
> > index 96bda41d9148..045402033763 100644
> > --- a/include/linux/hdmi.h
> > +++ b/include/linux/hdmi.h
> > @@ -82,7 +82,7 @@ enum hdmi_colorspace {
> > HDMI_COLORSPACE_YUV422,
> > HDMI_COLORSPACE_YUV444,
> > HDMI_COLORSPACE_YUV420,
> > - HDMI_COLORSPACE_RESERVED4,
> > + HDMI_COLORSPACE_AUTO,
> > HDMI_COLORSPACE_RESERVED5,
> > HDMI_COLORSPACE_RESERVED6,
> > HDMI_COLORSPACE_IDO_DEFINED,
>
> I'm not sure we can use hdmi_colorspace as is. This is the enum that
> represents the colorspace encoded in the AVI infoframe, so we can't
> change it, really.
I see. Was hoping I can re-use these as is when defining the color
format enum.
Should I just de-couple the color format entirely from the enum hdmi
colorspace? With the enum color format in it feels they sort of overlap,
with some drivers explicitly using the hdmi colorspace enum others the
color format enum. Feels a bit inconsistent but maybe that's just me
and folks do not see this as an issue.
Perhaps just handle 'Auto' distinctly but still re-use the hdmi
colorspace enum?
Any (strong) preference?
>
> Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-12 18:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 13:07 [PATCH v3 0/8] Add new general DRM property "color format" Marius Vlad
2025-09-11 13:07 ` [PATCH 1/8] drm/amd/display: Remove unnecessary SIGNAL_TYPE_HDMI_TYPE_A check Marius Vlad
2025-09-11 13:07 ` [PATCH 2/8] hdmi: Add HDMI_COLORSPACE_AUTO enum option Marius Vlad
2025-09-12 15:17 ` Maxime Ripard
2025-09-12 18:39 ` Marius Vlad [this message]
2025-09-17 14:42 ` Maxime Ripard
2025-09-11 13:07 ` [PATCH 3/8] drm: Add new general DRM property "color format" Marius Vlad
2025-09-11 13:50 ` Dmitry Baryshkov
2025-09-11 17:15 ` Marius Vlad
2025-09-15 0:57 ` Dmitry Baryshkov
2025-09-15 10:33 ` Daniel Stone
2025-09-15 10:46 ` Dmitry Baryshkov
2025-09-16 11:04 ` Daniel Stone
2025-09-16 8:29 ` Maxime Ripard
2025-09-16 10:46 ` Daniel Stone
2025-09-16 10:48 ` Daniel Stone
2025-09-16 10:57 ` Dmitry Baryshkov
2025-09-16 11:11 ` Daniel Stone
2025-09-16 11:15 ` Dmitry Baryshkov
2025-09-16 11:35 ` Daniel Stone
2025-09-16 16:13 ` Dmitry Baryshkov
2025-09-11 13:07 ` [PATCH 4/8] drm: Add enum conversion from/to HDMI_COLORSPACE to DRM_COLOR_FORMAT Marius Vlad
2025-09-12 15:19 ` Maxime Ripard
2025-09-26 14:50 ` Cristian Ciocaltea
2025-09-30 11:40 ` Maxime Ripard
2025-09-11 13:07 ` [PATCH 5/8] drm: Pass supported color formats straight onto drm_bridge Marius Vlad
2025-09-11 13:55 ` Dmitry Baryshkov
2025-09-11 17:34 ` Marius Vlad
2025-09-12 15:31 ` Maxime Ripard
2025-09-12 18:57 ` Marius Vlad
2025-09-12 21:17 ` Dmitry Baryshkov
2025-09-12 15:33 ` Maxime Ripard
2025-09-12 19:09 ` Marius Vlad
2025-09-15 0:59 ` Dmitry Baryshkov
2025-09-11 13:07 ` [PATCH 6/8] drm/i915: Implement the "color format" DRM property Marius Vlad
2025-09-11 13:07 ` [PATCH 7/8] drm/amdgpu: Implement " Marius Vlad
2025-09-11 13:07 ` [PATCH 8/8] drm/rockchip: " Marius Vlad
2025-09-26 17:58 ` Cristian Ciocaltea
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=aMRoza-hOf29I4OH@xpredator \
--to=marius.vlad@collabora.com \
--cc=andri@yngvason.is \
--cc=christian.koenig@amd.com \
--cc=daniel.stone@collabora.com \
--cc=derek.foreman@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=jani.nikula@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sebastian.wick@redhat.com \
--cc=simona.vetter@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=wse@tuxedocomputers.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.