From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Matt Flax <flatmax@flatmax.org>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
brian.austin@cirrus.com, paul.handrigan@cirrus.com
Subject: Re: [PATCH] ASoC: cs4265: Add a MIC pre. switch
Date: Fri, 7 Sep 2018 09:26:26 +0100 [thread overview]
Message-ID: <20180907082626.GF1653@imbe.wolfsonmicro.main> (raw)
In-Reply-To: <20180907032729.26532-1-flatmax@flatmax.org>
On Fri, Sep 07, 2018 at 01:27:29PM +1000, Matt Flax wrote:
> This patch adds a MIC preamp enable switch as a SOC_SINGLE.
>
> Signed-off-by: Matt Flax <flatmax@flatmax.org>
> ---
> sound/soc/codecs/cs4265.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/sound/soc/codecs/cs4265.c b/sound/soc/codecs/cs4265.c
> index d9eebf6a..03476f93 100644
> --- a/sound/soc/codecs/cs4265.c
> +++ b/sound/soc/codecs/cs4265.c
> @@ -161,6 +161,7 @@ static const struct snd_kcontrol_new cs4265_snd_controls[] = {
> SOC_SINGLE("MMTLR Data Switch", CS4265_SPDIF_CTL2, 0, 1, 0),
> SOC_ENUM("Mono Channel Select", spdif_mono_select_enum),
> SND_SOC_BYTES("C Data Buffer", CS4265_C_DATA_BUFF, 24),
> + SOC_SINGLE("MIC Preamp", CS4265_PWRCTL, 3, 1, 1),
> };
Is this the correct way to control this bit? There is already
a SND_SOC_DAPM_PGA widget called "Pre-amp MIC" that controls
the bit, it looks like this widget is not connected to the
rest of the DAPM graph. Should we just be hooking that widget
up instead? The datasheet isn't abundantly clear but it looks
like the bit needs to be set whenever the mic is in use:
"The microphone preamplifier block will enter a low-power state
whenever this bit is set."
Which would really make DAPM a better fit, unless there are valid
use-cases for using the mic with the preamp powered down?
Thanks,
Charles
next prev parent reply other threads:[~2018-09-07 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 3:27 [PATCH] ASoC: cs4265: Add a MIC pre. switch Matt Flax
2018-09-07 8:26 ` Charles Keepax [this message]
2018-09-07 10:18 ` Matt Flax
2018-09-07 10:55 ` Charles Keepax
2018-09-07 11:06 ` Matt Flax
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=20180907082626.GF1653@imbe.wolfsonmicro.main \
--to=ckeepax@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.com \
--cc=broonie@kernel.org \
--cc=flatmax@flatmax.org \
--cc=paul.handrigan@cirrus.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.