From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Linus Walleij <linus.walleij@stericsson.com>,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] gpiolib: Add support for Wolfson Microelectronics Arizona class devices
Date: Mon, 25 Jun 2012 23:30:59 +0100 [thread overview]
Message-ID: <20120625223058.GD30406@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACRpkdbKyHtwcsGoph_s-YPtn9yUxxKQBfXc_ksiNu=yE51spA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
On Tue, Jun 26, 2012 at 03:13:58AM +0800, Linus Walleij wrote:
> On Sat, Jun 23, 2012 at 8:29 PM, Mark Brown
> > + regmap_update_bits(arizona->regmap, ARIZONA_GPIO1_CTRL + offset,
> > + ARIZONA_GPN_LVL, value);
> I'm guessing that regmap is caching, selectively updating volatile
> regs and marshalling the writes in the background.
It's just the standard read/modify/write operation (the same as you've
got for ab8500 IIRC). As far as the immediate user is concerned it's
just doing the I/O, the API will work with cache or the hardware
depending on how the chip register map is configured.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-25 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 12:29 [PATCH] gpiolib: Add support for Wolfson Microelectronics Arizona class devices Mark Brown
2012-06-25 19:13 ` Linus Walleij
2012-06-25 22:30 ` Mark Brown [this message]
2012-06-25 22:32 ` Mark Brown
2012-07-05 13:23 ` Linus Walleij
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=20120625223058.GD30406@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.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 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.