From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jerry Wong <Jerry.Wong@maximintegrated.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"jwong@jwassociates.com" <jwong@jwassociates.com>
Subject: Re: [PATCH 002/002] ASoC: Replace max98090 Device Driver
Date: Sat, 26 Jan 2013 15:12:54 +0800 [thread overview]
Message-ID: <20130126071252.GG10580@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <A453F1AE3B5DC14DB19666C506CE75A7108684F4CC@ITSVLEX06.it.maxim-ic.internal>
[-- Attachment #1.1: Type: text/plain, Size: 1531 bytes --]
On Fri, Jan 25, 2013 at 07:39:45AM -0800, Jerry Wong wrote:
> On Thu, Jan 24, 2013 at 03:28:54PM -0800, Jerry Wong wrote:
> > This is an odd control that is a combination of an enum and a power
> > management widget. The 0 value of the enum turns power off.
> > Not sure what is another choice. The enum value needs to be
> > saved so it can be restored when DAPM turns the control on.
> > That doesn't appear to be what your control actually does - what happens
> > if someone writes ot the control while the widget is powered down?
> It stores the desired value for DAPM to use when the widget is powered up.
It looks like it's a SOC_ENUM_SINGLE so it should map directly on to the
register map?
> > > +static const struct snd_kcontrol_new max98090_snd_controls[] = {
> > > + SOC_SINGLE("MIC Bias VCM Bandgap", M98090_REG_BIAS_CNTL,
> > > + M98090_VCM_MODE_SHIFT, M98090_VCM_MODE_NUM - 1, 0),
> > > Why is this a user visible control?
> > It is not controlled by DAPM. The low power function is taken care of by
> > /SHDN\, so this retains the user choice of bandgap or divider reference.
> > Why would the user want this choice?
> This allows the user to select VCM Bandgap for all their references (higher power
> and higher audio quality when in use), or divider reference (lower power and lower
> audio quality when in use). /SHDN\ prevents power drain when either is not in use.
So in that case I'd recommend doing something like making it an
enmerated control which makes the tradeoff clear.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-01-26 7:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 15:13 [PATCH 002/002] ASoC: Replace max98090 Device Driver Jerry Wong
2013-01-17 2:53 ` Mark Brown
2013-01-23 17:33 ` Jerry Wong
[not found] ` <A453F1AE3B5DC14DB19666C506CE75A7108684F4C7@ITSVLEX06.it.maxim-ic.internal>
2013-01-25 7:21 ` Mark Brown
2013-01-25 15:39 ` Jerry Wong
2013-01-25 17:02 ` Jerry Wong
2013-01-26 7:15 ` Mark Brown
2013-01-26 7:12 ` Mark Brown [this message]
[not found] ` <A453F1AE3B5DC14DB19666C506CE75A7108684F4ED@ITSVLEX06.it.maxim-ic.internal>
2013-02-01 5:13 ` Jerry Wong
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=20130126071252.GG10580@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Jerry.Wong@maximintegrated.com \
--cc=alsa-devel@alsa-project.org \
--cc=jwong@jwassociates.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).