From: Srinivas Kandagatla <srini@kernel.org>
To: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>,
Srinivas Kandagatla <srini@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@oss.qualcomm.com, prasad.kumpatla@oss.qualcomm.com,
ajay.nandam@oss.qualcomm.com, stable@vger.kernel.org
Subject: Re: [PATCH v1] ASoC: soc-pcm: Fix mute and unmute control for non-dynamic DAI links
Date: Wed, 8 Oct 2025 17:12:37 +0100 [thread overview]
Message-ID: <317f4edc-0592-492f-8c3d-f0cdb0d013cd@kernel.org> (raw)
In-Reply-To: <b257d715-cc12-46cc-ba31-7f7fc257f763@oss.qualcomm.com>
On 10/8/25 5:08 PM, Mohammad Rafi Shaik wrote:
>
>
> On 10/8/2025 7:16 PM, Srinivas Kandagatla wrote:
>>
>>
>> On 10/7/25 3:33 AM, Mohammad Rafi Shaik wrote:
>>> In setups where the same codec DAI is reused across multiple DAI
>>> links, mute controls via `snd_soc_dai_digital_mute()` is skipped for
>>
>> Please explain the problem.
>>
> In Qualcomm audioreach setup, if platform dai not specified in DT, then
> cpu dai using as platform and initialize as static dai-link and created
> pcm device and link-dynamic == false by default.
>
> In existing setup if dynamic==false, it's skipping trigger snd-ops and
> the codec is always on mute state.
>
>>> non-dynamic links. The trigger operations are not invoked when
>>> `dai_link->dynamic == 0`, and mute controls is currently conditioned
>>
>> I dont think any of the Qualcomm upstream platforms use this flag.
>>
>
> Yes, we are using dynamic flag and it's set to true in Qualcomm platforms.
>
> Please check: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/
> sound.git/tree/sound/soc/qcom/qdsp6/topology.c#n1093
>
>>> only on `snd_soc_dai_mute_is_ctrled_at_trigger()`. This patch ensures
>>> that mute and unmute is applied explicitly for non-dynamic links.
>> How is this resolving the issue, mute on these codecs happens at trigger
>> level instead of prepare.
>>
> yes agree, but if link->dynamic==false the trigger ops not getting
> called, which leading to codec always on mute state.
This is because you are using something very different solution to what
ASoC kernel provides.
I dont think this is a problem with as long as you use kernel ABI..
This patch looks totally a hack from something that does not belong to
kernel, so is NAK from my side on this.
--srini
>
> Thanks & Regards,
> Rafi.
>
>> --srini
>>>
>>> Fixes: f0220575e65a ("ASoC: soc-dai: add flag to mute and unmute
>>> stream during trigger")
>>> Cc: stable@vger.kernel.org
>>> Signed-off-by: Mohammad Rafi Shaik
>>> <mohammad.rafi.shaik@oss.qualcomm.com>
>>> ---
>>> sound/soc/soc-pcm.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/sound/soc/soc-pcm.c b/sound/soc/soc-pcm.c
>>> index 2c21fd528afd..4ed829b49bc2 100644
>>> --- a/sound/soc/soc-pcm.c
>>> +++ b/sound/soc/soc-pcm.c
>>> @@ -949,7 +949,7 @@ static int __soc_pcm_prepare(struct
>>> snd_soc_pcm_runtime *rtd,
>>> SND_SOC_DAPM_STREAM_START);
>>> for_each_rtd_dais(rtd, i, dai) {
>>> - if (!snd_soc_dai_mute_is_ctrled_at_trigger(dai))
>>> + if (!snd_soc_dai_mute_is_ctrled_at_trigger(dai) || !rtd-
>>> >dai_link->dynamic)
>>> snd_soc_dai_digital_mute(dai, 0, substream->stream);
>>> }
>>> @@ -1007,7 +1007,7 @@ static int soc_pcm_hw_clean(struct
>>> snd_soc_pcm_runtime *rtd,
>>> soc_pcm_set_dai_params(dai, NULL);
>>> if (snd_soc_dai_stream_active(dai, substream->stream) ==
>>> 1) {
>>> - if (!snd_soc_dai_mute_is_ctrled_at_trigger(dai))
>>> + if (!snd_soc_dai_mute_is_ctrled_at_trigger(dai) || !rtd-
>>> >dai_link->dynamic)
>>> snd_soc_dai_digital_mute(dai, 1, substream->stream);
>>> }
>>> }
>>
>
prev parent reply other threads:[~2025-10-08 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 2:33 Mohammad Rafi Shaik
2025-10-08 13:46 ` Srinivas Kandagatla
2025-10-08 16:08 ` Mohammad Rafi Shaik
2025-10-08 16:12 ` Srinivas Kandagatla [this message]
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=317f4edc-0592-492f-8c3d-f0cdb0d013cd@kernel.org \
--to=srini@kernel.org \
--cc=ajay.nandam@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=kernel@oss.qualcomm.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mohammad.rafi.shaik@oss.qualcomm.com \
--cc=perex@perex.cz \
--cc=prasad.kumpatla@oss.qualcomm.com \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®