From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
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 0/3] drm/connector: hdmi: Allow using the YUV420 output format
Date: Sat, 30 Nov 2024 21:05:29 +0200 [thread overview]
Message-ID: <ca8c796e-fa89-412e-acdc-2515efeb6ca5@collabora.com> (raw)
In-Reply-To: <6hcjgagu7hvbnn6rp5znwjxeaa6wqkeecgvvqkzvtma2ni6mfz@lrbmtbogkzgm>
On 11/30/24 10:38 AM, Dmitry Baryshkov wrote:
> On Sat, Nov 30, 2024 at 01:56:31AM +0200, Cristian Ciocaltea wrote:
>> Provide the basic support to enable using YUV420 as an RGB fallback when
>> computing the best output format and color depth.
>
> The HDMI Connector functionality has pretty good KUnit coverage. Please
> expand KUnits to cover your patches too.
Sure, will handle this in v2.
Thanks for reviewing,
Cristian
prev parent reply other threads:[~2024-11-30 19:05 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
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 [this message]
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=ca8c796e-fa89-412e-acdc-2515efeb6ca5@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=airlied@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--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