From: phucduc.bui@gmail.com
To: Mark Brown <broonie@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Trevor Wu <trevor.wu@mediatek.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
cassiogabrielcontato@gmail.com, Haotian Zhang <vulab@iscas.ac.cn>,
Christian Marangi <ansuelsmth@gmail.com>,
Cezary Rojewski <cezary.rojewski@intel.com>,
Cyril Chao <Cyril.Chao@mediatek.com>, Tuo Li <islituo@gmail.com>,
Rosen Penev <rosenp@gmail.com>,
Garlic Tseng <garlic.tseng@mediatek.com>,
Alexandre Mergnat <amergnat@baylibre.com>,
Dan Carpenter <error27@gmail.com>,
linux-sound@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
bui duc phuc <phucduc.bui@gmail.com>
Subject: [PATCH 0/4] ASoC: mediatek: Return 0 from FE startup on success
Date: Tue, 6 Oct 2026 17:16:02 +0700 [thread overview]
Message-ID: <20261006101606.54079-1-phucduc.bui@gmail.com> (raw)
From: bui duc phuc <phucduc.bui@gmail.com>
Hi all,
Some FE startup callbacks may return a positive value from constraint
helpers, but ASoC expects 0 on success. This can cause .shutdown() to be
skipped during rollback.
Return 0 explicitly on success.
Compile-tested only.
Best regards,
Phuc
bui duc phuc (4):
ASoC: mediatek: common: return 0 from mtk_afe_fe_startup() on success
ASoC: mediatek: mt8188: return 0 from mt8188_afe_fe_startup() on
success
ASoC: mediatek: mt8189:return 0 from mt8189_fe_startup() on success
ASoC: mediatek: mt8365: return 0 from mt8365_afe_fe_startup() on
success
sound/soc/mediatek/common/mtk-afe-fe-dai.c | 8 +++++---
sound/soc/mediatek/mt8188/mt8188-afe-pcm.c | 5 ++++-
sound/soc/mediatek/mt8189/mt8189-afe-pcm.c | 8 +++++---
sound/soc/mediatek/mt8365/mt8365-afe-pcm.c | 7 +++++--
4 files changed, 19 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2026-10-06 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 10:16 phucduc.bui [this message]
2026-10-06 10:16 ` [PATCH 1/4] ASoC: mediatek: common: return 0 from mtk_afe_fe_startup() on success phucduc.bui
2026-10-06 10:16 ` [PATCH 2/4] ASoC: mediatek: mt8188: return 0 from mt8188_afe_fe_startup() " phucduc.bui
2026-10-06 10:39 ` Cezary Rojewski
2026-10-06 11:09 ` Bui Duc Phuc
2026-10-06 10:16 ` [PATCH 3/4] ASoC: mediatek: mt8189:return 0 from mt8189_fe_startup() " phucduc.bui
2026-10-06 10:44 ` Cezary Rojewski
2026-10-06 11:18 ` Bui Duc Phuc
2026-10-06 10:16 ` [PATCH 4/4] ASoC: mediatek: mt8365: return 0 from mt8365_afe_fe_startup() " phucduc.bui
2026-10-08 9:10 ` [PATCH 0/4] ASoC: mediatek: Return 0 from FE startup " Mark Brown
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=20261006101606.54079-1-phucduc.bui@gmail.com \
--to=phucduc.bui@gmail.com \
--cc=Cyril.Chao@mediatek.com \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ansuelsmth@gmail.com \
--cc=broonie@kernel.org \
--cc=cassiogabrielcontato@gmail.com \
--cc=cezary.rojewski@intel.com \
--cc=error27@gmail.com \
--cc=garlic.tseng@mediatek.com \
--cc=islituo@gmail.com \
--cc=kuninori.morimoto.gx@renesas.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=rosenp@gmail.com \
--cc=tiwai@suse.com \
--cc=trevor.wu@mediatek.com \
--cc=vulab@iscas.ac.cn \
/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.