From: sashiko-bot@kernel.org
To: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 03/12] drm/bridge: ti-dlpc3433: don't depend on DRM_PANEL
Date: Tue, 25 Aug 2026 10:22:54 +0000 [thread overview]
Message-ID: <20260825102255.0EA6E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260825-drm-bridge-drm_panel-cleanup-v2-3-c6c88ba7ffd2@bootlin.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] The DSI device registered with `mipi_dsi_device_register_full()` is never unregistered, causing a memory and device node leak that prevents driver reload.
--
--- Patch [3]: [PATCH v2 03/12] drm/bridge: ti-dlpc3433: don't depend on DRM_PANEL ---
commit 1c4393105a1871917fd54292e2edbfa8634d5ce0
Author: Luca Ceresoli <luca.ceresoli@bootlin.com>
drm/bridge: ti-dlpc3433: don't depend on DRM_PANEL
This driver does not use the drm_panel APIs at all, so no need to select
DRM_PANEL.
> diff --git a/drivers/gpu/drm/bridge/Kconfig b/drivers/gpu/drm/bridge/Kconfig
> index 958b4f687d4dd..043596801a65b 100644
> --- a/drivers/gpu/drm/bridge/Kconfig
> +++ b/drivers/gpu/drm/bridge/Kconfig
> @@ -428,7 +428,7 @@ config DRM_TOSHIBA_TC358775
>
> config DRM_TI_DLPC3433
> tristate "TI DLPC3433 Display controller"
> - depends on DRM && DRM_PANEL
> + depends on DRM
[Severity: High]
This is a pre-existing issue, but I noticed a device node leak in the
driver itself.
In dlpc_host_attach(), the DSI device is registered manually:
drivers/gpu/drm/bridge/ti-dlpc3433.c:dlpc_host_attach()
...
dlpc->dsi = mipi_dsi_device_register_full(host, &info);
...
However, the remove callback fails to unregister it:
drivers/gpu/drm/bridge/ti-dlpc3433.c:dlpc3433_remove()
static void dlpc3433_remove(struct i2c_client *client)
{
struct dlpc *dlpc = i2c_get_clientdata(client);
drm_bridge_remove(&dlpc->bridge);
of_node_put(dlpc->host_node);
}
Should there be a call to mipi_dsi_device_unregister(dlpc->dsi) here to
prevent leaking the device node unconditionally upon unbind? Alternatively,
could this be migrated to devm_mipi_dsi_device_register_full() so it is
managed by devres?
> depends on OF
> select DRM_MIPI_DSI
> help
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260825-drm-bridge-drm_panel-cleanup-v2-0-c6c88ba7ffd2@bootlin.com?part=3
next prev parent reply other threads:[~2026-08-25 10:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 10:09 [PATCH v2 00/12] drm/bridge: Kconfig: cleanup DRM_PANEL usage Luca Ceresoli
2026-08-25 10:09 ` [PATCH v2 01/12] drm/bridge: megachips-stdpxxxx-ge-b850v3-fw: don't select unused DRM_PANEL Luca Ceresoli
2026-08-25 10:09 ` [PATCH v2 02/12] drm/bridge: tc358764: " Luca Ceresoli
2026-08-25 10:09 ` [PATCH v2 03/12] drm/bridge: ti-dlpc3433: don't depend on DRM_PANEL Luca Ceresoli
2026-08-25 10:22 ` sashiko-bot [this message]
2026-08-25 10:09 ` [PATCH v2 04/12] drm/bridge: ti-sn65dsi86: don't select unused DRM_PANEL Luca Ceresoli
2026-08-27 16:24 ` Doug Anderson
2026-08-31 8:55 ` Luca Ceresoli
2026-08-25 10:09 ` [PATCH v2 05/12] drm/bridge: ti-sn65dsi83: select DRM_PANEL_BRIDGE Luca Ceresoli
2026-08-25 12:24 ` Herve Codina
2026-08-25 13:40 ` Esben Haabendal
2026-08-25 10:09 ` [PATCH v2 06/12] drm/bridge: nxp-ptn3460: " Luca Ceresoli
2026-08-25 10:09 ` [PATCH v2 07/12] drm/bridge: parade-ps8622: " Luca Ceresoli
2026-08-25 10:09 ` [PATCH v2 08/12] drm/bridge: parade-ps8640: " Luca Ceresoli
2026-08-27 16:23 ` Doug Anderson
2026-08-31 9:01 ` Luca Ceresoli
2026-08-31 14:58 ` Doug Anderson
2026-08-31 15:26 ` Luca Ceresoli
2026-08-31 15:28 ` Doug Anderson
2026-08-25 10:09 ` [PATCH v2 09/12] drm/bridge: tc358775: " Luca Ceresoli
2026-08-25 10:09 ` [PATCH v2 10/12] drm/bridge: tc358767: " Luca Ceresoli
2026-08-25 10:32 ` sashiko-bot
2026-08-25 10:09 ` [PATCH v2 11/12] drm/bridge: tc358768: " Luca Ceresoli
2026-08-25 10:09 ` [PATCH v2 12/12] drm/bridge: ssd2825: " Luca Ceresoli
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=20260825102255.0EA6E1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=luca.ceresoli@bootlin.com \
--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.