From: Mark Brown <broonie@kernel.org>
To: "Opensource [Adam Thomson]" <Adam.Thomson.Opensource@diasemi.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] ASoC: da732x: Mark DC offset control registers volatile
Date: Wed, 26 Feb 2014 08:54:34 +0900 [thread overview]
Message-ID: <20140225235434.GH2927@sirena.org.uk> (raw)
In-Reply-To: <2E89032DDAA8B9408CB92943514A03376BAD41AF@SW-EX-MBX01.diasemi.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
On Tue, Feb 25, 2014 at 04:13:02PM +0000, Opensource [Adam Thomson] wrote:
> On Tue, 25 Feb 2014 01:22:04 +0000, Mark Brown wrote:
> > Refactoring the offset correction to happen once on startup would solve
> > the issue since the cache could just be bypassed, though you are likely
> > to find that there is some run to run variation for the callibration due
> > to effects like thermal variation and simple measurement errors. Still,
> > the effects are typically very small.
> I have to agree, the variation won't be great. If it were then you'd see
> problems for example when keeping a device awake for prolonged periods and
> during fluctuations in temperature. As far as I'm aware issues like this have
> not been experienced with this device so I think it's safe to make this a one
> time thing at startup.
OK, so in that case how about applying the patch I sent for now (since
it should make things better for stable users) and then refactoring to
do the callibration at startup with cache bypass enabled for a proper
fix?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-25 23:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 3:00 [PATCH] ASoC: da732x: Mark DC offset control registers volatile Mark Brown
2014-02-24 11:31 ` Opensource [Adam Thomson]
2014-02-24 12:42 ` Mark Brown
2014-02-24 13:57 ` Opensource [Adam Thomson]
2014-02-25 1:21 ` Mark Brown
2014-02-25 16:13 ` Opensource [Adam Thomson]
2014-02-25 23:54 ` Mark Brown [this message]
2014-02-26 9:39 ` Opensource [Adam Thomson]
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=20140225235434.GH2927@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=stable@vger.kernel.org \
/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