From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Andrey Danin <danindrey@mail.ru>
Cc: alsa-devel@alsa-project.org, Leon Romanovsky <leon@leon.nu>,
Marc Dietrich <marvin24@gmx.de>
Subject: Re: [PATCH 1/2] ASoC: tegra+alc5632: Swap MICBIAS1 and MIC1 dapm widgets
Date: Tue, 10 Jul 2012 14:51:52 +0100 [thread overview]
Message-ID: <20120710135152.GF9409@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1341901029.151674687@f219.mail.ru>
[-- Attachment #1.1: Type: text/plain, Size: 953 bytes --]
On Tue, Jul 10, 2012 at 10:17:09AM +0400, Andrey Danin wrote:
> Mon, 9 Jul 2012 17:44:41 +0100 от Mark Brown <broonie@opensource.wolfsonmicro.com>:
> > On Sat, Jul 07, 2012 at 03:36:29PM +0200, Marc Dietrich wrote:
Please fix your mailer to word wrap within paragraph.
> > > MICBIAS1 is an internal widget. If MICBIAS1 is connected to the board
> > > driver instead of the MIC1 ASoC core, it enables widgets even if the
> > > capture stream isn't active.
> > What exactly is MICBIAS1 then? It sounds horribly named...
> According to alc5632 documentation alc5632 has one physical pin named
> MICBIAS (MIC BIAS Voltage Output). MICBIAS1 is declared as
> SND_SOC_DAPM_SUPPLY. It describes "MICBIAS1 Power" bit in power
> management register. Should "MICBIAS1/2" be renamed to "MICBIAS1/2
> Power" ?
Sounds like it might be plausible, and whatever controls the external
MICBIAS pin probably ought to be renamed to MICBIAS.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-07-10 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-07 13:36 [PATCH 1/2] ASoC: tegra+alc5632: Swap MICBIAS1 and MIC1 dapm widgets Marc Dietrich
2012-07-07 13:36 ` [PATCH 2/2] ARM: dt: documentation: tegra+alc5632: don't use MICBIAS1 in external dapm linkage Marc Dietrich
2012-07-09 16:44 ` [PATCH 1/2] ASoC: tegra+alc5632: Swap MICBIAS1 and MIC1 dapm widgets Mark Brown
2012-07-10 6:17 ` Andrey Danin
2012-07-10 13:51 ` 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=20120710135152.GF9409@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=danindrey@mail.ru \
--cc=leon@leon.nu \
--cc=marvin24@gmx.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