From: Mark Brown <broonie@kernel.org>
To: "Andrew F. Davis" <afd@ti.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: tlv320aic31xx: Remove regulator notification handling
Date: Tue, 4 Sep 2018 16:49:05 +0100 [thread overview]
Message-ID: <20180904154905.GH12993@sirena.org.uk> (raw)
In-Reply-To: <f6c7df62-a98f-009a-2169-0e5564f4b675@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 923 bytes --]
On Tue, Sep 04, 2018 at 10:03:40AM -0500, Andrew F. Davis wrote:
> On 09/04/2018 09:57 AM, Mark Brown wrote:
> > It's there to save us having to rewrite the register cache if we asked
> > for the device to be powered down but that didn't actually happen due to
> > other constraints, we know all the registers are still as we left them.
> I don't see that happening for any other user of this, we will still
> have to re-write the cache when the device goes from OFF->STANDBY, and
You will? All the power_off() code seems to do is mark the regmap as
cache only and turn off the regulators.
> if it stays in standby and never went off, then we are still broken as
> we switched to using the register cache only, but never turned on real
> writes again.
regmap can remember which registers were written to while in cache only
mode and only sync the ones that are actually dirty, or you can
invalidate the entire cache.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-09-04 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 18:17 [PATCH] ASoC: tlv320aic31xx: Remove regulator notification handling Andrew F. Davis
2018-09-03 11:30 ` Mark Brown
2018-09-04 14:50 ` Andrew F. Davis
2018-09-04 14:57 ` Mark Brown
2018-09-04 15:03 ` Andrew F. Davis
2018-09-04 15:49 ` Mark Brown [this message]
2018-09-04 15:55 ` Andrew F. Davis
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=20180904154905.GH12993@sirena.org.uk \
--to=broonie@kernel.org \
--cc=afd@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@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