From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Bensaid, Selma" <selma.bensaid@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: : Question cpu_dai->active & codec_dai->active
Date: Fri, 11 Mar 2011 15:31:00 +0000 [thread overview]
Message-ID: <20110311153059.GN1760@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <2A84145621092446B6659B8A0F28E26F4703F71706@irsmsx501.ger.corp.intel.com>
On Fri, Mar 04, 2011 at 11:04:20AM +0000, Bensaid, Selma wrote:
> Why the cpu_dai->active and codec_dai->active are not used to check if
> the corresponding shutdown or startup callbacks should be called or not?
> This could be useful for DAIs that handle capture and playback streams by avoiding:
> - perform 2 cpu_dai or codec_dai startup when opening both streams (playback and
> Capture)
> - close a cpu_dai or codec_dai for a stream (example playback) while
> the 2nd stream (playback) is still running
It's done to allow the driver to make the decision about needing to do
anything - some drivers may need to do per-stream things, those that
don't can work out if they need to do anything. If it became very
common we could add variants that only get called once but at the minute
we have very few things that support multiple streams in the first
place.
prev parent reply other threads:[~2011-03-11 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 11:04 : Question cpu_dai->active & codec_dai->active Bensaid, Selma
2011-03-11 15:31 ` 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=20110311153059.GN1760@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=selma.bensaid@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.