From: Jarkko Nikula <jhnikula@gmail.com>
To: Jane Wang <jwang@ti.com>
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
peter.ujfalusi@nokia.com, broonie@opensource.wolfsonmicro.com
Subject: Re: [PATCH 2/2] ASoC: OMAP: reconfigure DMA to resume audio
Date: Sat, 14 Nov 2009 10:36:28 +0200 [thread overview]
Message-ID: <20091114103628.51476f3d.jhnikula@gmail.com> (raw)
In-Reply-To: <1258135323-20523-1-git-send-email-jwang@ti.com>
Hi
On Fri, 13 Nov 2009 12:02:03 -0600
Jane Wang <jwang@ti.com> wrote:
> Reconfigure DMA transfer parameters to resume audio after system comming out of OFF state.
>
> Signed-off-by: Jane Wang <jwang@ti.com>
> ---
> sound/soc/omap/omap-pcm.c | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/sound/soc/omap/omap-pcm.c b/sound/soc/omap/omap-pcm.c
> index 6a829ee..5e04390 100644
> --- a/sound/soc/omap/omap-pcm.c
> +++ b/sound/soc/omap/omap-pcm.c
> @@ -215,8 +215,13 @@ static int omap_pcm_trigger(struct snd_pcm_substream *substream, int cmd)
>
> spin_lock_irqsave(&prtd->lock, flags);
> switch (cmd) {
> - case SNDRV_PCM_TRIGGER_START:
> case SNDRV_PCM_TRIGGER_RESUME:
> + /* Reconfigure DMA transfer parameters
> + * in order to come back from OFF mode
> + */
> + omap_pcm_prepare(substream);
> + /* fall through */
Again looks simple workaround for the audio case for restoring the
DMA context but how about all other DMA clients if the low-level DMA
module expects that the clients must do the context restore?
I'm not the PM expert but I think only need for PM in omap-pcm.c or
omap-mcbsp.c would be to dealing with possible suspend/resume order not
to bring up the low-level module back alive.
--
Jarkko
next prev parent reply other threads:[~2009-11-14 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 18:02 [PATCH 2/2] ASoC: OMAP: reconfigure DMA to resume audio Jane Wang
2009-11-14 8:36 ` Jarkko Nikula [this message]
[not found] <1258056918-19769-1-git-send-email-jwang@ti.com>
2009-11-13 13:50 ` Mark Brown
2009-11-13 17:48 ` Wang, Jane
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=20091114103628.51476f3d.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jwang@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@nokia.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