From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: gregkh@linuxfoundation.org, sameo@linux.intel.com,
lee.jones@linaro.org, linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 2/3] regmap: Add API call apply but not register a patch file
Date: Mon, 24 Feb 2014 10:24:21 +0900 [thread overview]
Message-ID: <20140224012421.GO25940@sirena.org.uk> (raw)
In-Reply-To: <20140223161159.GA5901@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
On Sun, Feb 23, 2014 at 04:11:59PM +0000, Charles Keepax wrote:
> On Sat, Feb 22, 2014 at 11:10:48AM +0900, Mark Brown wrote:
> > This is just regmap_multi_reg_write() I think? That already exists, the
> > theory was that we're going to get an optimised version of that for some
> > hardware which can stream things and cut out some overheads though that
> > doesn't seem to have materialised yet.
> I had missed regmap_multi_reg_write but the difference here is that we
> apply cache bypass, and that the cache bypass is only applied whilst the
> regmap lock is held. This allows users to be sure that no writes
> from other threads will accidentally have the bypass applied to them.
Right, OK - but it should still be a wrapper for a core implementation
and share interface/naming.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-24 5:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 19:37 [PATCH 1/3] regmap: Check stride of register patch as we register it Charles Keepax
2014-02-21 19:37 ` [PATCH 2/3] regmap: Add API call apply but not register a patch file Charles Keepax
2014-02-22 2:10 ` Mark Brown
2014-02-23 16:11 ` Charles Keepax
2014-02-24 1:24 ` Mark Brown [this message]
2014-02-21 19:37 ` [PATCH 3/3] mfd: arizona: Use new regmap features for manual register patch Charles Keepax
2014-02-24 16:10 ` Lee Jones
2014-02-25 9:37 ` Charles Keepax
2014-02-25 10:02 ` Lee Jones
2014-02-22 2:15 ` [PATCH 1/3] regmap: Check stride of register patch as we register it Mark Brown
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=20140224012421.GO25940@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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 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®