All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ola Lilja <ola.o.lilja@stericsson.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Liam Girdwood <lrg@ti.com>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 7/8] ASoC: codecs: Add AB8500 codec-driver
Date: Mon, 30 Apr 2012 10:56:01 +0100	[thread overview]
Message-ID: <20120430095601.GD3170@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F9E526F.6090705@stericsson.com>


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

On Mon, Apr 30, 2012 at 10:50:55AM +0200, Ola Lilja wrote:
> On 04/27/2012 01:11 PM, Mark Brown wrote:
> > On Fri, Apr 27, 2012 at 12:54:59PM +0200, Ola Lilja wrote:

> > OK, then why aren't they hooked up in the board anyway (probably fixed to
> > a specific configuration there, though there are some use cases for
> > changing)?  This is what other CODEC drivers do with their MICBIASes...

> OK, I will have to investigate this possibility then... I'm not certain that we
> have this information available from the board in any easy way.

Usually it's very clear in the schematic?

[-- 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-30  9:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1334914402-27554-1-git-send-email-ola.o.lilja@stericsson.com>
2012-04-23 18:59 ` [PATCH 7/8] ASoC: codecs: Add AB8500 codec-driver Mark Brown
2012-04-27  9:19   ` Ola Lilja
2012-04-27  9:35     ` Mark Brown
2012-04-27 10:54       ` Ola Lilja
2012-04-27 11:11         ` Mark Brown
2012-04-30  8:50           ` Ola Lilja
2012-04-30  9: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=20120430095601.GD3170@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linus.walleij@linaro.org \
    --cc=lrg@ti.com \
    --cc=ola.o.lilja@stericsson.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.