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>,
Tiffany Lin <tiffany.lin@mediatek.com>,
Yunfei Dong <yunfei.dong@mediatek.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
linux-media@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-kernel@vger.kernel.org, Johan Hovold <johan@kernel.org>
Subject: [PATCH 0/3] media: mediatek: fix VPU device leaks on probe
Date: Wed, 24 Sep 2025 15:35:49 +0200 [thread overview]
Message-ID: <20250924133552.28841-1-johan@kernel.org> (raw)
This series fixes VPU device leaks during probe of the mdp and two codec
drivers.
Included is also a minor documentation update to make it clear that the
VPU lookup helper returns the device with an incremented refcount.
Johan
Johan Hovold (3):
media: mediatek: vcodec: fix device leak on codec init
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 +++++--
.../mediatek/vcodec/common/mtk_vcodec_fw_vpu.c | 13 +++++++++++++
drivers/media/platform/mediatek/vpu/mtk_vpu.h | 2 +-
3 files changed, 19 insertions(+), 3 deletions(-)
--
2.49.1
next reply other threads:[~2025-09-24 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 13:35 Johan Hovold [this message]
2025-09-24 13:35 ` [PATCH 1/3] media: mediatek: vcodec: fix device leak on codec init Johan Hovold
2025-09-24 13:35 ` [PATCH 2/3] media: mediatek: mdp: fix device leak on probe Johan Hovold
2025-09-24 13:35 ` [PATCH 3/3] media: mediatek: amend vpu_get_plat_device() documentation Johan Hovold
2025-09-25 4:54 ` [PATCH 0/3] media: mediatek: fix VPU device leaks on probe Chen-Yu Tsai
2025-10-27 13:37 ` Johan Hovold
2025-10-27 19:29 ` Nicolas Dufresne
2025-10-28 8:21 ` Johan Hovold
2025-10-28 9:32 ` 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=20250924133552.28841-1-johan@kernel.org \
--to=johan@kernel.org \
--cc=andrew-ct.chen@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=hans.verkuil@cisco.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=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 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.