public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] regmap updates for v6.1
Date: Mon, 03 Oct 2022 13:46:22 +0100	[thread overview]
Message-ID: <20221003124639.E723CC433D6@smtp.kernel.org> (raw)

The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:

  Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v6.1

for you to fetch changes up to 01ed230761e51f0403b3f3845c11cb67014487e2:

  regmap: mmio: replace return 0 with break in switch statement (2022-09-22 12:33:18 +0100)

----------------------------------------------------------------
regmap: Updates for v6.1

This has been a busy release for regmap with one thing and other,
there's been an especially large interest in MMIO regmaps for some
reason.  The bulk of the changes are cleanups but there are several user
visible changes too:

 - Support for I/O ports in regmap-mmio.
 - Support for accelerated noinc operations in regmap-mmio.
 - Support for tracing the register values in bulk operations.

----------------------------------------------------------------
Andy Shevchenko (11):
      regmap: mmio: Remove mmio_relaxed member from context
      regmap: mmio: Get rid of broken 64-bit IO
      regmap: mmio: Introduce IO accessors that can talk to IO port
      regmap: mmio: Fix MMIO accessors to avoid talking to IO port
      regmap: Make use of get_unaligned_be24(), put_unaligned_be24()
      regmap: trace: Remove useless check for NULL for bulk ops
      regmap: trace: Remove explicit castings
      regmap: trace: Remove unneeded blank lines
      swab: Add array operations
      regmap: mmio: Use swabXX_array() helpers
      regmap: spi-avmm: Use swabXX_array() helpers

Colin Ian King (1):
      regmap: mmio: replace return 0 with break in switch statement

Dmitry Rokosov (1):
      regmap: introduce value tracing for regmap bulk operations

Linus Walleij (5):
      regmap: Support accelerated noinc operations
      regmap: mmio: Support accelerared noinc operations
      regmap/hexagon: Properly fix the generic IO helpers
      regmap: check right noinc bounds in debug print
      regmap: mmio: Fix rebase error

Mark Brown (1):
      regmap: mmio: Extending to support IO ports

 arch/hexagon/include/asm/io.h         |  25 +++
 drivers/base/regmap/regmap-mmio.c     | 289 +++++++++++++++++++++++++++-------
 drivers/base/regmap/regmap-spi-avmm.c |  14 +-
 drivers/base/regmap/regmap.c          | 167 +++++++++++++++++---
 drivers/base/regmap/trace.h           |  61 +++++--
 include/linux/regmap.h                |  11 ++
 include/linux/swab.h                  |  25 +++
 7 files changed, 489 insertions(+), 103 deletions(-)

             reply	other threads:[~2022-10-03 12:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 12:46 Mark Brown [this message]
2022-10-05  2:27 ` [GIT PULL] regmap updates for v6.1 Linus Torvalds
2022-10-05  2:41 ` 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:
  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=20221003124639.E723CC433D6@smtp.kernel.org \
    --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