From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] regmap updates for v3.10
Date: Mon, 29 Apr 2013 21:03:37 +0100 [thread overview]
Message-ID: <20130429200337.GD3270@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 3438 bytes --]
The following changes since commit 41ef2d5678d83af030125550329b6ae8b74618fa:
Linux 3.9-rc7 (2013-04-14 17:45:16 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v3.10
for you to fetch changes up to 38a817965d2d624b0db68f3bf5ae783ad7f2087a:
Merge remote-tracking branch 'regmap/topic/range' into regmap-next (2013-04-16 16:05:50 +0100)
----------------------------------------------------------------
regmap: Updates for v3.10
In user visible terms just a couple of enhancements here, though there
was a moderate amount of refactoring required in order to support the
register cache sync performance improvements.
- Support for block and asynchronous I/O during register cache syncing;
this provides a use case dependant performance improvement.
- Additional debugfs information on the memory consuption and register
set.
----------------------------------------------------------------
Dimitris Papastamos (4):
regmap: debugfs: Simplify calculation of `c->max_reg'
regmap: debugfs: Add a registers `range' file
regmap: rbtree Expose total memory consumption in the rbtree debugfs entry
regmap: Cut down on the average # of nodes in the rbtree cache
Mark Brown (21):
regmap: async: Add tracepoints for async I/O
regmap: rbtree: Don't bother checking for noop updates
regmap: cache: Pass the map rather than the word size when updating values
regmap: cache: Use regcache_get_value() to check if we updated
regmap: core: Split out in place value parsing
regmap: cache: Store caches in native register format where possible
regmap: irq: Clarify error message when we fail to request primary IRQ
regmap: core: Warn on invalid operation combinations
regmap: core: Make raw write available to regcache
regmap: cache: Provide a get address of value operation
regmap: core: Provide regmap_can_raw_write() operation
regmap: cache: Use raw I/O to sync rbtrees if we can
regmap: cache: Factor out reg_present support from rbtree cache
regmap: cache: Factor out block sync
regmap: cache: Split raw and non-raw syncs
regmap: cache: Write consecutive registers in a single block write
Merge tag 'v3.9-rc7' into regmap-cache
Merge remote-tracking branch 'regmap/topic/async' into regmap-next
Merge remote-tracking branch 'regmap/topic/cache' into regmap-next
Merge remote-tracking branch 'regmap/topic/irq' into regmap-next
Merge remote-tracking branch 'regmap/topic/range' into regmap-next
Sachin Kamat (1):
regmap: cache: Make regcache_sync_block_raw static
Stephen Warren (1):
regmap: don't corrupt work buffer in _regmap_raw_write()
Stratos Karafotis (1):
regmap: cache: Fix format specifier in dev_dbg
drivers/base/regmap/internal.h | 40 ++++++-
drivers/base/regmap/regcache-lzo.c | 6 +-
drivers/base/regmap/regcache-rbtree.c | 100 ++++++++---------
drivers/base/regmap/regcache.c | 196 ++++++++++++++++++++++++++++++---
drivers/base/regmap/regmap-debugfs.c | 94 ++++++++++++++--
drivers/base/regmap/regmap-irq.c | 3 +-
drivers/base/regmap/regmap.c | 92 +++++++++++-----
include/linux/regmap.h | 1 +
include/trace/events/regmap.h | 48 ++++++++
9 files changed, 462 insertions(+), 118 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-04-29 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 20:03 Mark Brown [this message]
2013-05-12 14:42 Mark Brown
2013-05-12 14:50 ` Mark Brown
2013-06-10 10:06 Mark Brown
2013-06-10 10:46 ` 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=20130429200337.GD3270@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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®