From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: "Osama Abdelkader" <osama.abdelkader@gmail.com>,
<luca.ceresoli@bootlin.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Jessica Zhang" <jesszhan0024@gmail.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Jerry Han" <hanxu5@huaqin.corp-partner.google.com>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/6] drm/panel: Use devm_mipi_dsi_attach in BOE panels
Date: Tue, 25 Aug 2026 17:59:23 +0200 [thread overview]
Message-ID: <DKY5E1PJ172I.2LYOZZT775PE9@bootlin.com> (raw)
In-Reply-To: <20260812130429.16850-1-osama.abdelkader@gmail.com>
On Wed Aug 12, 2026 at 3:04 PM CEST, Osama Abdelkader wrote:
> Use the managed MIPI DSI attach helper in BOE panel drivers and drop the
> corresponding manual detach calls from remove paths.
>
> Signed-off-by: Osama Abdelkader <osama.abdelkader@gmail.com>
Please, next time use proper tools to send your series ina single thread
with a cover letter. This v3 is made of 6 e-mails in 6 separate threads,
which is very annoying to handle.
>
> ---
> v3:
> - Move the changelog after the `---`.
>
> v2:
> - break long description lines.
> - add Signed-off-by tag
>
> drivers/gpu/drm/panel/panel-boe-bf060y8m-aj0.c | 8 +-------
> drivers/gpu/drm/panel/panel-boe-himax8279d.c | 8 +-------
> drivers/gpu/drm/panel/panel-boe-td4320.c | 8 +-------
> drivers/gpu/drm/panel/panel-boe-th101mb31ig002-28a.c | 4 +---
> drivers/gpu/drm/panel/panel-boe-tv101wum-ll2.c | 8 +-------
> drivers/gpu/drm/panel/panel-boe-tv101wum-nl6.c | 7 +------
> 6 files changed, 6 insertions(+), 37 deletions(-)
>
> diff --git a/drivers/gpu/drm/panel/panel-boe-bf060y8m-aj0.c b/drivers/gpu/drm/panel/panel-boe-bf060y8m-aj0.c
> index 84c21c62a43e..6a74523a6614 100644
> --- a/drivers/gpu/drm/panel/panel-boe-bf060y8m-aj0.c
> +++ b/drivers/gpu/drm/panel/panel-boe-bf060y8m-aj0.c
> @@ -359,7 +359,7 @@ static int boe_bf060y8m_aj0_probe(struct mipi_dsi_device *dsi)
>
> drm_panel_add(&boe->panel);
Why not converting drm_panel_add() to the devm variant too? Without it...
>
> - ret = mipi_dsi_attach(dsi);
> + ret = devm_mipi_dsi_attach(&dsi->dev, dsi);
> if (ret < 0) {
> dev_err(dev, "Failed to attach to DSI host: %d\n", ret);
> return ret;
> @@ -371,12 +371,6 @@ static int boe_bf060y8m_aj0_probe(struct mipi_dsi_device *dsi)
> static void boe_bf060y8m_aj0_remove(struct mipi_dsi_device *dsi)
> {
> struct boe_bf060y8m_aj0 *boe = mipi_dsi_get_drvdata(dsi);
> - int ret;
> -
> - ret = mipi_dsi_detach(dsi);
> - if (ret < 0)
> - dev_err(&dsi->dev, "Failed to detach from DSI host: %d\n", ret);
> -
> drm_panel_remove(&boe->panel);
> }
...the remove sequence will be incorrect: removing the panel first (open
coded) and detaching the DSI device afterwards (devm, done after .remove
returns).
Same for the other files.
Note that patch 2 is correct in this respect.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-08-25 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 13:04 Osama Abdelkader
2026-08-12 13:04 ` [PATCH v3 2/6] drm/panel: Use devm_mipi_dsi_attach in Samsung panels Osama Abdelkader
2026-08-12 13:04 ` [PATCH v3 3/6] drm/panel: Use devm_mipi_dsi_attach in Novatek and Raydium panels Osama Abdelkader
2026-08-12 13:04 ` [PATCH v3 4/6] drm/panel: Use devm_mipi_dsi_attach in Himax and Ilitek panels Osama Abdelkader
2026-08-12 13:04 ` [PATCH v3 5/6] drm/panel: Use devm_mipi_dsi_attach in display vendor panels Osama Abdelkader
2026-08-12 13:04 ` [PATCH v3 6/6] drm/panel: Use devm_mipi_dsi_attach in assorted panels Osama Abdelkader
2026-08-12 13:26 ` [PATCH v3 1/6] drm/panel: Use devm_mipi_dsi_attach in BOE panels Maxime Ripard
2026-08-12 13:45 ` Luca Ceresoli
2026-08-12 14:23 ` Osama Abdelkader
2026-08-25 15:59 ` Luca Ceresoli [this message]
2026-08-25 16:32 ` 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=DKY5E1PJ172I.2LYOZZT775PE9@bootlin.com \
--to=luca.ceresoli@bootlin.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hanxu5@huaqin.corp-partner.google.com \
--cc=jesszhan0024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=osama.abdelkader@gmail.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
all inboxes | Powered by JetHome®