From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: alsa <alsa-devel@alsa-project.org>, Liam <lrg@slimlogic.co.uk>
Subject: Re: snd_soc_dapm_force_enable_pin question
Date: Fri, 25 Mar 2011 11:40:50 +0000 [thread overview]
Message-ID: <20110325114050.GC31415@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1301049930.1695.11.camel@vkoul-udesk3>
On Fri, Mar 25, 2011 at 04:15:30PM +0530, Koul, Vinod wrote:
> I have a Vibra controller on the codec which can be programmed using
> alsa controls. Now after configuration I added an enable control which
> when turned On, forces the Vibra Pin to be ON. The Pin is on, but not
> the path, I need the DAC and amplifier connected to be ON as well?
> Is this not what the force_enable_pin() is supposed to do?
No, it's there to force a pin to be on when there's no audio path - the
main use is for microphone biases, to ensure they're enabled in order to
allow jack detection to work. The purpose is to ignore routing so it
won't affect any other widgets.
> If not how should I ensure this path and codec BIAS is on when Vibra is
> activated by user?
Your above scenario sounds like you're just doing a regular playback of
some kind - if that is the case I'd expect things to power up when you
start playing through the DAC.
Otherwise I'd suggest creating an input widget, connecting it as an
input to the DAC and then using regular enable_pin() to enable that and
the output.
next prev parent reply other threads:[~2011-03-25 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 10:45 snd_soc_dapm_force_enable_pin question Koul, Vinod
2011-03-25 11:40 ` Mark Brown [this message]
2011-03-25 12:20 ` Koul, Vinod
2011-03-25 12:56 ` Mark Brown
2011-03-25 12:35 ` Koul, Vinod
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=20110325114050.GC31415@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--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 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.