From: Mark Brown <broonie@kernel.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: alsa-devel@alsa-project.org, Stephen Warren <swarren@nvidia.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: dapm: check suspend state in dapm_dai_check_power()
Date: Mon, 3 Jun 2013 20:44:43 +0100 [thread overview]
Message-ID: <20130603194443.GU31367@sirena.org.uk> (raw)
In-Reply-To: <20130603185120.GS31367@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1168 bytes --]
On Mon, Jun 03, 2013 at 07:51:20PM +0100, Mark Brown wrote:
> I would expect us to be dealing with this as part of quiescing the DMA
> operations on the links - it's not just the CODEC that needs handling
> here. This feels like it ought to be more joined up somewhere along the
> line.
So having grovelled a bit this is of course more annoying than it should
be; the trigger operation is in atomic context and there's nowhere
convenient to react to it outside of suspend and resume. That said the
active flag is only being used for links started and stopped from
userspace so this change *ought* to be safe to do what you're doing but
it still doesn't seem terribly clever.
Another way of looking at things here is that the DAI widgets are
unusual in that they don't require a complete path to power them as
widgets generally do (including DACs and ADCs). If we fixed that
instead then everything would work just fine. This should just be a
case of splitting the playback and capture DAIs into separate widget
types and then using the existing DAC and ADC functions. I can't recall
why we didn't do that in the first place, it's probably just an
oversight...
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2013-06-03 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 17:36 [PATCH] ASoC: dapm: check suspend state in dapm_dai_check_power() Stephen Warren
2013-06-03 18:51 ` Mark Brown
2013-06-03 19:16 ` Lars-Peter Clausen
2013-06-03 19:46 ` Mark Brown
2013-06-03 19:44 ` Mark Brown [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=20130603194443.GU31367@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.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