From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] regmap updates for v3.8
Date: Wed, 12 Dec 2012 16:19:23 +0900 [thread overview]
Message-ID: <20121212071922.GE30719@opensource.wolfsonmicro.com> (raw)
The following changes since commit 9489e9dcae718d5fde988e4a684a0f55b5f94d17:
Linux 3.7-rc7 (2012-11-25 17:59:19 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-3.8
for you to fetch changes up to 7c8a2994309214cbb6dba33cd72ec85f91fd6fcd:
Merge remote-tracking branch 'regmap/topic/type' into regmap-next (2012-12-11 12:39:49 +0900)
----------------------------------------------------------------
regmap: Updates for v3.8
Quite a few enhancements this time around, helpers and diagnostics for
the most part which is good to see:
- Addition of table based lookups for the register access checks from
Davide Ciminaghi, making life easier for drivers with big blocks of
similar registers.
- Allow drivers to get the irqdomain for regmap irq_chips, allowing the
domain to be used with other APIs.
- Debug improvements for paged register maps.
- Performance improvments for some of the diagnostic infrastructure,
very helpful for devices with large register maps.
----------------------------------------------------------------
Davide Ciminaghi (2):
regmap: make lock/unlock functions customizable
regmap: introduce tables for readable/writeable/volatile/precious checks
Fabio Estevam (1):
regmap: Fix printing of size_t variable
Mark Brown (22):
regmap: irq: Allow users to retrieve the irq_domain
regmap: Rename n_ranges to num_ranges
regmap: When we sanity check during range adds say what errors we find
regmap: Allow ranges to be named
regmap: Factor out debugfs register read
regmap: Provide debugfs read of register ranges
regmap: Factor range lookup out of page selection
regmap: Make return code checks consistent
regmap: Split raw writes that cross window boundaries
regmap: core: Report registers in hex when we can't cache
Merge branches 'topic/core' and 'topic/range' of git://git.kernel.org/.../broonie/regmap into regmap-table
Merge branch 'topic/lock' of git://git.kernel.org/.../broonie/regmap into regmap-table
regmap: Cache register and value sizes for debugfs
regmap: debugfs: Avoid overflows for very small reads
regmap: debugfs: Factor out initial seek
regmap: debugfs: Cache offsets of valid regions for dump
Merge remote-tracking branch 'regmap/topic/core' into regmap-next
Merge remote-tracking branch 'regmap/topic/debugfs' into regmap-next
Merge remote-tracking branch 'regmap/topic/domain' into regmap-next
Merge remote-tracking branch 'regmap/topic/lock' into regmap-next
Merge remote-tracking branch 'regmap/topic/table' into regmap-next
Merge remote-tracking branch 'regmap/topic/type' into regmap-next
Paul Bolle (1):
regmap: silence GCC warning
drivers/base/regmap/internal.h | 24 ++-
drivers/base/regmap/regmap-debugfs.c | 148 +++++++++++++++++--
drivers/base/regmap/regmap-irq.c | 19 +++
drivers/base/regmap/regmap.c | 269 ++++++++++++++++++++++++----------
include/linux/regmap.h | 95 +++++++++++-
5 files changed, 453 insertions(+), 102 deletions(-)
reply other threads:[~2012-12-12 7:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121212071922.GE30719@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--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