From: dgreid@chromium.org (Dylan Reid)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: samsung dma - prepare dma in start/resume trigger path
Date: Thu, 23 Aug 2012 13:51:09 -0700 [thread overview]
Message-ID: <1345755069-9512-1-git-send-email-dgreid@chromium.org> (raw)
On suspend all dma transactions are terminated (by the stop/suspend
trigger calling ops->stop), they need to be set up again during resume.
Move the prepare op to the start/resume/unpause trigger path so that dma
and audio will restart on resume/unpause.
Signed-off-by: Dylan Reid <dgreid@chromium.org>
---
sound/soc/samsung/dma.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/sound/soc/samsung/dma.c b/sound/soc/samsung/dma.c
index f3ebc38..5772762 100644
--- a/sound/soc/samsung/dma.c
+++ b/sound/soc/samsung/dma.c
@@ -250,6 +250,7 @@ static int dma_trigger(struct snd_pcm_substream *substream, int cmd)
case SNDRV_PCM_TRIGGER_START:
case SNDRV_PCM_TRIGGER_RESUME:
case SNDRV_PCM_TRIGGER_PAUSE_RELEASE:
+ dma_prepare(substream);
prtd->state |= ST_RUNNING;
prtd->params->ops->trigger(prtd->params->ch);
break;
@@ -352,7 +353,6 @@ static struct snd_pcm_ops dma_ops = {
.ioctl = snd_pcm_lib_ioctl,
.hw_params = dma_hw_params,
.hw_free = dma_hw_free,
- .prepare = dma_prepare,
.trigger = dma_trigger,
.pointer = dma_pointer,
.mmap = dma_mmap,
--
1.7.7.3
next reply other threads:[~2012-08-23 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 20:51 Dylan Reid [this message]
2012-08-23 20:54 ` [PATCH] ASoC: samsung dma - prepare dma in start/resume trigger path Dylan Reid
2012-08-24 7:15 ` [alsa-devel] " Clemens Ladisch
2012-08-24 7:41 ` Sangbeom Kim
2012-08-24 7:52 ` Dylan Reid
2012-08-24 10:06 ` Sangbeom Kim
2012-08-24 17:29 ` Dylan Reid
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=1345755069-9512-1-git-send-email-dgreid@chromium.org \
--to=dgreid@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).