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] ASoC: arizona: Improve ultrasonic frequency response
Date: Fri, 31 Jan 2014 16:14:46 +0000 [thread overview]
Message-ID: <20140131161446.GB12183@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20140131160644.GJ22609@sirena.org.uk>
On Fri, Jan 31, 2014 at 04:06:44PM +0000, Mark Brown wrote:
> On Fri, Jan 31, 2014 at 03:47:14PM +0000, Charles Keepax wrote:
> > Evaluation of the device has given some settings to improve the
> > ultrasonic frequency response. This patch allows the user the option of
> > applying those.
>
> Why would the user ever not want to do this?
>
> > + switch (priv->arizona->type) {
> > + case WM5102:
> > + if (priv->arizona->pdata.ultrasonic_response) {
> > + snd_soc_write(codec, 0x80, 0x3);
> > + if (params_rate(params) >= 176400)
> > + snd_soc_write(codec, 0x4dd, 0x1);
> > + else
> > + snd_soc_write(codec, 0x4dd, 0x0);
> > + snd_soc_write(codec, 0x80, 0x0);
> > + }
> > + break;
>
> The code is only changing the configuration when the user is actually
> using ultrasonic sample rates so it doesn't seem like it should have a
> detrimental effect on other configurations.
Apologies I should have included a bit more in the commit message
I think, I will fire out a quick respin.
Thanks,
Charles
next prev parent reply other threads:[~2014-01-31 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 15:47 [PATCH 1/2] mfd: wm5102: Update register patch Charles Keepax
2014-01-31 15:47 ` [PATCH 2/2] ASoC: arizona: Improve ultrasonic frequency response Charles Keepax
2014-01-31 16:06 ` Mark Brown
2014-01-31 16:14 ` Charles Keepax [this message]
2014-02-03 8:37 ` Lee Jones
2014-02-03 16:10 ` Mark Brown
2014-02-03 16:48 ` Lee Jones
2014-02-03 18:43 ` 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=20140131161446.GB12183@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox