linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Christoph Fritz <chf.fritz@googlemail.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 17:15:59 +0000	[thread overview]
Message-ID: <20120515171553.GA4140@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120515091541.GA4433@lovely.krouter>

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

On Tue, May 15, 2012 at 11:15:41AM +0200, Christoph Fritz wrote:
> On Sun, May 13, 2012 at 05:56:53AM +0200, Christoph Fritz wrote:

> > > 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?

There will need to be routes in the audio map.  Don't know if there are
any fixes needed in the enum, it was the routing I noticed was missing.

> > > 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 ?

No, that should never happen.

> > >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.

For personal reasons I don't really have an ETA for when I'll be in the
office, sorry.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-05-15 17: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
2012-05-15 17:15                             ` 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=20120515171553.GA4140@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=chf.fritz@googlemail.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).