All of
 help / color / mirror / Atom feed
From: Mark Brown <>
To: Linus Torvalds <>
Cc:, Mark Brown <>
Subject: [GIT PULL] regmap updates for v5.19
Date: Mon, 23 May 2022 14:11:56 +0100	[thread overview]
Message-ID: <> (raw)

The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:

  Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)

are available in the Git repository at: tags/regmap-v5.19

for you to fetch changes up to 5c422f0b970d287efa864b8390a02face404db5d:

  regmap: Add missing map->bus check (2022-05-09 12:48:45 +0100)

regmap: Updates for v5.19

The main change here is Marek's addition of bulk read/write callbacks
for individual regmaps, we've supported single register operations for a
while but there's enough hardware out there which can use bulk equivalents
to make it worthwhile.

Jeongtae Park (1):
      regmap: cache: set max_register with reg_stride

Marek Vasut (2):
      regmap: Add bulk read/write callbacks into regmap_config
      regmap: Add missing map->bus check

Mark Brown (1):
      regmap: Custom bulk operations for regmaps

Rikard Falkeborn (1):
      regmap: Constify static regmap_bus structs

 drivers/base/regmap/internal.h       |  4 ++
 drivers/base/regmap/regcache.c       |  4 +-
 drivers/base/regmap/regmap-i3c.c     |  2 +-
 drivers/base/regmap/regmap-sccb.c    |  2 +-
 drivers/base/regmap/regmap-sdw-mbq.c |  2 +-
 drivers/base/regmap/regmap-sdw.c     |  2 +-
 drivers/base/regmap/regmap-slimbus.c |  2 +-
 drivers/base/regmap/regmap-w1.c      |  6 +--
 drivers/base/regmap/regmap.c         | 78 +++++++++++++++++++-----------------
 include/linux/regmap.h               | 12 ++++++
 10 files changed, 67 insertions(+), 47 deletions(-)

             reply	other threads:[~2022-05-23 13:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 13:11 Mark Brown [this message]
2022-05-24 22:27 ` [GIT PULL] regmap updates for v5.19 pr-tracker-bot

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.