alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Hans J. Koch" <hjk@hansjkoch.de>
Cc: Christoph Fritz <chf.fritz@googlemail.com>,
	alsa-devel@alsa-project.org,
	Sascha Hauer <s.hauer@pengutronix.de>, Liam Girdwood <lrg@ti.com>
Subject: Re: ASoC: wm9712: Microphone doesn't work, "Capture Volume" inverted
Date: Mon, 30 Apr 2012 22:43:33 +0100	[thread overview]
Message-ID: <20120430214332.GA4414@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120430192258.GA15188@local>


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

On Mon, Apr 30, 2012 at 09:40:55PM +0200, Hans J. Koch wrote:
> On Thu, Apr 26, 2012 at 10:37:45PM +0100, Mark Brown wrote:
> > On Thu, Apr 26, 2012 at 11:11:33PM +0200, Christoph Fritz wrote:

> > > ac97_write() doesn't get called when I try to change "Item: Differential Source".

> > Oh, right - you're not actually seeing any attempt to write.  There
> > won't be anything on the bus, then.  Still, why are you identifying the
> > shift there?  The write will be suppresed if the register contents don't
> > change which looks like what you're seeing here - though I can't see
> [...]

> I overlooked that one. What kind of horror show is that? It's definetly wrong
> to make any assumptions about hardware register contents. A low-level write
> function always has to write the given value to the given register. Everything
> else, like suppressing a write because you _think_ a register hasn't changed,
> will sooner or later lead to hard-to-find errors.

> Any performance optimizations have to take place on the highest possible level.

I'm not entirely sure you've looked at the code here...

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

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



  parent reply	other threads:[~2012-04-30 21:43 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
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             ` Mark Brown [this message]
     [not found]               ` <20120430234458.GB15188@local>
2012-05-01 17:12                 ` ASoC: wm9712: Microphone doesn't work, "Capture Volume" inverted 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=20120430214332.GA4414@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).