From: "Maxime Ripard" <mripard@kernel.org>
To: "Cristian Ciocaltea" <cristian.ciocaltea@collabora.com>
Cc: dri-devel@lists.freedesktop.org, kernel@collabora.com,
linux-kernel@vger.kernel.org,
"Dave Stevenson" <dave.stevenson@raspberrypi.com>,
"David Airlie" <airlied@gmail.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
"Dmitry Baryshkov" <lumag@kernel.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Simona Vetter" <simona@ffwll.ch>,
"Thomas Zimmermann" <tzimmermann@suse.de>
Subject: Re: [PATCH v5 04/19] drm/connector: hdmi: Add missing bpc debug info to hdmi_try_format_bpc()
Date: Mon, 02 Jun 2025 09:00:24 +0000 [thread overview]
Message-ID: <441ae7c44624f4efbee5e793f13bfa1e@kernel.org> (raw)
In-Reply-To: <20250527-hdmi-conn-yuv-v5-4-74c9c4a8ac0c@collabora.com>
On Tue, 27 May 2025 15:11:12 +0300, Cristian Ciocaltea wrote:
> The very first debug message in hdmi_try_format_bpc() is incomplete, as
> it doesn't provide the given bpc in addition to the tried format.
>
> Add the missing debug information and drop the now redundant message
> from hdmi_compute_config().
>
> [ ... ]
Reviewed-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2025-06-02 9:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 12:11 [PATCH v5 00/19] drm/connector: hdmi: Allow using the YUV420 output format Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 01/19] drm/connector: hdmi: Evaluate limited range after computing format Cristian Ciocaltea
2025-06-02 9:00 ` Maxime Ripard
2025-05-27 12:11 ` [PATCH v5 02/19] drm/connector: hdmi: Add support for YUV420 format verification Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 03/19] drm/connector: hdmi: Improve debug message for supported format Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 04/19] drm/connector: hdmi: Add missing bpc debug info to hdmi_try_format_bpc() Cristian Ciocaltea
2025-06-02 9:00 ` Maxime Ripard [this message]
2025-05-27 12:11 ` [PATCH v5 05/19] drm/connector: hdmi: Factor out bpc and format computation logic Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 06/19] drm/connector: hdmi: Use YUV420 output format as an RGB fallback Cristian Ciocaltea
2025-06-02 9:00 ` Maxime Ripard
2025-05-27 12:11 ` [PATCH v5 07/19] drm/tests: hdmi: Replace '[_]MHz' with 'mhz' Cristian Ciocaltea
2025-06-02 8:59 ` Maxime Ripard
2025-05-27 12:11 ` [PATCH v5 08/19] drm/tests: hdmi: Switch to 'void *' type for EDID data Cristian Ciocaltea
2025-06-02 8:59 ` Maxime Ripard
2025-05-27 12:11 ` [PATCH v5 09/19] drm/tests: hdmi: Add macro to simplify EDID setup Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 10/19] drm/tests: hdmi: Replace open coded " Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 11/19] drm/tests: hdmi: Drop unused drm_kunit_helper_connector_hdmi_init_funcs() Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 12/19] drm/tests: hdmi: Setup ycbcr_420_allowed before initializing connector Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 13/19] drm/tests: hdmi: Switch to drm_atomic_get_new_connector_state() where possible Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 14/19] drm/tests: hdmi: Provide EDID supporting 4K@30Hz with YUV420 only Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 15/19] drm/tests: hdmi: Add limited range tests for YUV420 mode Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 16/19] drm/tests: hdmi: Rename max TMDS rate fallback tests Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 17/19] drm/tests: hdmi: Provide EDID supporting 4K@30Hz with RGB/YUV Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 18/19] drm/tests: hdmi: Add max TMDS rate fallback tests for YUV420 mode Cristian Ciocaltea
2025-05-27 12:11 ` [PATCH v5 19/19] drm/tests: hdmi: Add test for unsuccessful fallback to YUV420 Cristian Ciocaltea
2025-06-02 9:05 ` [PATCH v5 00/19] drm/connector: hdmi: Allow using the YUV420 output format Maxime Ripard
2025-06-02 9:09 ` Maxime Ripard
2025-06-02 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=441ae7c44624f4efbee5e793f13bfa1e@kernel.org \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@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;
as well as URLs for NNTP newsgroup(s).