All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Scheel <julian@jusst.de>
To: Stephen Warren <swarren@nvidia.com>
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com,
	lrg@slimlogic.co.uk
Subject: Re: [PATCH] ASoC: WM8903: Implement DMIC support
Date: Fri, 14 Oct 2011 12:34:21 +0200	[thread overview]
Message-ID: <1318588461.2686.9.camel@localhost.localdomain> (raw)
In-Reply-To: <1303181891-25064-1-git-send-email-swarren@nvidia.com>

Am Montag, den 18.04.2011, 20:58 -0600 schrieb Stephen Warren:
> In addition to the currently supported analog capture path, the WM8903
> also supports digital mics.
> 
> The analog and digital capture paths are exclusive; a mux is present to
> select the capture source.
> 
> Logically, the mux exists to select the decimator's input, from either
> the ADC or DMIC block outputs. However, the ADC power domain also
> includes the DMIC interface. Consequently, this change represents the
> mux as existing immediately before the ADC, and selecting between the
> Input PGA and DMIC block outputs.
> 
> An alternative might be to represent the mux in its correct location,
> and associate the ADC power enable controls with both the real ADC, and
> a fake ADC for the DMIC?

Hi,

actually the wm8903 codec needs GPIO1 and GPIO2 to be configured
properly to be able to use DMIC actually. I would propose to
automatically configure these to DMIC-mode whenever ADCINPUT is set to
DMIC. Would you agree with this procedure?
I would prepare a patch which changes all relevant registers then.

Regards,
Julian

  parent reply	other threads:[~2011-10-14 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19  2:58 [PATCH] ASoC: WM8903: Implement DMIC support Stephen Warren
2011-04-20 11:10 ` Liam Girdwood
2011-04-20 13:00 ` Mark Brown
2011-10-14 10:34 ` Julian Scheel [this message]
2011-10-14 12:16   ` 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=1318588461.2686.9.camel@localhost.localdomain \
    --to=julian@jusst.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=swarren@nvidia.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.