alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Harsha, Priya" <priya.harsha@intel.com>,
	"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/4] ASoC: sn95031: add capture support
Date: Wed, 19 Jan 2011 18:48:01 +0000	[thread overview]
Message-ID: <20110119184800.GC17150@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <438BB0150E931F4B9CE701519A446301084470BBD1@bgsmsx502.gar.corp.intel.com>

On Wed, Jan 19, 2011 at 09:58:11PM +0530, Koul, Vinod wrote:

> > How about using a supply widget for the LDO and the clock?  This would
> > also ensure that...

> Hmmm, so what you are saying is add a supply widget like we have "Headset" and
> which does above. I thought about that, but what I have here is ADC with NULL
> stream (to ensure ADCs are on only when AMICs are selected) and added virtual
> AIF with capture stream, and all TX paths (and thereby DMIC and ADC connected
> to that). If I add supply widgets, then how do I code the map? Should I do
> AIF->TXPATH ->DMIC->Supply ?

A supply widget needs to feed into other widgets.  It will be turned on
before and turned off after the widgets it supplies but won't affect
their power.

      reply	other threads:[~2011-01-19 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 12:46 [PATCH 1/4] ASoC: sn95031: add capture support Harsha Priya
2011-01-19 12:51 ` Mark Brown
2011-01-19 16:28   ` Koul, Vinod
2011-01-19 18:48     ` 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=20110119184800.GC17150@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=priya.harsha@intel.com \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).