From: Maxime Ripard <mripard@kernel.org>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
David Airlie <airlied@gmail.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Jonas Karlman <jonas@kwiboo.se>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Phong LE <ple@baylibre.com>, Robert Foss <rfoss@kernel.org>,
Simona Vetter <simona@ffwll.ch>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/bridge: it66121: Select HDMI or DVI mode based on sink type
Date: Mon, 11 May 2026 09:08:15 +0200 [thread overview]
Message-ID: <20260511-spiritual-unique-uakari-5ffce7@houat> (raw)
In-Reply-To: <20260510191459.90769-4-javierm@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2086 bytes --]
Hi,
On Sun, May 10, 2026 at 09:14:49PM +0200, Javier Martinez Canillas wrote:
> Currently, the driver assumes that the connector sink type is always HDMI
> and configures the IT66121 bridge appropriately. But configuring in this
> mode and enabling the transmission of AVI infoframe packets can cause DVI
> monitors to fail parsing the video signal.
>
> To prevent this, store the connector display information sink type in the
> bridge atomic state and use it to decide whether the bridge should be set
> in HDMI or DVI mode, and if the AVI infoframes packets should be sent.
>
> Assisted-by: Cursor:claude-4.6-opus
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
> ---
>
> drivers/gpu/drm/bridge/ite-it66121.c | 68 ++++++++++++++++++----------
> 1 file changed, 44 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/gpu/drm/bridge/ite-it66121.c b/drivers/gpu/drm/bridge/ite-it66121.c
> index a203c94a27e5..99088277d170 100644
> --- a/drivers/gpu/drm/bridge/ite-it66121.c
> +++ b/drivers/gpu/drm/bridge/ite-it66121.c
> @@ -322,6 +322,7 @@ static inline struct it66121_ctx *bridge_to_it66121_ctx(struct drm_bridge *bridg
>
> struct it66121_bridge_state {
> struct drm_bridge_state base;
> + bool sink_is_hdmi;
> };
>
> static inline struct it66121_bridge_state *
> @@ -790,6 +791,14 @@ static int it66121_bridge_check(struct drm_bridge *bridge,
> struct drm_connector_state *conn_state)
> {
> struct it66121_ctx *ctx = bridge_to_it66121_ctx(bridge);
> + struct it66121_bridge_state *state =
> + to_it66121_bridge_state(bridge_state);
> +
> + /* Default to HDMI to preserve legacy behavior. */
> + state->sink_is_hdmi = true;
> +
> + if (conn_state && conn_state->connector)
> + state->sink_is_hdmi = conn_state->connector->display_info.is_hdmi;
It's really not clear to me why you need to have that in the bridge
state. What's wrong with using drm_display_info.is_hdmi directly?
If you really want to rework the driver though, switch to HDMI state
helpers would fix all of it :)
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2026-05-11 7:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 19:14 [PATCH 0/3] drm/bridge: it66121: Fix display output on DVI monitors Javier Martinez Canillas
2026-05-10 19:14 ` [PATCH 1/3] drm/bridge: it66121: Add bridge_to_it66121_ctx() helper Javier Martinez Canillas
2026-05-16 6:11 ` Claude review: " Claude Code Review Bot
2026-05-10 19:14 ` [PATCH 2/3] drm/bridge: it66121: Add bridge-private atomic state Javier Martinez Canillas
2026-05-16 6:11 ` Claude review: " Claude Code Review Bot
2026-05-10 19:14 ` [PATCH 3/3] drm/bridge: it66121: Select HDMI or DVI mode based on sink type Javier Martinez Canillas
2026-05-11 7:08 ` Maxime Ripard [this message]
2026-05-11 12:48 ` Javier Martinez Canillas
2026-05-11 13:23 ` Maxime Ripard
2026-05-11 13:44 ` Javier Martinez Canillas
2026-05-12 9:24 ` Javier Martinez Canillas
2026-05-16 6:11 ` Claude review: " Claude Code Review Bot
2026-05-16 6:11 ` Claude review: drm/bridge: it66121: Fix display output on DVI monitors Claude Code Review Bot
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=20260511-spiritual-unique-uakari-5ffce7@houat \
--to=mripard@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=neil.armstrong@linaro.org \
--cc=ple@baylibre.com \
--cc=rfoss@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