From: Christoph Fritz <chf.fritz@googlemail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, "Hans J. Koch" <hjk@hansjkoch.de>,
Sascha Hauer <s.hauer@pengutronix.de>, Liam Girdwood <lrg@ti.com>,
linux-fbdev@vger.kernel.org
Subject: Re: ASoC: wm9712: Microphone doesn't work: Mux handling broken?
Date: Tue, 15 May 2012 09:15:41 +0000 [thread overview]
Message-ID: <20120515091541.GA4433@lovely.krouter> (raw)
In-Reply-To: <20120513035652.GA3532@lovely.krouter>
On Sun, May 13, 2012 at 05:56:53AM +0200, Christoph Fritz wrote:
> On Sat, May 12, 2012 at 12:51:31PM +0100, Mark Brown wrote:
> > On Sat, May 12, 2012 at 02:15:56AM +0200, Christoph Fritz wrote:
> >
> > > They refuse to change their Item0 because they are defined as
> > > SND_SOC_DAPM_MUX without a correlating path->name so that
> > > snd_soc_dapm_mux_update_power() (in sound/soc/soc-dapmc) doesn't
> > > change anything.
> >
> > A route into a mux without a path name (other than a supply) just isn't
> > meaningful and I'm surprised it ever worked.
> >
> > > It works in 2.6.33, but current kernel has different mux handling and
> > > it seems that no one since cared that much about microphone support.
> >
> > It's nothing to do with microphones really, it's more that AC'97 CODECs
> > are rarely used with modern kernels as the boards that use AC'97 are
> > mostly quite old and suffer performance issues with modern software
> > stacks so newer kernels haven't been getting much testing with them.
> >
> > > Mark, can you confirm this, purpose a fix or even come up with
> > > a patch?
> >
> > Just filling in the appropriate mux value in the relevant route should
> > do the trick.
Do you mean filling in to wm9712_audio_map or wm9712_enum?
> > Looking at the code it looks like the widget isn't hooked
> > into the audio routing map at all so I'm a little surprised.
Does that mean that wm9712_dapm_widgets should be referred by a
struct snd_kcontrol_new ?
> >I'm out of
> > the office at the minute and so can't readily set up a test system
> > myself.
I'm not that into alsa and would greatly appreciate if you could have
a look with your test system.
Thanks,
-- Christoph
next prev parent reply other threads:[~2012-05-15 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1335384469.14096.203.camel@mars>
[not found] ` <20120426112726.GF3207@opensource.wolfsonmicro.com>
[not found] ` <1335448142.20000.40.camel@mars>
[not found] ` <20120426172010.GP3207@opensource.wolfsonmicro.com>
[not found] ` <1335474693.3628.26.camel@lovely>
[not found] ` <20120426213745.GA18260@opensource.wolfsonmicro.com>
[not found] ` <1335513602.3504.4.camel@mars>
[not found] ` <20120427134638.GI18260@opensource.wolfsonmicro.com>
[not found] ` <20120504132845.GA24245@lovely.krouter>
2012-05-07 21:55 ` ASoC: wm9712: Microphone doesn't work, "Capture Volume" inverted Christoph Fritz
2012-05-08 10:29 ` Christoph Fritz
2012-05-12 0:15 ` ASoC: wm9712: Microphone doesn't work: Mux handling broken? Christoph Fritz
2012-05-12 11:51 ` Mark Brown
2012-05-13 3:56 ` Christoph Fritz
2012-05-15 9:15 ` Christoph Fritz [this message]
2012-05-15 17:15 ` Mark Brown
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=20120515091541.GA4433@lovely.krouter \
--to=chf.fritz@googlemail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=hjk@hansjkoch.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=lrg@ti.com \
--cc=s.hauer@pengutronix.de \
/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).