All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shengjiu Wang <shengjiu.wang@nxp.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] pcm: Don't store the state for SND_PCM_STATE_SUSPENDED
Date: Tue, 24 May 2016 10:12:49 +0000	[thread overview]
Message-ID: <DB5PR04MB212063DBF8904F58516C3137E34F0@DB5PR04MB2120.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <s5hr3cwkdh6.wl-tiwai@suse.de>

Hi

> -----Original Message-----
> From: Takashi Iwai [mailto:tiwai@suse.de]
> Sent: Friday, May 20, 2016 10:32 PM
> To: Shengjiu Wang
> Cc: perex@perex.cz; alsa-devel@alsa-project.org
> Subject: Re: [PATCH] pcm: Don't store the state for
> SND_PCM_STATE_SUSPENDED
> 
> On Fri, 20 May 2016 12:46:37 +0200,
> Takashi Iwai wrote:
> >
> > On Fri, 20 May 2016 11:41:25 +0200,
> > Shengjiu Wang wrote:
> > >
> > > Hi Takashi
> > >
> > >    I tested your patch, after suspend and resume, the playback is
> stopped.
> > > It is caused by the DMA. DMA is not started after resume.
> > >
> > > With your patch, DMA is not terminated but then is re-started. The
> driver don't
> > > support this behavior.
> >
> > If so, it's simply a driver bug.  Blame the kernel driver instead.
> 
> Which driver did you see the problem?  We should fix it.

But my thought is when suspended, the dmaengine_pause() is called, then
dmaengine_resume() should be called in resume(). If there is no resume()
Just call the prepare() and start(), it seems not reasonable. What do
you think?

Best regards
Wang shengjiu
> 
> 
> thanks,
> 
> Takashi

  reply	other threads:[~2016-05-24 10:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10  7:45 [PATCH] pcm: Don't store the state for SND_PCM_STATE_SUSPENDED Shengjiu Wang
2016-05-10  8:22 ` Takashi Iwai
2016-05-11  2:28   ` Shengjiu Wang
2016-05-11  5:15     ` Takashi Iwai
2016-05-11  6:24       ` Shengjiu Wang
2016-05-11  7:13         ` Takashi Iwai
2016-05-18  5:48           ` Shengjiu Wang
2016-05-18  8:49             ` Takashi Iwai
2016-05-20  7:27               ` Takashi Iwai
2016-05-20 10:03                 ` Shengjiu Wang
2016-05-20  9:41               ` Shengjiu Wang
2016-05-20 10:46                 ` Takashi Iwai
2016-05-20 14:31                   ` Takashi Iwai
2016-05-24 10:12                     ` Shengjiu Wang [this message]
2016-05-24 10:18                       ` Takashi Iwai
2016-05-28  8:46                         ` Takashi Iwai
2016-05-31  9:27                           ` Shengjiu Wang
2016-05-31 10:52                             ` Takashi Iwai
2016-06-01  3:10                               ` Shengjiu Wang
2016-06-01  5:15                                 ` Takashi Iwai
2016-05-31  7:30                         ` Shengjiu Wang
2016-05-31  7:47                           ` Takashi Iwai

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=DB5PR04MB212063DBF8904F58516C3137E34F0@DB5PR04MB2120.eurprd04.prod.outlook.com \
    --to=shengjiu.wang@nxp.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.