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 v4.2
Date: Tue, 23 Jun 2015 11:30:46 +0100 [thread overview]
Message-ID: <20150623103046.GA14071@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2397 bytes --]
The following changes since commit d4a4f75cd8f29cd9464a5a32e9224a91571d6649:
Linux 4.1-rc7 (2015-06-07 20:23:50 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v4.2
for you to fetch changes up to 8ca006adeffca5c760e86e660018ec9253d53dd3:
Merge remote-tracking branches 'regmap/topic/defaults', 'regmap/topic/irq' and 'regmap/topic/reg-params' into regmap-next (2015-06-17 17:40:08 +0100)
----------------------------------------------------------------
regmap: Fixes for v4.2
As well as a few fixes and updates for API changes there's two new
features for the API:
- Better support for handling a reset of the underlying hardware,
marking the register map as needing a resync to the device when
we need to do that automatically.
- Support for querying the size and stride of the register map,
allowing higher level frameworks to configure themselves more
readily.
----------------------------------------------------------------
Arun Chandran (1):
regmap: Fix regmap_bulk_read in BE mode
Julia Lawall (1):
regmap: drop unneeded goto
Kevin Cernekee (2):
regmap: Add a helper function for regcache sync test
regmap: Use regcache_mark_dirty() to indicate power loss or reset
Krzysztof Kozlowski (1):
regmap: Constify irq_domain_ops
Mark Brown (4):
Merge remote-tracking branch 'regmap/fix/core' into regmap-linus
Merge remote-tracking branch 'regmap/fix/field' into regmap-linus
Merge remote-tracking branch 'regmap/topic/core' into regmap-next
Merge remote-tracking branches 'regmap/topic/defaults', 'regmap/topic/irq' and 'regmap/topic/reg-params' into regmap-next
Maxime Coquelin (1):
regmap: Fix possible shift overflow in regmap_field_init()
Rob Herring (1):
regmap: kill off set_irq_flags usage
Srinivas Kandagatla (2):
regmap: Introduce regmap_get_max_register
regmap: Introduce regmap_get_reg_stride
dashsriram (1):
regmap: irq: Fixed a typo error
drivers/base/regmap/internal.h | 3 +++
drivers/base/regmap/regcache.c | 45 ++++++++++++++++++++++++++--------------
drivers/base/regmap/regmap-irq.c | 11 ++--------
drivers/base/regmap/regmap.c | 32 ++++++++++++++++++++++------
include/linux/regmap.h | 14 +++++++++++++
5 files changed, 75 insertions(+), 30 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
reply other threads:[~2015-06-23 10:30 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=20150623103046.GA14071@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®