From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ola Lilja <ola.o.lilja@stericsson.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@ti.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 10/11] ASoC: codecs: Add AB8500 codec-driver
Date: Thu, 24 May 2012 11:33:07 +0100 [thread overview]
Message-ID: <20120524103306.GI5361@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FBDD365.7080304@stericsson.com>
On Thu, May 24, 2012 at 08:21:25AM +0200, Ola Lilja wrote:
> Well, yes. One of the control enables/disables the ability to use another
> charge-pump voltage when the signal gets over a certain threshold. The other
> parameters are tuning of this theshold and responsiveness. This feature can be
> changed during runtime depending of quality vs. powersaving needs.
Right, this is what I had expected except usually the consequence of the
charge pump voltage failing to adapt rapidly enough is clipping which is
normally considered unacceptably bad in any situation so with most
devices there isn't much opportunity to tune the responsiveness. You do
see on/off controls that get used for configurations the device can't
handle for some reason but the responsiveness parameters that work are
normally a static property of the device.
I guess you might be able to do something slightly more aggressive for
voice perhaps... Anyway, like I say the main thing here is surprise at
seeing these things user tunable.
prev parent reply other threads:[~2012-05-24 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 13:57 [PATCH 10/11] ASoC: codecs: Add AB8500 codec-driver Ola Lilja
2012-05-08 18:27 ` Mark Brown
2012-05-09 7:48 ` Ola Lilja
2012-05-09 8:33 ` Mark Brown
2012-05-09 9:09 ` Ola Lilja
2012-05-09 10:51 ` Mark Brown
2012-05-23 7:04 ` Ola Lilja
2012-05-23 17:40 ` Mark Brown
2012-05-24 6:21 ` Ola Lilja
2012-05-24 10:33 ` 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=20120524103306.GI5361@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linus.walleij@linaro.org \
--cc=lrg@ti.com \
--cc=ola.o.lilja@stericsson.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.