mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] regmap updates for v4.4
Date: Mon, 2 Nov 2015 19:48:05 +0000	[thread overview]
Message-ID: <20151102194805.GJ20228@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 2591 bytes --]

The following changes since commit 25cb62b76430a91cc6195f902e61c2cb84ade622:

  Linux 4.3-rc5 (2015-10-11 11:09:45 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v4.4

for you to fetch changes up to d4a1a317e7478b70e18b9cc8eac7d29090121b6e:

  Merge remote-tracking branches 'regmap/topic/atomic', 'regmap/topic/debugfs' and 'regmap/topic/irq-hdr' into regmap-next (2015-10-12 19:25:07 +0100)

----------------------------------------------------------------
regmap: Updates for v4.4

Quite a few new features for regmap this time, mostly expanding things
around the edges of the existing functionality to cover more devices
rather than thinsg with wide applicability:

 - Support for offload of the update_bits() operation to hardware where
   devices implement bit level access.
 - Support for a few extra operations that need scratch buffers on
   fast_io devices where we can't sleep.
 - Expanded the feature set of regmap_irq to cope with some extra
   register layouts.
 - Cleanups to the debugfs code.

----------------------------------------------------------------
Guo Zeng (2):
      regmap: irq: add support for chips who have separate unmask registers
      regmap: irq: add ack_invert flag for chips using cleared bits as ack

Jon Ringle (1):
      regmap: Allow installing custom reg_update_bits function

Mark Brown (5):
      regmap: debugfs: Remove scratch buffer for register length calculation
      Merge tag 'ib-mfd-regmap-v4.3' of git://git.kernel.org/.../lee/mfd into regmap-irq-hdr
      Merge tag 'regmap-irq-unmask' into regmap-next
      Merge tag 'regmap-offload-update-bits' into regmap-next
      Merge remote-tracking branches 'regmap/topic/atomic', 'regmap/topic/debugfs' and 'regmap/topic/irq-hdr' into regmap-next

Qipeng Zha (1):
      regmap: Add generic macro to define regmap_irq

Rasmus Villemoes (3):
      regmap: debugfs: use snprintf return value in regmap_reg_ranges_read_file()
      regmap: debugfs: use memcpy instead of snprintf
      regmap: debugfs: simplify regmap_reg_ranges_read_file() slightly

Stephen Boyd (1):
      regmap: Allocate buffers with GFP_ATOMIC when fast_io == true

 drivers/base/regmap/internal.h       |  3 +++
 drivers/base/regmap/regmap-debugfs.c | 23 +++++++++----------
 drivers/base/regmap/regmap-irq.c     | 43 +++++++++++++++++++++++++++++++-----
 drivers/base/regmap/regmap.c         | 41 ++++++++++++++++++++++++----------
 include/linux/regmap.h               | 11 +++++++++
 5 files changed, 91 insertions(+), 30 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

                 reply	other threads:[~2015-11-02 19:48 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=20151102194805.GJ20228@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®