From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Javier Martin <javier.martin@vista-silicon.com>
Cc: alsa-devel@alsa-project.org, lrg@ti.com
Subject: Re: [PATCH] ASoC: Fix mic bias handling in TI tlv320aic32x codec.
Date: Thu, 5 Jan 2012 15:56:07 +0000 [thread overview]
Message-ID: <20120105155605.GA17659@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1325775904-22177-1-git-send-email-javier.martin@vista-silicon.com>
On Thu, Jan 05, 2012 at 04:05:04PM +0100, Javier Martin wrote:
> For this reason it's not possible to add this as
> a DAPM event since we lack the possibility to associate
> it to a DAPM route. So we use platform data totell the
> device whether we are connecting a microphone or not.
No, this change would be a regression - if this were a problem we'd not
have microphones working at all in ASoC. The routing of the microphone
bias is done by the machine driver, not the CODEC driver.
prev parent reply other threads:[~2012-01-05 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 15:05 [PATCH] ASoC: Fix mic bias handling in TI tlv320aic32x codec Javier Martin
2012-01-05 15:56 ` 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=20120105155605.GA17659@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=javier.martin@vista-silicon.com \
--cc=lrg@ti.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).