From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: broonie@kernel.org
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: [PATCH v4 0/3] ASoC: cs35l56: Replace open-coded SoundWire regmap with generic regmap-sdw
Date: Thu, 21 May 2026 12:54:17 +0100 [thread overview]
Message-ID: <20260521115420.978616-1-rf@opensource.cirrus.com> (raw)
This series replaces the entirely custom SoundWire regmap with the generic
regmap-sdw. The reasons for doing this are:
- Avoid code duplication
- Avoid effort of keeping custom implementation up-to-date
- Prepare for supporting BRA
Changes in V4:
- In patch #1 moved dereference of regmap_config after it has been
checked for not-NULL.
Changes in V3:
- Change cs35l56-shared-test KUnit test to handle the offset addresses
passed into its mock regmap bus.
Changes in V2:
- Select REGMAP_SOUNDWIRE
Richard Fitzgerald (3):
ASoC: cs35l56-shared-test: Subtract reg_base offset in dummy regmap
ASoC: cs35l56: Use reg_base to offset addresses on SoundWire
ASoC: cs35l56: Use standard SoundWire regmap implementation
sound/soc/codecs/Kconfig | 2 +-
sound/soc/codecs/cs35l56-sdw.c | 137 +++++++++----------------
sound/soc/codecs/cs35l56-shared-test.c | 6 ++
sound/soc/codecs/cs35l56-shared.c | 2 +
sound/soc/codecs/cs35l56.h | 1 +
5 files changed, 59 insertions(+), 89 deletions(-)
--
2.47.3
next reply other threads:[~2026-05-21 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 11:54 Richard Fitzgerald [this message]
2026-05-21 11:54 ` [PATCH v4 1/3] ASoC: cs35l56-shared-test: Subtract reg_base offset in dummy regmap Richard Fitzgerald
2026-05-21 11:54 ` [PATCH v4 2/3] ASoC: cs35l56: Use reg_base to offset addresses on SoundWire Richard Fitzgerald
2026-05-21 11:54 ` [PATCH v4 3/3] ASoC: cs35l56: Use standard SoundWire regmap implementation Richard Fitzgerald
2026-05-21 23:17 ` [PATCH v4 0/3] ASoC: cs35l56: Replace open-coded SoundWire regmap with generic regmap-sdw Mark Brown
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=20260521115420.978616-1-rf@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
/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