From: Cezary Rojewski <cezary.rojewski@intel.com>
To: <phucduc.bui@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
<linux-sound@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Mark Brown <broonie@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>
Subject: Re: [PATCH v2 2/4] ASoC: mediatek: mt8183: Fix APLL enable error handling
Date: Wed, 26 Aug 2026 20:31:00 +0200 [thread overview]
Message-ID: <47c14ad6-0311-467b-907c-517ff5044438@intel.com> (raw)
In-Reply-To: <20260821122928.41343-3-phucduc.bui@gmail.com>
On 8/21/2026 2:29 PM, phucduc.bui@gmail.com wrote:
> From: bui duc phuc <phucduc.bui@gmail.com>
>
> Currently, the mt8183_apll*_enable() functions call mux_setting(afe, true)
> but do not check its return value to handle failures.
>
> In addition, the cleanup paths of mt8183_apll*_enable() do not call
> mux_setting(afe, false) when the enable operation fails, while the
> mt8183_apll*_disable() functions do.
>
> Add error handling for apll*_mux_setting() and call mux_setting(afe, false)
> in the cleanup paths when mt8183_apll*_enable() fails.
I have mixed feelings about appl*_mux_setting(). Take a look at its
disable-path: if clk_set_parent() fails the follow up
clk_disable_unprepare() is skipped possibly leaving one of the clks
hanging. I'd expect error paths of callers (of said mux_setting()
function) to ensure all the clks are disabled and unprepared
unconditionally.
> Fixes: a94aec035a12 ("ASoC: mediatek: mt8183: add platform driver")
> Signed-off-by: bui duc phuc <phucduc.bui@gmail.com>
> ---
> sound/soc/mediatek/mt8183/mt8183-afe-clk.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/mediatek/mt8183/mt8183-afe-clk.c b/sound/soc/mediatek/mt8183/mt8183-afe-clk.c
> index 6ab0734ad136..0790d8123179 100644
> --- a/sound/soc/mediatek/mt8183/mt8183-afe-clk.c
> +++ b/sound/soc/mediatek/mt8183/mt8183-afe-clk.c
> @@ -382,7 +382,9 @@ int mt8183_apll1_enable(struct mtk_base_afe *afe)
> int ret;
>
> /* setting for APLL */
> - apll1_mux_setting(afe, true);
> + ret = apll1_mux_setting(afe, true);
> + if (ret)
> + goto ERR_APLL1_MUX_SETTING;
Why goto? The check is valid but the label in my opinion is unnecessary.
>
> ret = clk_prepare_enable(afe_priv->clk[CLK_APLL22M]);
> if (ret) {
> @@ -411,6 +413,8 @@ int mt8183_apll1_enable(struct mtk_base_afe *afe)
> ERR_CLK_APLL1_TUNER:
> clk_disable_unprepare(afe_priv->clk[CLK_APLL22M]);
> ERR_CLK_APLL22M:
> + apll1_mux_setting(afe, false);
> +ERR_APLL1_MUX_SETTING:
While UPPER case for goto-labels is not part of the coding style I see
why you did it - to be cohesive with the rest of the file.
next prev parent reply other threads:[~2026-08-26 18:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 12:29 [PATCH v2 0/4] ASoC: mediatek: mt8183: Fix clock error handling phucduc.bui
2026-08-21 12:29 ` [PATCH v2 1/4] ASoC: mediatek: mt8183: Fix wrong clock cleanup on clk_set_parent() failure phucduc.bui
2026-08-26 18:40 ` Cezary Rojewski
2026-08-21 12:29 ` [PATCH v2 2/4] ASoC: mediatek: mt8183: Fix APLL enable error handling phucduc.bui
2026-08-26 18:31 ` Cezary Rojewski [this message]
2026-08-27 7:58 ` Bui Duc Phuc
2026-08-27 16:28 ` Mark Brown
2026-08-28 4:13 ` Bui Duc Phuc
2026-08-21 12:29 ` [PATCH v2 3/4] ASoC: mediatek: mt8183: Use dev_err_probe() for " phucduc.bui
2026-08-26 18:32 ` Cezary Rojewski
2026-08-21 12:29 ` [PATCH v2 4/4] ASoC: mediatek: mt8183: Drop redundant probe error messages phucduc.bui
2026-08-26 18:33 ` Cezary Rojewski
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=47c14ad6-0311-467b-907c-517ff5044438@intel.com \
--to=cezary.rojewski@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--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=phucduc.bui@gmail.com \
--cc=tiwai@suse.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