From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
lee.jones@linaro.org, sameo@linux.intel.com, lgirdwood@gmail.com
Subject: Re: [PATCH 2/2 v2] ASoC: arizona: Improve ultrasonic frequency response
Date: Tue, 4 Feb 2014 09:17:58 +0000 [thread overview]
Message-ID: <20140204091758.GA16684@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20140204001727.GO22609@sirena.org.uk>
On Tue, Feb 04, 2014 at 12:17:27AM +0000, Mark Brown wrote:
> On Fri, Jan 31, 2014 at 04:16:18PM +0000, Charles Keepax wrote:
> > Evaluation of the device has given some settings to improve the
> > ultrasonic frequency response. However, this may cause sub-optimal
> > performance in system designs with high output gains on the headphone
> > path (0dB or -2dB), and as the frequencies are inaudible anyway some
> > users may not desire higher frequency response at those frequencies.
> > So allow the user the option to select it if it is appopriate for
> > their system design.
>
> Reading what you're saying here I can't help but think that this sounds
> like it may be use case dependent as well and therefore something that
> ought to be runtime controllable depending on if ultrasonics and/or line
> level outputs are in use (0dB isn't high gain, it's no gain!) for
> example.
I think in practice it will likely be set once for a given
system. Although that said there is nothing that would prevent
this being switchable at runtime, I will look into respinning it
with runtime control.
Thanks,
Charles
next prev parent reply other threads:[~2014-02-04 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 16:16 [PATCH 1/2 v2] mfd: wm5102: Update register patch Charles Keepax
2014-01-31 16:16 ` [PATCH 2/2 v2] ASoC: arizona: Improve ultrasonic frequency response Charles Keepax
2014-02-04 0:17 ` Mark Brown
2014-02-04 9:17 ` Charles Keepax [this message]
2014-02-03 8:35 ` [PATCH 1/2 v2] mfd: wm5102: Update register patch Lee Jones
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=20140204091758.GA16684@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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.