From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: 朱灿灿 <zhucancan@vivo.com>,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Cc: kernel <kernel@vivo.com>, 王文虎 <wenhu.wang@vivo.com>, trivial@kernel.org
Subject: Re: Subject: [PATCH v2] ASoC: soc-pcm: fix BE dai not hw_free and shutdown during mixer update
Date: Tue, 2 Jun 2020 11:19:56 -0500 [thread overview]
Message-ID: <338690ee-a081-054c-36e3-3f5fb3733442@linux.intel.com> (raw)
In-Reply-To: <ALMAWwB5CP9aAcKXCU5FzqqF.1.1590747164172.Hmail.zhucancan@vivo.com>
On 5/29/20 5:12 AM, 朱灿灿 wrote:
> FE state is SND_SOC_DPCM_STATE_PREPARE now, BE1 is
> used by FE.
>
> Later when new BE2 is added to FE by mixer update,
> it will call dpcm_run_update_startup() to update
> BE2's state, but unfortunately BE2 .prepare() meets
> error, it will disconnect all non started BE.
>
> This make BE1 dai skip .hw_free() and .shutdown(),
> and the BE1 users will never decrease to zero.
>
> Signed-off-by: zhucancan <zhucancan@vivo.com>
> ---
> re-format patch content v2
> ---
> sound/soc/soc-pcm.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/sound/soc/soc-pcm.c b/sound/soc/soc-pcm.c
> index 1f302de44052..df34422bd0dd 100644
> --- a/sound/soc/soc-pcm.c
> +++ b/sound/soc/soc-pcm.c
> @@ -2730,12 +2730,12 @@ static int dpcm_run_update_startup(struct snd_soc_pcm_runtime *fe, int stream)
> close:
> dpcm_be_dai_shutdown(fe, stream);
> disconnect:
> - /* disconnect any non started BEs */
> + /* disconnect any closed BEs */
> spin_lock_irqsave(&fe->card->dpcm_lock, flags);
> for_each_dpcm_be(fe, stream, dpcm) {
> struct snd_soc_pcm_runtime *be = dpcm->be;
> - if (be->dpcm[stream].state != SND_SOC_DPCM_STATE_START)
> - dpcm->state = SND_SOC_DPCM_LINK_STATE_FREE;
> + if (be->dpcm[stream].state == SND_SOC_DPCM_STATE_CLOSE)
> + dpcm->state = SND_SOC_DPCM_LINK_STATE_FREE;
> }
> spin_unlock_irqrestore(&fe->card->dpcm_lock, flags);
This change is quite hard to review, this error handling can be called
from multiple places.
I *think* it's correct because in all cases where the
disconnect/close/hw_free labels are reached, the non-shared BEs either
remain or are put in the DPCM_STATE_CLOSE state before doing this test.
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
It really wouldn't hurt though if others double-checked this change...
prev parent reply other threads:[~2020-06-02 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 10:12 朱灿灿
2020-06-02 16:19 ` Pierre-Louis Bossart [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=338690ee-a081-054c-36e3-3f5fb3733442@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kernel@vivo.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=trivial@kernel.org \
--cc=wenhu.wang@vivo.com \
--cc=zhucancan@vivo.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
Powered by JetHome