From: Myeonghun Pak <mhun512@gmail.com>
To: Mark Brown <broonie@kernel.org>, Liam Girdwood <lgirdwood@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, Ijae Kim <ae878000@gmail.com>,
Cyril Chao <Cyril.Chao@mediatek.com>,
Darren Ye <darren.ye@mediatek.com>,
Jiaxin Yu <jiaxin.yu@mediatek.com>,
Trevor Wu <trevor.wu@mediatek.com>
Subject: [PATCH v2 0/5] ASoC: mediatek: fix AFE IRQ registration and removal ordering
Date: Thu, 12 Nov 2026 01:17:44 -0500 [thread overview]
Message-ID: <20261112011708-afe-v2-0-mhun512@gmail.com> (raw)
This series fixes IRQ lifetime ordering in the MT8186, MT8188, MT8189,
MT8195 and MT8196 AFE drivers.
Request each IRQ after regmap initialization so it is freed before
the regmap. Where remove() shuts down the AFE, free the IRQ first.
Also balance MT8186's IRQ wake setting.
Found by a static analysis tool under development.
Not tested on hardware.
Changes in v2:
- Rebased onto broonie/sound for-next (cde5523c75f1).
- 1-3: removed redundant IRQ request error logs and clarified changelogs.
- 4-5: added MT8195 and MT8188.
Link to v1: https://lore.kernel.org/r/20261011222234.2098904-1-mhun512@gmail.com
Myeonghun Pak (5):
ASoC: mediatek: mt8186: Keep the AFE IRQ within its resource lifetime
ASoC: mediatek: mt8189: Keep the AFE IRQ within its resource lifetime
ASoC: mediatek: mt8196: Keep the AFE IRQ within its resource lifetime
ASoC: mediatek: mt8195: Keep the AFE IRQ within its resource lifetime
ASoC: mediatek: mt8188: Keep the AFE IRQ within its resource lifetime
sound/soc/mediatek/mt8186/mt8186-afe-common.h | 1 +
sound/soc/mediatek/mt8186/mt8186-afe-pcm.c | 42 +++++++++++++------
sound/soc/mediatek/mt8188/mt8188-afe-pcm.c | 10 ++---
sound/soc/mediatek/mt8189/mt8189-afe-common.h | 1 +
sound/soc/mediatek/mt8189/mt8189-afe-pcm.c | 16 ++++---
sound/soc/mediatek/mt8195/mt8195-afe-common.h | 1 +
sound/soc/mediatek/mt8195/mt8195-afe-pcm.c | 16 ++++---
sound/soc/mediatek/mt8196/mt8196-afe-common.h | 1 +
sound/soc/mediatek/mt8196/mt8196-afe-pcm.c | 16 ++++---
9 files changed, 70 insertions(+), 34 deletions(-)
base-commit: cde5523c75f1320a55ac1d55a717ccbb566557f0
--
2.43.0
next reply other threads:[~2026-11-12 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 6:17 Myeonghun Pak [this message]
2026-11-12 6:17 ` [PATCH v2 1/5] ASoC: mediatek: mt8186: Keep the AFE IRQ within its resource lifetime Myeonghun Pak
2026-11-12 6:17 ` [PATCH v2 2/5] ASoC: mediatek: mt8189: " Myeonghun Pak
2026-11-12 6:17 ` [PATCH v2 3/5] ASoC: mediatek: mt8196: " Myeonghun Pak
2026-11-12 6:17 ` [PATCH v2 4/5] ASoC: mediatek: mt8195: " Myeonghun Pak
2026-11-12 6:17 ` [PATCH v2 5/5] ASoC: mediatek: mt8188: " Myeonghun Pak
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=20261112011708-afe-v2-0-mhun512@gmail.com \
--to=mhun512@gmail.com \
--cc=Cyril.Chao@mediatek.com \
--cc=ae878000@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=darren.ye@mediatek.com \
--cc=jiaxin.yu@mediatek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=trevor.wu@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