From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Charles Keepax <ckeepax@opensource.cirrus.com>, broonie@kernel.org
Cc: lgirdwood@gmail.com, peter.ujfalusi@linux.intel.com,
yung-chuan.liao@linux.intel.com, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org
Subject: Re: [PATCH 0/4] Add SDCA register map support
Date: Thu, 20 Feb 2025 07:01:44 -0600 [thread overview]
Message-ID: <8f0f70de-d3cf-4956-a5aa-c5bed91a61cf@linux.dev> (raw)
In-Reply-To: <20250217140159.2288784-1-ckeepax@opensource.cirrus.com>
On 2/17/25 08:01, Charles Keepax wrote:
> This series is the next step of adding SDCA support. Here we add
> helper functions to allow drivers to easily use the SDCA DisCo
> information to create a register map for the device.
Can you remind me where we ended-up in the discussion on one regmap per physical device or one regmap per function?
The DisCo definition are all function-centric, but the physical SoundWire bus access for all read/writes is shared by all functions so having a single regmap isn't silly either.
> The basic idea here is the code takes the list of SDCA controls parsed
> from DisCo and uses primarily the Access Mode to determine if the
> register should be marked as readable/writable etc. Further more
> some additional concepts such as DisCo Constants and Defaults are
> handled. There is some potential confusion, as DisCo Constants are
> handled as an entry in the regmap defaults table, whereas a DisCo
> Default is simply handled as a write to the register. Alas the naming
> confusion is an unavoidable result of the slight impedance mismatch
> between the two systems.
>
> Thanks,
> Charles
>
> Charles Keepax (4):
> regcache: Add support for sorting defaults arrays
> ASoC: SDCA: Add generic regmap SDCA helpers
> ASoC: SDCA: Add regmap helpers for parsing for DisCo Constant values
> ASoC: SDCA: Add helper to write out defaults and fixed values
The code looks fine, thanks!
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
>
> drivers/base/regmap/regcache.c | 31 ++++
> include/linux/regmap.h | 7 +
> include/sound/sdca_regmap.h | 31 ++++
> sound/soc/sdca/Makefile | 2 +-
> sound/soc/sdca/sdca_regmap.c | 321 +++++++++++++++++++++++++++++++++
> 5 files changed, 391 insertions(+), 1 deletion(-)
> create mode 100644 include/sound/sdca_regmap.h
> create mode 100644 sound/soc/sdca/sdca_regmap.c
>
next prev parent reply other threads:[~2025-02-20 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 14:01 [PATCH 0/4] Add SDCA register map support Charles Keepax
2025-02-17 14:01 ` [PATCH 1/4] regcache: Add support for sorting defaults arrays Charles Keepax
2025-02-17 14:01 ` [PATCH 2/4] ASoC: SDCA: Add generic regmap SDCA helpers Charles Keepax
2025-02-17 14:01 ` [PATCH 3/4] ASoC: SDCA: Add regmap helpers for parsing for DisCo Constant values Charles Keepax
2025-02-17 14:01 ` [PATCH 4/4] ASoC: SDCA: Add helper to write out defaults and fixed values Charles Keepax
2025-02-20 13:01 ` Pierre-Louis Bossart [this message]
2025-02-21 9:46 ` [PATCH 0/4] Add SDCA register map support Charles Keepax
2025-02-27 17:27 ` 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=8f0f70de-d3cf-4956-a5aa-c5bed91a61cf@linux.dev \
--to=pierre-louis.bossart@linux.dev \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=yung-chuan.liao@linux.intel.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 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.