From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: patches@opensource.wolfsonmicro.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 8/8] mfd: Enable register cache for wm8994 devices
Date: Mon, 28 Nov 2011 22:58:29 +0000 [thread overview]
Message-ID: <20111128225829.GC16133@sirena.org.uk> (raw)
In-Reply-To: <1322520274-13789-8-git-send-email-broonie@opensource.wolfsonmicro.com>
On Mon, Nov 28, 2011 at 10:44:34PM +0000, Mark Brown wrote:
> As part of this we provide information about the registers that exist in
> the device to the regmap core, drop the small amount of cache that the
> core had been using and let regmap do the sync.
Oh, and I forgot that this one depends on a regmap patch (regmap: Track
if the register cache is dirty and suppress unneeded syncs). I've
rebuilt the branch with the appropriate merge in it.
next prev parent reply other threads:[~2011-11-28 22:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 22:40 [PATCH 0/8] WM8994 MFD updates for 3.3 Mark Brown
2011-11-28 22:44 ` [PATCH 1/8] mfd: Remove some unused functions in wm8894-irq Mark Brown
2011-11-28 22:44 ` [PATCH 2/8] mfd: Add basic device tree binding for wm8994 Mark Brown
2011-11-28 22:44 ` [PATCH 3/8] mfd: Convert wm8994 to devm_kzalloc() Mark Brown
2011-11-28 22:44 ` [PATCH 4/8] mfd: Disable more pulls on WM8994 Mark Brown
2011-11-28 22:44 ` [PATCH 5/8] mfd: Don't hard code the reset value for WM8994 devices Mark Brown
2011-11-28 22:44 ` [PATCH 6/8] mfd: Define some additional wm8994 registers Mark Brown
2011-11-28 22:44 ` [PATCH 7/8] mfd: Add wm8994 register access and default information Mark Brown
2011-11-28 22:44 ` [PATCH 8/8] mfd: Enable register cache for wm8994 devices Mark Brown
2011-11-28 22:58 ` Mark Brown [this message]
2011-11-28 22:47 ` [PATCH] mfd: Convert wm8994 to use generic regmap irq_chip Mark Brown
2011-12-12 14:34 ` [PATCH 0/8] WM8994 MFD updates for 3.3 Samuel Ortiz
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=20111128225829.GC16133@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--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
Powered by JetHome