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: Fri, 11 May 2018 11:23:41 +0900 [thread overview]
Message-ID: <20180511022341.GG949@sirena.org.uk> (raw)
In-Reply-To: <5AEFF8D8.5090003@nuvoton.com>
[-- Attachment #1.1: Type: text/plain, Size: 645 bytes --]
On Mon, May 07, 2018 at 02:57:28PM +0800, John Hsu wrote:
> Yes, you are right. In the driver, we suppose that the input of codec
> is microphone always. Therefore, we make the micbias on to provide the
> power of microphone automatically if any input path is enabled.
> What advice do you have to deal with micbias? Thank you.
Like I say you should just provide the MICBIAS pin and leave it up to
the machine drivers to connect it to whatever microphones it is being
used with. This means deleting the route from the driver and (in order
to avoid breaking them) adding the relevant route to any machine drivers
that are in mainline already.
[-- 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-11 2:23 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
2018-05-07 6:57 ` John Hsu
2018-05-11 2:23 ` Mark Brown [this message]
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=20180511022341.GG949@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 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).