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: Tue, 25 Feb 2014 10:21:38 +0900 [thread overview]
Message-ID: <20140225012138.GK25940@sirena.org.uk> (raw)
In-Reply-To: <2E89032DDAA8B9408CB92943514A03376BAD405D@SW-EX-MBX01.diasemi.com>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
On Mon, Feb 24, 2014 at 01:57:53PM +0000, Opensource [Adam Thomson] wrote:
> anyway. I'd be tempted to keep it simple and just make those registers volatile,
> then you know it will work as expected, at least for the time being until a
That breaks suspend and resume without further work - for suspend and
resume we generally rely on restoring the register cache to restore the
current settings but if a register is volatile it won't be cached so
will go back to the hardware defaults after suspend. The ability to
avoid I2C traffic is partly just a nice side effect (though it was
needed on devices that don't have readback), the main thing these days
is that controls get efficient suspend and resume handling for free.
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.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-25 1:21 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 [this message]
2014-02-25 16:13 ` Opensource [Adam Thomson]
2014-02-25 23:54 ` Mark Brown
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=20140225012138.GK25940@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