From: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
To: Felix Gu <ustc.gu@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Benoit Parrot <bparrot@ti.com>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Dale Farnsworth <dale@farnsworth.org>,
Sukrut Bellary <sbellary@baylibre.com>
Cc: <linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] media: ti: vpe: Add missing v4l2_device_unregister in vip_remove()
Date: Tue, 3 Mar 2026 14:47:42 +0530 [thread overview]
Message-ID: <26808c31-ef61-4476-b36b-d6c9cf3596a7@ti.com> (raw)
In-Reply-To: <20260301-vip-v1-1-d90572c2c55a@gmail.com>
On 01/03/26 19:09, Felix Gu wrote:
> The v4l2_device is registered during probe but was not being unregistered
> during remove. Add the missing v4l2_device_unregister() call to properly
> clean up resources.
>
> Fixes: fc2873aa4a21 ("media: ti: vpe: Add the VIP driver")
> Signed-off-by: Felix Gu <ustc.gu@gmail.com>
> ---
Reviewed-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
> drivers/media/platform/ti/vpe/vip.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/media/platform/ti/vpe/vip.c b/drivers/media/platform/ti/vpe/vip.c
> index a4b616a5ece7..0e91e87bda9b 100644
> --- a/drivers/media/platform/ti/vpe/vip.c
> +++ b/drivers/media/platform/ti/vpe/vip.c
> @@ -3641,6 +3641,7 @@ static void vip_remove(struct platform_device *pdev)
> }
>
> v4l2_ctrl_handler_free(&shared->ctrl_handler);
> + v4l2_device_unregister(&shared->v4l2_dev);
>
> pm_runtime_put_sync(&pdev->dev);
> pm_runtime_disable(&pdev->dev);
>
> ---
> base-commit: 3fa5e5702a82d259897bd7e209469bc06368bf31
> change-id: 20260301-vip-c6e932239447
>
> Best regards,
prev parent reply other threads:[~2026-03-03 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 13:39 Felix Gu
2026-03-03 9:17 ` Yemike Abhilash Chandra [this message]
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=26808c31-ef61-4476-b36b-d6c9cf3596a7@ti.com \
--to=y-abhilashchandra@ti.com \
--cc=bparrot@ti.com \
--cc=dale@farnsworth.org \
--cc=hverkuil+cisco@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sbellary@baylibre.com \
--cc=ustc.gu@gmail.com \
/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®