From: sashiko-bot@kernel.org
To: "Andreas Kemnade" <andreas@kemnade.info>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/omap: dss: fix handling deferrals
Date: Wed, 11 Nov 2026 21:30:11 +0000 [thread overview]
Message-ID: <sashiko-outbox-209709@kernel.org> (raw)
In-Reply-To: <20261111-gta04-drm-regression-fix-v2-1-010caf3b08bd@kemnade.info>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] drm/omap: dss: unreachable NULL check and error label in
omapdss_device_init_output()
--
commit f6c9c857e7ddd89b0afd04f9a84b349ebb1ccb32
Author: Andreas Kemnade <andreas@kemnade.info>
drm/omap: dss: fix handling deferrals
This commit forwards -EPROBE_DEFER from of_drm_get_bridge_by_endpoint() in
omapdss_device_init_output() instead of ignoring it as a missing video
sink.
> diff --git a/drivers/gpu/drm/omapdrm/dss/output.c b/drivers/gpu/drm/omapdrm/dss/output.c
> index 36d37deac8026..b5cef5093a883 100644
> --- a/drivers/gpu/drm/omapdrm/dss/output.c
> +++ b/drivers/gpu/drm/omapdrm/dss/output.c
> @@ -24,6 +24,9 @@ int omapdss_device_init_output(struct omap_dss_device *out,
>
> bridge = of_drm_get_bridge_by_endpoint(out->dev->of_node, out->of_port, 0);
> if (IS_ERR(bridge)) {
> + if (PTR_ERR(bridge) == -EPROBE_DEFER)
> + return PTR_ERR(bridge);
> +
> dev_dbg(out->dev, "failed to find video sink\n");
> return 0;
> }
[Severity: Low]
Can the !out->bridge check, local variable ret, and the error label later
in omapdss_device_init_output() be removed as well?
of_drm_get_bridge_by_endpoint() returns an error pointer rather than NULL
when no bridge is found, and the IS_ERR(bridge) branch returns early. With
-EPROBE_DEFER handled here, out->bridge is never NULL in the local_bridge
block and the error path left over from b7e9b93fc8ec ("drm/omap: dss:
don't create a panel_bridge") is unreachable:
drivers/gpu/drm/omapdrm/dss/output.c:omapdss_device_init_output() {
...
if (local_bridge) {
if (!out->bridge) {
ret = -EPROBE_DEFER;
goto error;
}
...
error:
omapdss_device_cleanup_output(out);
return ret;
}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111-gta04-drm-regression-fix-v2-1-010caf3b08bd@kemnade.info?part=1
next prev parent reply other threads:[~2026-11-11 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 21:14 [PATCH v2] drm/omap: dss: fix handling deferrals Andreas Kemnade
2026-11-11 21:30 ` sashiko-bot [this message]
2026-11-12 7:43 ` Luca Ceresoli
2026-11-12 10:25 ` Tomi Valkeinen
2026-11-12 11:35 ` Andreas Kemnade
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=sashiko-outbox-209709@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=andreas@kemnade.info \
--cc=dri-devel@lists.freedesktop.org \
--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 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.