From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: mic bias for tlv320aic3x?
Date: Wed, 28 Nov 2012 09:35:34 +0000 [thread overview]
Message-ID: <20121128093534.GK32691@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1211280927500.26303@pmeerw.net>
[-- Attachment #1.1: Type: text/plain, Size: 1308 bytes --]
On Wed, Nov 28, 2012 at 10:28:53AM +0100, Peter Meerwald wrote:
> I am missing the overall strategy how this is supposed to work
> is there a good reference driver?
Currently nobody is implementing this dynamically, it's always
configured via platform data.
> per default, Mic Bias is off
Well, of course... it's just a normal thing in DAPM.
> there already are some mic bias definitions in tlv320aic3x:
> /* Mic Bias */
> SND_SOC_DAPM_REG(snd_soc_dapm_micbias, "Mic Bias 2V",
> MICBIAS_CTRL, 6, 3, 1, 0),
> SND_SOC_DAPM_REG(snd_soc_dapm_micbias, "Mic Bias 2.5V",
> MICBIAS_CTRL, 6, 3, 2, 0),
> SND_SOC_DAPM_REG(snd_soc_dapm_micbias, "Mic Bias AVDD",
> MICBIAS_CTRL, 6, 3, 3, 0),
> however, those are not referenced anywhere and it is not clear how to
> access those from the machine driver
I'm not clear what the above is intended to do but I think you're
supposed to pick the MICBIAS you want to use in your board when you're
hooking it up.
> as for the use case: user wants to connect either a microphone or line-in
> to a connector, hence mic bias selection is necessary -- this doesn't
> sound so unusual
Normally this sort of thing would be done automatically by the kernel
detecting what's plugged in, not manually by an application.
[-- 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:[~2012-11-28 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 17:15 mic bias for tlv320aic3x? Peter Meerwald
2012-11-27 17:53 ` Mark Brown
2012-11-28 9:28 ` Peter Meerwald
2012-11-28 9:35 ` 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=20121128093534.GK32691@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=pmeerw@pmeerw.net \
/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.