From: Maxime Ripard <mripard@kernel.org>
To: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
kernel@collabora.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] drm/connector: hdmi: Add support for YUV420 format verification
Date: Mon, 2 Dec 2024 12:59:45 +0100 [thread overview]
Message-ID: <20241202-divergent-holistic-seal-b24cd6@houat> (raw)
In-Reply-To: <a00ba6bb-aa91-4ecf-a4e7-88d80e29dedc@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 3526 bytes --]
On Mon, Dec 02, 2024 at 01:15:36PM +0200, Cristian Ciocaltea wrote:
> Hi Maxime,
>
> On 12/2/24 12:50 PM, Maxime Ripard wrote:
> > On Sat, Nov 30, 2024 at 01:56:33AM +0200, Cristian Ciocaltea wrote:
> >> Provide the necessary constraints verification in
> >> sink_supports_format_bpc() in order to support handling of YUV420
> >> output format.
> >>
> >> Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
> >> ---
> >> drivers/gpu/drm/display/drm_hdmi_state_helper.c | 40 +++++++++++++++++++++++--
> >> 1 file changed, 37 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/display/drm_hdmi_state_helper.c b/drivers/gpu/drm/display/drm_hdmi_state_helper.c
> >> index 0cbcee7e77cd8dff387044487ce28ee5748f5587..3a55881a544a519bb1254968db891c814f831a0f 100644
> >> --- a/drivers/gpu/drm/display/drm_hdmi_state_helper.c
> >> +++ b/drivers/gpu/drm/display/drm_hdmi_state_helper.c
> >> @@ -3,6 +3,7 @@
> >> #include <drm/drm_atomic.h>
> >> #include <drm/drm_connector.h>
> >> #include <drm/drm_edid.h>
> >> +#include <drm/drm_modes.h>
> >> #include <drm/drm_print.h>
> >>
> >> #include <drm/display/drm_hdmi_helper.h>
> >> @@ -114,6 +115,12 @@ sink_supports_format_bpc(const struct drm_connector *connector,
> >> return false;
> >> }
> >>
> >> + if (drm_mode_is_420_only(info, mode) && format != HDMI_COLORSPACE_YUV420) {
> >> + drm_dbg_kms(dev, "%s format unsupported by the sink for VIC%u.\n",
> >> + drm_hdmi_connector_get_output_format_name(format), vic);
> >> + return false;
> >> + }
> >> +
> >> switch (format) {
> >> case HDMI_COLORSPACE_RGB:
> >> drm_dbg_kms(dev, "RGB Format, checking the constraints.\n");
> >> @@ -144,9 +151,36 @@ sink_supports_format_bpc(const struct drm_connector *connector,
> >> return true;
> >>
> >> case HDMI_COLORSPACE_YUV420:
> >> - /* TODO: YUV420 is unsupported at the moment. */
> >> - drm_dbg_kms(dev, "YUV420 format isn't supported yet.\n");
> >> - return false;
> >> + drm_dbg_kms(dev, "YUV420 format, checking the constraints.\n");
> >> +
> >> + if (!(info->color_formats & DRM_COLOR_FORMAT_YCBCR420)) {
> >> + drm_dbg_kms(dev, "Sink doesn't support YUV420.\n");
> >> + return false;
> >> + }
> >> +
> >> + if (!drm_mode_is_420(info, mode)) {
> >> + drm_dbg_kms(dev, "Sink doesn't support YUV420 for VIC%u.\n", vic);
> >> + return false;
> >> + }
> >> +
> >> + if (bpc == 10 && !(info->hdmi.y420_dc_modes & DRM_EDID_YCBCR420_DC_30)) {
> >> + drm_dbg_kms(dev, "10 BPC but sink doesn't support Deep Color 30.\n");
> >> + return false;
> >> + }
> >> +
> >> + if (bpc == 12 && !(info->hdmi.y420_dc_modes & DRM_EDID_YCBCR420_DC_36)) {
> >> + drm_dbg_kms(dev, "12 BPC but sink doesn't support Deep Color 36.\n");
> >> + return false;
> >> + }
> >> +
> >> + if (bpc == 16 && !(info->hdmi.y420_dc_modes & DRM_EDID_YCBCR420_DC_48)) {
> >> + drm_dbg_kms(dev, "16 BPC but sink doesn't support Deep Color 48.\n");
> >> + return false;
> >> + }
> >> +
> >> + drm_dbg_kms(dev, "YUV420 format supported in that configuration.\n");
> >> +
> >> + return true;
> >
> > We also need to check whether the source supports it or not.
>
> I assumed the following check does already handle that:
>
> if (!(connector->hdmi.supported_formats & BIT(format))) {
> drm_dbg_kms(dev, "%s format unsupported by the connector.\n",
>
> Is there anything else missing?
You're right, sorry for the noise :)
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2024-12-02 11:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 23:56 [PATCH 0/3] drm/connector: hdmi: Allow using the YUV420 output format Cristian Ciocaltea
2024-11-29 23:56 ` [PATCH 1/3] drm/connector: hdmi: Evaluate limited range after computing format Cristian Ciocaltea
2024-11-30 8:42 ` Dmitry Baryshkov
2024-11-29 23:56 ` [PATCH 2/3] drm/connector: hdmi: Add support for YUV420 format verification Cristian Ciocaltea
2024-11-30 8:40 ` Dmitry Baryshkov
2024-12-02 10:50 ` Maxime Ripard
2024-12-02 11:15 ` Cristian Ciocaltea
2024-12-02 11:59 ` Maxime Ripard [this message]
2024-11-29 23:56 ` [PATCH 3/3] drm/connector: hdmi: Use YUV420 output format as an RGB fallback Cristian Ciocaltea
2024-11-30 8:39 ` Dmitry Baryshkov
2024-12-02 11:11 ` Maxime Ripard
2024-11-30 8:38 ` [PATCH 0/3] drm/connector: hdmi: Allow using the YUV420 output format Dmitry Baryshkov
2024-11-30 19:05 ` 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=20241202-divergent-holistic-seal-b24cd6@houat \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®