All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
	alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH] ASoC: Intel: Add support for PM ops in bxt-da7219_max98357a
Date: Mon, 20 Jun 2016 19:32:53 +0530	[thread overview]
Message-ID: <20160620140253.GR16910@localhost> (raw)
In-Reply-To: <20160620132640.GT26099@sirena.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 878 bytes --]

On Mon, Jun 20, 2016 at 02:26:40PM +0100, Mark Brown wrote:
> On Mon, Jun 20, 2016 at 05:14:29PM +0530, Vinod Koul wrote:
> > On Fri, Jun 17, 2016 at 01:31:56PM +0100, Mark Brown wrote:
> > > On Fri, Jun 17, 2016 at 05:45:48PM +0530, Vinod Koul wrote:
> > > > On Fri, Jun 17, 2016 at 01:18:10PM +0200, Lars-Peter Clausen wrote:
> 
> > > > > Why and why is this something that other cards do not need to do?
> 
> > Other systems do not have a DSP sitting and need to redownload code which
> > takes time and results in card being resumed even when the platform is not
> > ready.
> 
> So what you're actually trying to do here is serialize the resume - this
> isn't just a thing with DSPs, it's also a thing with I2C, regulators and
> so on.  A quick glance suggests that disabling async suspend might help
> here.

Okay let me check that

Thanks
-- 
~Vinod

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2016-06-20 13:56 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
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 [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=20160620140253.GR16910@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.