From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
Graeme Gregory <gg@slimlogic.co.uk>,
Samuel Oritz <sameo@linux.intel.com>
Subject: Re: [PATCH 6/6 v3] regmap: Incorporate the regcache core into regmap
Date: Fri, 16 Sep 2011 00:53:24 +0100 [thread overview]
Message-ID: <20110915235324.GI3218@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E728840.407@metafoo.de>
On Fri, Sep 16, 2011 at 01:20:32AM +0200, Lars-Peter Clausen wrote:
> But for writes the error is propagated to the caller, instead of falling back
> to a hw write. There should be at least consistency between the two.
Hrm, yes we should do that (I haven't actually had time to read this
round yet).
> And I think we should document that regmap_readable and regmap_writeable don't
> prevent actuall hw access, but are merely meant as hints for stuff like caching.
Well, right now we don't enforce anything at all. I wouldn't object to
a patch for this but once we go out of spec I think we're fine so long
as we're senseible.
prev parent reply other threads:[~2011-09-15 23:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 10:34 [PATCH 0/6 v3] Introduce caching support for regmap Dimitris Papastamos
2011-09-15 10:34 ` [PATCH 1/6 v3] regmap: Introduce caching support Dimitris Papastamos
2011-09-15 15:11 ` Lars-Peter Clausen
2011-09-15 15:32 ` Dimitris Papastamos
2011-09-15 10:34 ` [PATCH 2/6 v3] regmap: Add the indexed cache support Dimitris Papastamos
2011-09-15 10:34 ` [PATCH 3/6 v3] regmap: Add the rbtree " Dimitris Papastamos
2011-09-15 10:34 ` [PATCH 4/6 v3] regmap: Add the LZO " Dimitris Papastamos
2011-09-15 10:34 ` [PATCH 5/6 v3] regmap: Add the regcache_sync trace event Dimitris Papastamos
2011-09-15 10:34 ` [PATCH 6/6 v3] regmap: Incorporate the regcache core into regmap Dimitris Papastamos
2011-09-15 15:19 ` Lars-Peter Clausen
2011-09-15 15:37 ` Dimitris Papastamos
2011-09-15 22:57 ` Mark Brown
2011-09-15 23:20 ` Lars-Peter Clausen
2011-09-15 23:53 ` Mark Brown [this message]
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=20110915235324.GI3218@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.