From: Marius Vlad <marius.vlad@collabora.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
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 5/8] drm: Pass supported color formats straight onto drm_bridge
Date: Fri, 12 Sep 2025 21:57:47 +0300 [thread overview]
Message-ID: <aMRtK6yLsQHzk26y@xpredator> (raw)
In-Reply-To: <20250912-amiable-dandelion-bullfrog-abc930@penduick>
[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]
On Fri, Sep 12, 2025 at 05:31:17PM +0200, Maxime Ripard wrote:
> Hi,
>
> On Thu, Sep 11, 2025 at 08:34:48PM +0300, Marius Vlad wrote:
> > > > diff --git a/drivers/gpu/drm/msm/dsi/dsi_manager.c b/drivers/gpu/drm/msm/dsi/dsi_manager.c
> > > > index ca400924d4ee..4b87f4f78d38 100644
> > > > --- a/drivers/gpu/drm/msm/dsi/dsi_manager.c
> > > > +++ b/drivers/gpu/drm/msm/dsi/dsi_manager.c
> > > > @@ -479,7 +479,7 @@ int msm_dsi_manager_connector_init(struct msm_dsi *msm_dsi,
> > > > if (ret)
> > > > return ret;
> > > >
> > > > - connector = drm_bridge_connector_init(dev, encoder);
> > > > + connector = drm_bridge_connector_init(dev, encoder, BIT(HDMI_COLORSPACE_RGB));
> > >
> > > And this totally depends on the bridge chain. If we have a DSI-to-HDMI
> > > bridge somewhere in the middle, we are able to output YUV data to the
> > > HDMI connector.
> > That's actually the usecase for this patch: to allow passing other color
> > formats, but this patch is a transitory patch to further expose the fact
> > drm_bridge_connector_init was embedding BIT(HDMI_COLORSPACE_RGB) for the
> > format. See rockchip implementation for this bit, the last patch in this
> > series.
>
> I think Dmitry's point is that it needs to be integrated with the
> atomic_get_input_bus_fmt / atomic_get_output_bus_fmt, because not only
> we need to make sure the monitor supports it, and the userspace demands
> it, we also need to make sure every bridge in the chain (and possibly
> the encoder) can implement it.
Oookay. Will be looking at those bits then. Thanks for pointing where
I need to look at.
tbh it isn't super clear to me why is it now that an issue. If you don't
mind replying back, it this patch actually exposing that, or that was a
thing that had to addressed at one point?
>
> Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-12 18:57 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
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 [this message]
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=aMRtK6yLsQHzk26y@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=dmitry.baryshkov@oss.qualcomm.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.