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.14
Date: Mon, 20 Jan 2025 15:04:20 +0000	[thread overview]
Message-ID: <10be53e4cb210fa41ab8abacc3cd26c3.broonie@kernel.org> (raw)

The following changes since commit 9d89551994a430b50c4fffcb1e617a057fa76e20:

  Linux 6.13-rc6 (2025-01-05 14:13:40 -0800)

are available in the Git repository at:

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

for you to fetch changes up to d406b354df909155ff0122acf80f3bc7410fa27e:

  Expand SoundWire MBQ register map support (2025-01-07 23:28:07 +0000)

----------------------------------------------------------------
regmap: Updates for v6.14

There's one big bit of work this time around, the addition of support for
a greater range of MBQ access sizes to SoundWire devices together with
support for deferred read/write.  The MBQ register maps generally have
variable register sizes, the variable regiseter size support allows them
to be handled much more naturally within regmap with less open coding in
drivers.  The deferred read/write support avoids spurious errors when
devices make use of a bus feature allowing them to indicate they're
busy.  These changes pull in a supporting SoundWire change, and there's
an ASoC change building off the new code.

The remainder of the changes are code cleanups.

----------------------------------------------------------------
Andy Shevchenko (5):
      regmap: cache: Use BITS_TO_BYTES()
      regmap: Use BITS_TO_BYTES()
      regmap: place foo / 8 and foo % 8 closer to each other
      regmap: cache: mapple: use kmalloc_array() to replace kmalloc()
      regmap: cache: rbtree: use krealloc_array() to replace krealloc()

Charles Keepax (4):
      soundwire: SDCA: Add additional SDCA address macros
      ASoC: SDCA: Update list of entity_0 controls
      regmap: sdw-mbq: Add support for further MBQ register sizes
      regmap: sdw-mbq: Add support for SDCA deferred controls

Mark Brown (3):
      regmap: Cleanup and microoptimization
      regmap: Merge up v6.12-rc2
      Expand SoundWire MBQ register map support

Richard Fitzgerald (1):
      regmap: regmap_multi_reg_read(): make register list const

 drivers/base/regmap/regcache-maple.c    |   7 +-
 drivers/base/regmap/regcache-rbtree.c   |  10 +-
 drivers/base/regmap/regcache.c          |   2 +-
 drivers/base/regmap/regmap-sdw-mbq.c    | 219 ++++++++++++++++++++++++++++----
 drivers/base/regmap/regmap.c            |  13 +-
 include/linux/regmap.h                  |  64 +++++++++-
 include/linux/soundwire/sdw_registers.h |  30 +++--
 include/sound/sdca_function.h           |  33 +++--
 8 files changed, 319 insertions(+), 59 deletions(-)

             reply	other threads:[~2025-01-20 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20 15:04 Mark Brown [this message]
2025-01-22 19:07 ` [GIT PULL] regmap updates for v6.14 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=10be53e4cb210fa41ab8abacc3cd26c3.broonie@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