alsa-devel.alsa-project.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>
Subject: Re: ASoC: wm9712: Microphone doesn't work, "Capture Volume" inverted
Date: Thu, 26 Apr 2012 18:20:10 +0100	[thread overview]
Message-ID: <20120426172010.GP3207@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1335448142.20000.40.camel@mars>


[-- Attachment #1.1: Type: text/plain, Size: 742 bytes --]

On Thu, Apr 26, 2012 at 03:49:02PM +0200, Christoph Fritz wrote:

> I added some printks into ac97_write() "sound/soc/codecs/wm9712.c" and
> when I do for example change "Item: Mic Boost [dB gain: 20.00] " I get
> this:

>  write  eh 8000  [6808]
>  write  eh 8000  [6888]

> but when I try to change "Mic Select Source" or "Item: Differential
> Source", nothing happens here.

Odd.  Can you see the write actually happening on the bus?

> Why is wm9712_enum[0] never used?

I rather imagine it's just a simple case of the feature having being
missed when the driver was implemented.

> Is "SOC_ENUM_SINGLE(0x5c, 8, 2, wm9712_diff_sel)," correct? Because of
> the ">> 1" shift in ac97_write() ?

What makes you think it might not be correct?

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

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2012-04-26 17:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 20:07 ASoC: wm9712: Microphone doesn't work, "Capture Volume" inverted Christoph Fritz
2012-04-26 10:15 ` Christoph Fritz
2012-04-26 11:27 ` Mark Brown
2012-04-26 13:49   ` Christoph Fritz
2012-04-26 17:20     ` Mark Brown [this message]
2012-04-26 21:11       ` Christoph Fritz
2012-04-26 21:37         ` Mark Brown
2012-04-27  8:00           ` Christoph Fritz
2012-04-27 13:46             ` Mark Brown
2012-05-04 13:28               ` Christoph Fritz
2012-05-07 21:55                 ` 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
     [not found]           ` <20120430192258.GA15188@local>
2012-04-30 21:43             ` ASoC: wm9712: Microphone doesn't work, "Capture Volume" inverted Mark Brown
     [not found]               ` <20120430234458.GB15188@local>
2012-05-01 17:12                 ` Mark Brown
     [not found]                   ` <20120501200755.GF15188@local>
2012-05-01 22:25                     ` 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=20120426172010.GP3207@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=chf.fritz@googlemail.com \
    --cc=hjk@hansjkoch.de \
    --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).