Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Shengjiu Wang <shengjiu.wang@freescale.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] PCM: snd_pcm_dmix_drain() maybe blocked after suspend and resume
Date: Tue, 09 Jun 2015 07:27:24 +0200	[thread overview]
Message-ID: <s5hegllbgeb.wl-tiwai@suse.de> (raw)
In-Reply-To: <20150609023539.GA3277@shlinux2>

At Tue, 9 Jun 2015 10:35:41 +0800,
Shengjiu Wang wrote:
> 
> On Mon, Jun 08, 2015 at 01:31:41PM +0200, Takashi Iwai wrote:
> > At Mon, 8 Jun 2015 17:38:11 +0800,
> > Shengjiu Wang wrote:
> > > 
> > > After suspend and resume, the alsa driver is stopped. But if alsa-lib run
> > > into snd_pcm_dmix_drain(), it need to wait avail >= pcm->stop_threshold,
> > > otherwise, it will not exit the loop, so finally it is blocked at poll() of
> > > snd_pcm_wait_nocheck(pcm, -1).
> > > This patch is to add state check after snd_pcm_wait_nocheck(pcm, -1), if
> > > the state is SND_PCM_STATE_SUSPENDED, then return error.
> > > 
> > > Signed-off-by: Shengjiu Wang <shengjiu.wang@freescale.com>
> > > ---
> > >  src/pcm/pcm_dmix.c |    6 ++++++
> > >  1 file changed, 6 insertions(+)
> > > 
> > > diff --git a/src/pcm/pcm_dmix.c b/src/pcm/pcm_dmix.c
> > > index babde6a..0cc318e 100644
> > > --- a/src/pcm/pcm_dmix.c
> > > +++ b/src/pcm/pcm_dmix.c
> > > @@ -647,6 +647,12 @@ static int snd_pcm_dmix_drain(snd_pcm_t *pcm)
> > >  		if (dmix->state == SND_PCM_STATE_DRAINING) {
> > >  			snd_pcm_dmix_sync_area(pcm);
> > >  			snd_pcm_wait_nocheck(pcm, -1);
> > > +			switch (snd_pcm_state(pcm)) {
> > 
> > It's better (shorter) to call snd_pcm_state(dmix->spcm) in this case.
> > 
> > And, I think we should have the check of SND_PCM_STATE_SUSPENDED at
> > the beginning of snd_pcm_dmix_drain() before entering to the loop,
> > too.
> > 
> > Last but not least, the very same bug is present for dshare.  Could
> > you fix this together?
> > 
> Ok, I will refine the patch. But one thing I don't understand is that why need
> to check the SND_PCM_STATE_SUSPENDED before entering the loop, seems check the
> state in the loop can resolve the issue.

It's just a minor optimization.  The check isn't done at the beginning
of the loop but after a few other calls (sync_ptr and sync_area) to be
skipped at PM.


Takashi

      reply	other threads:[~2015-06-09  5:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08  9:38 [PATCH] PCM: snd_pcm_dmix_drain() maybe blocked after suspend and resume Shengjiu Wang
2015-06-08 11:31 ` Takashi Iwai
2015-06-09  2:35   ` Shengjiu Wang
2015-06-09  5:27     ` Takashi Iwai [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=s5hegllbgeb.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=shengjiu.wang@freescale.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