Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>
To: phucduc.bui@gmail.com, 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,
	Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>,
	Liviu Dudau <liviu.dudau@arm.com>,
	Haotian Zhang <vulab@iscas.ac.cn>,
	HariKrishna Sagala <hariconscious@gmail.com>,
	linux-sound@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 14/14] ASoC: mediatek: mt8195: Fix clock parent error handling
Date: Thu, 8 Oct 2026 17:33:47 +0530	[thread overview]
Message-ID: <24ffbf82-adad-4153-a2b9-f2123189c722@oss.qualcomm.com> (raw)
In-Reply-To: <20261005110257.50145-15-phucduc.bui@gmail.com>



On 10/5/2026 4:32 PM, phucduc.bui@gmail.com wrote:
> From: bui duc phuc <phucduc.bui@gmail.com>
> 
> Propagate the error returned by mt8195_afe_set_clk_parent() instead of
> ignoring it.
> 
> This allows clock parent configuration failures to be properly handled
> by the caller.
> 
> Fixes: 3de3eba588bb ("ASoC: mediatek: mt8195: support adda in platform driver")
> Signed-off-by: bui duc phuc <phucduc.bui@gmail.com>
> ---
>   sound/soc/mediatek/mt8195/mt8195-dai-adda.c | 3 +--
>   1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/sound/soc/mediatek/mt8195/mt8195-dai-adda.c b/sound/soc/mediatek/mt8195/mt8195-dai-adda.c
> index 94abde15ea09..8a58a142064d 100644
> --- a/sound/soc/mediatek/mt8195/mt8195-dai-adda.c
> +++ b/sound/soc/mediatek/mt8195/mt8195-dai-adda.c
> @@ -262,9 +262,8 @@ static int mtk_audio_hires_event(struct snd_soc_dapm_widget *w,
>   	default:
>   		return 0;
>   	}
> -	mt8195_afe_set_clk_parent(afe, clk, clk_parent);
>   
> -	return 0;
> +	return mt8195_afe_set_clk_parent(afe, clk, clk_parent);


The commit message says this allows clock parent configuration failures
to be properly handled by the caller, but I don't think the current DAPM
event path propagates this error back to the operation that triggered 
the power change.

mtk_audio_hires_event() now returns the error from 
mt8195_afe_set_clk_parent(), but the caller in the DAPM core is
dapm_seq_check_event(), which is a void helper. It logs a negative event
return with "event failed", but it does not return that error up through
the DAPM sequencing path.

So this looks like it improves error reporting, but not actual failure
handling/propagation. Was the intent only to get the DAPM error log 
here, or should the commit message/code be adjusted so the behavior 
matches the "properly handled by the caller" wording?

Thanks
Ajay Kumar Nandam

>   }
>   
>   static struct mtk_dai_adda_priv *get_adda_priv_by_name(struct mtk_base_afe *afe,



  reply	other threads:[~2026-10-08 12:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 11:02 [PATCH v2 00/14] ASoC: mediatek: mt8195: Fix clock error handling phucduc.bui
2026-10-05 11:02 ` [PATCH v2 01/14] ASoC: mediatek: mt8195: Fix tuner " phucduc.bui
2026-10-08 11:21   ` Ajay Kumar Nandam
2026-10-09  7:03     ` Bui Duc Phuc
2026-10-05 11:02 ` [PATCH v2 02/14] ASoC: mediatek: mt8195: Use dev_err_probe() in mt8195_afe_init_clock() phucduc.bui
2026-10-08 11:23   ` Ajay Kumar Nandam
2026-10-05 11:02 ` [PATCH v2 03/14] ASoC: mediatek: mt8195: Fix register access clock error handling phucduc.bui
2026-10-08 11:25   ` Ajay Kumar Nandam
2026-10-05 11:02 ` [PATCH v2 04/14] ASoC: mediatek: mt8195: Fix timing system " phucduc.bui
2026-10-05 11:02 ` [PATCH v2 05/14] ASoC: mediatek: mt8195: Fix paired memif " phucduc.bui
2026-10-08 11:42   ` Ajay Kumar Nandam
2026-10-09  7:11     ` Bui Duc Phuc
2026-10-05 11:02 ` [PATCH v2 06/14] ASoC: mediatek: mt8195: Fix FE startup " phucduc.bui
2026-10-05 11:02 ` [PATCH v2 07/14] ASoC: mediatek: mt8195: Fix runtime resume " phucduc.bui
2026-10-05 11:02 ` [PATCH v2 08/14] ASoC: mediatek: mt8195: Remove redundant error message phucduc.bui
2026-10-08 11:48   ` Ajay Kumar Nandam
2026-10-05 11:02 ` [PATCH v2 09/14] ASoC: mediatek: mt8195: Propagate IRQ lookup errors phucduc.bui
2026-10-08 11:50   ` Ajay Kumar Nandam
2026-10-05 11:02 ` [PATCH v2 10/14] ASoC: mediatek: mt8195: Fix ETDM MCLK error handling phucduc.bui
2026-10-08 11:54   ` Ajay Kumar Nandam
2026-10-05 11:02 ` [PATCH v2 11/14] ASoC: mediatek: mt8195: Fix ETDM startup " phucduc.bui
2026-10-08 11:55   ` Ajay Kumar Nandam
2026-10-05 11:02 ` [PATCH v2 12/14] ASoC: mediatek: mt8195: Fix HDMI TX " phucduc.bui
2026-10-05 11:02 ` [PATCH v2 13/14] ASoC: mediatek: mt8195: Fix ETDM probe " phucduc.bui
2026-10-05 11:02 ` [PATCH v2 14/14] ASoC: mediatek: mt8195: Fix clock parent " phucduc.bui
2026-10-08 12:03   ` Ajay Kumar Nandam [this message]
2026-10-09  7:21     ` Bui Duc Phuc

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=24ffbf82-adad-4153-a2b9-f2123189c722@oss.qualcomm.com \
    --to=ajay.nandam@oss.qualcomm.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=broonie@kernel.org \
    --cc=cassiogabrielcontato@gmail.com \
    --cc=hariconscious@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=liviu.dudau@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=mukesh.ojha@oss.qualcomm.com \
    --cc=perex@perex.cz \
    --cc=phucduc.bui@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox