From: Mark Brown <broonie@kernel.org>
To: John Hsu <KCHSU0@nuvoton.com>
Cc: alsa-devel@alsa-project.org, CFYU0@nuvoton.com, WTLI@nuvoton.com,
lgirdwood@gmail.com, YHCHuang@nuvoton.com, CTLIN0@nuvoton.com,
YCPENG7@nuvoton.com
Subject: Re: [PATCH 2/2] ASoC: nau8810: change the target of MIC BIAS supply
Date: Sat, 5 May 2018 10:01:10 +0900 [thread overview]
Message-ID: <20180505010110.GI13402@sirena.org.uk> (raw)
In-Reply-To: <5AEBB308.6020006@nuvoton.com>
[-- Attachment #1.1: Type: text/plain, Size: 1420 bytes --]
On Fri, May 04, 2018 at 09:10:32AM +0800, John Hsu wrote:
> On 5/4/2018 7:10 AM, Mark Brown wrote:
> > On Thu, May 03, 2018 at 10:46:42AM +0800, John Hsu wrote:
> > > The MICBAIS will not supply if there is only one path from MICP to
> > > input boost stage. The driver fixes the issue by changing the supply
> > > target to input boost stage mixer.
> > Does the input boost stage actually use the MICBIAS supply directly?
> > More usually a microphone bias would supply the microphone rather than
> > anything on the chip itself.
> The input boost stage has a mixer of two input sources. The normal case
> is that MIC goes to input PGA, then to input boot stage. The case is
> the original design of the driver. But there is another path that MIC
> goes input boot stage directly. The case is less happened but has chance.
> Ex. The single-end MIC goes to input boot stage. Therefore, we move
> the target of MICBIAS to input boost stage which can supply power for
> both cases.
That's not really answering the question - the issue is that the micbias
is normally connected to the microphone and supplies that, it's not
normally connected to anything in the CODEC itself. You're talking
about the path for the signal from the microphone which isn't the same
thing as the power to the microphone. The system could have external
micbiases or use the input for something that isn't actually a
microphone for example.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-05-05 1:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 2:46 [PATCH 1/2] ASoC: nau8810: change input PGA mixer stage John Hsu
2018-05-03 2:46 ` [PATCH 2/2] ASoC: nau8810: change the target of MIC BIAS supply John Hsu
2018-05-03 23:10 ` Mark Brown
2018-05-04 1:10 ` John Hsu
2018-05-05 1:01 ` Mark Brown [this message]
2018-05-07 6:57 ` John Hsu
2018-05-11 2:23 ` Mark Brown
2018-05-03 23:18 ` Applied "ASoC: nau8810: change input PGA mixer stage" to the asoc tree 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=20180505010110.GI13402@sirena.org.uk \
--to=broonie@kernel.org \
--cc=CFYU0@nuvoton.com \
--cc=CTLIN0@nuvoton.com \
--cc=KCHSU0@nuvoton.com \
--cc=WTLI@nuvoton.com \
--cc=YCPENG7@nuvoton.com \
--cc=YHCHuang@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.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.