From: Valdis.Kletnieks@vt.edu
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: dp@opensource.wolfsonmicro.com, linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 2/2] regmap: Allow caches for devices with no defaults
Date: Sun, 09 Oct 2011 13:43:42 -0400 [thread overview]
Message-ID: <109263.1318182222@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 09 Oct 2011 14:44:36 BST." <1318167876-17801-2-git-send-email-broonie@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
On Sun, 09 Oct 2011 14:44:36 BST, Mark Brown said:
> We only really need the defaults in order to cut down the number of
> registers we sync and to satisfy reads while the device is powered off
So let me get this straight - we cache the values so that if there's a read,
we can return our best guess as to what the device would return if it was
in fact powered on, instead of notifying the caller that the device is off?
I think I just sprained my brain trying to parse the logic there :)
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-10-09 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 13:44 [PATCH 1/2] regmap: Return a sensible error code if we fail to read the cache Mark Brown
2011-10-09 13:44 ` [PATCH 2/2] regmap: Allow caches for devices with no defaults Mark Brown
2011-10-09 17:43 ` Valdis.Kletnieks [this message]
2011-10-09 19:34 ` Mark Brown
2011-10-10 8:41 ` Dimitris Papastamos
2011-10-10 9:23 ` Mark Brown
2011-10-10 10:50 ` Dimitris Papastamos
2011-10-10 9:03 ` [PATCH 1/2] regmap: Return a sensible error code if we fail to read the cache Dimitris Papastamos
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=109263.1318182222@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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
all inboxes | Powered by JetHome®