All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
	alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH] ASoC: Intel: Add support for PM ops in bxt-da7219_max98357a
Date: Fri, 17 Jun 2016 17:45:48 +0530	[thread overview]
Message-ID: <20160617121548.GI16910@localhost> (raw)
In-Reply-To: <5763DC72.1060200@metafoo.de>

On Fri, Jun 17, 2016 at 01:18:10PM +0200, Lars-Peter Clausen wrote:
> On 06/17/2016 06:33 AM, Vinod Koul wrote:
> > We need card to be early suspended and late resumed, so use
> > prepare and complete for card suspend and resume.
> 
> Why and why is this something that other cards do not need to do?

When card suspends, the DAPM suspend closes the widgets, which translates to
we sending IPC to DSP for tearing down the pipelines.

So we need the platform to be suspended last and resume first. This way the
snd_soc_suspend will tear down pipelines and snd_soc_resume restore those
back.

Thanks
-- 
~Vinod

  reply	other threads:[~2016-06-17 12:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17  4:33 [PATCH] ASoC: Intel: Add support for PM ops in bxt-da7219_max98357a Vinod Koul
2016-06-17 11:14 ` Mark Brown
2016-06-17 12:14   ` Vinod Koul
2016-06-17 12:35     ` Mark Brown
2016-06-20 11:47       ` Vinod Koul
2016-06-17 11:18 ` Lars-Peter Clausen
2016-06-17 12:15   ` Vinod Koul [this message]
2016-06-17 12:31     ` Mark Brown
2016-06-20 11:44       ` Vinod Koul
2016-06-20 13:26         ` Mark Brown
2016-06-20 14:02           ` Vinod Koul

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=20160617121548.GI16910@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lars@metafoo.de \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@intel.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 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.