From: Johan Hovold <johan@kernel.org>
To: Minghsiu Tsai <minghsiu.tsai@mediatek.com>,
Houlong Wei <houlong.wei@mediatek.com>,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Tiffany Lin <tiffany.lin@mediatek.com>,
Yunfei Dong <yunfei.dong@mediatek.com>,
Nicolas Dufresne <nicolas@ndufresne.ca>,
linux-media@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-kernel@vger.kernel.org, Johan Hovold <johan@kernel.org>
Subject: [PATCH v2 0/2] media: mediatek: fix VPU device leaks on probe
Date: Tue, 28 Oct 2025 11:04:52 +0100 [thread overview]
Message-ID: <20251028100454.4086-1-johan@kernel.org> (raw)
This series fixes VPU device leaks during probe of the mdp driver.
Included is also a minor documentation update to make it clear that the
VPU lookup helper returns the device with an incremented refcount.
Johan
Changes in v2
- drop incorrect vcodec patch since that reference leak has already
been fixed by commit bf1d556ad4e0 ("media: mtk-vcodec: abstract
firmware interface") which added the codec release callback
Johan Hovold (2):
media: mediatek: mdp: fix device leak on probe
media: mediatek: amend vpu_get_plat_device() documentation
drivers/media/platform/mediatek/mdp/mtk_mdp_core.c | 7 +++++--
drivers/media/platform/mediatek/vpu/mtk_vpu.h | 2 +-
2 files changed, 6 insertions(+), 3 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-28 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 10:04 Johan Hovold [this message]
2025-10-28 10:04 ` [PATCH v2 1/2] media: mediatek: mdp: fix device leak on probe Johan Hovold
2025-10-28 10:04 ` [PATCH v2 2/2] media: mediatek: amend vpu_get_plat_device() documentation Johan Hovold
2025-11-05 8:07 ` [PATCH v2 0/2] media: mediatek: fix VPU device leaks on probe Johan Hovold
2025-11-05 12:31 ` AngeloGioacchino Del Regno
2025-11-20 13:14 ` Johan Hovold
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=20251028100454.4086-1-johan@kernel.org \
--to=johan@kernel.org \
--cc=andrew-ct.chen@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=houlong.wei@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=minghsiu.tsai@mediatek.com \
--cc=nicolas@ndufresne.ca \
--cc=tiffany.lin@mediatek.com \
--cc=yunfei.dong@mediatek.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;
as well as URLs for NNTP newsgroup(s).