From: sashiko-bot@kernel.org
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: imx@lists.linux.dev, Frank.Li@kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm/imx: imx-tve: probe DDC before claiming the connector is connected
Date: Mon, 10 Aug 2026 15:01:50 +0000 [thread overview]
Message-ID: <20260810150151.7E0131F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260810-imx53-fix-hdmi-v1-3-fff9b1b17f25@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
New issues:
- [Medium] Missing polling configuration for dynamic hotplug detection.
Pre-existing issues:
- [High] Missing -EPROBE_DEFER handling undermines the intended fix under normal probe ordering.
--
--- Patch [3]: [PATCH 3/4] drm/imx: imx-tve: probe DDC before claiming the connector is connected ---
commit 496cfa19c398d86d2f77e8a07cbe96a51f14ca0a
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
drm/imx: imx-tve: probe DDC before claiming the connector is connected
This commit adds a detect_ctx hook to the TVE connector using the DDC bus to
detect whether a monitor is attached. It aims to fix a CRTC timeout issue
caused by unconditionally lighting up the VGA output when nothing is
connected.
> diff --git a/drivers/gpu/drm/imx/ipuv3/imx-tve.c b/drivers/gpu/drm/imx/ipuv3/imx-tve.c
> index e861b8b9d8fa8..11ac69561eb81 100644
> --- a/drivers/gpu/drm/imx/ipuv3/imx-tve.c
> +++ b/drivers/gpu/drm/imx/ipuv3/imx-tve.c
> @@ -322,6 +322,7 @@ static const struct drm_connector_funcs imx_tve_connector_funcs = {
> static const struct drm_connector_helper_funcs imx_tve_connector_helper_funcs = {
> .get_modes = imx_tve_connector_get_modes,
> .mode_valid = imx_tve_connector_mode_valid,
> + .detect_ctx = drm_connector_helper_detect_from_ddc,
[Severity: Medium]
Since this adds dynamic detection through the detect_ctx callback, shouldn't
we also configure the connector polling flags in imx_tve_bind()?
It looks like the connector is initialized here:
imx_tve_bind() {
...
ret = drm_connector_init_with_ddc(drm, connector,
&imx_tve_connector_funcs,
DRM_MODE_CONNECTOR_VGA, tve->ddc);
...
}
Without setting connector->polled = DRM_CONNECTOR_POLL_CONNECT |
DRM_CONNECTOR_POLL_DISCONNECT, the DRM core's periodic poll worker will
ignore this connector. Will this prevent dynamic detection if a user plugs
in a monitor after boot?
[Severity: High]
This is a pre-existing issue, but could probe ordering undermine this fix?
The patch relies on tve->ddc being initialized to accurately report the
connector status. However, imx_tve_probe() does not currently handle probe
deferral:
imx_tve_probe() {
...
tve->ddc = of_find_i2c_adapter_by_node(ddc_node);
of_node_put(ddc_node);
if (tve->ddc) {
...
}
If the I2C driver hasn't probed yet, tve->ddc will be left as NULL instead
of returning -EPROBE_DEFER.
If detect_ctx is later called with a NULL DDC adapter,
drm_connector_helper_detect_from_ddc() will return connector_status_unknown.
Because the DRM core treats unknown as connected when fallback modes are
involved, does this mean the CRTC timeout bug will reoccur whenever the I2C
driver probes after imx-tve?
> };
>
> static const struct drm_encoder_helper_funcs imx_tve_encoder_helper_funcs = {
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260810-imx53-fix-hdmi-v1-0-fff9b1b17f25@oss.qualcomm.com?part=3
next prev parent reply other threads:[~2026-08-10 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 14:51 [PATCH 0/4] drm/imx: fix TVE / HDMI coexistence Dmitry Baryshkov
2026-08-10 14:51 ` [PATCH 1/4] drm/imx: ipuv3-plane: do not advertise separate alpha formats on DC planes Dmitry Baryshkov
2026-08-10 14:51 ` [PATCH 2/4] drm/imx: ipuv3-plane: add the pixel blend mode property Dmitry Baryshkov
2026-08-10 15:02 ` sashiko-bot
2026-08-10 14:51 ` [PATCH 3/4] drm/imx: imx-tve: probe DDC before claiming the connector is connected Dmitry Baryshkov
2026-08-10 15:01 ` sashiko-bot [this message]
2026-08-10 14:51 ` [PATCH 4/4] gpu: ipu-v3: di: report an unattainable pixel clock Dmitry Baryshkov
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=20260810150151.7E0131F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imx@lists.linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
/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