From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
Cc: <broonie@kernel.org>, <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: Fri, 21 Feb 2025 09:46:27 +0000 [thread overview]
Message-ID: <Z7hLc647A8wUIQtO@opensource.cirrus.com> (raw)
In-Reply-To: <8f0f70de-d3cf-4956-a5aa-c5bed91a61cf@linux.dev>
On Thu, Feb 20, 2025 at 07:01:44AM -0600, Pierre-Louis Bossart wrote:
> 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.
>
We haven't really fully resolved that yet, however, I have
came to the conclusion that all the helper function bits I am
currently adding are completely agnostic of the choice.
So I think it makes most sense to address this once we are adding
an actually driver component. That way we will have the most
context for discussion.
Thanks,
Charles
next prev parent reply other threads:[~2025-02-21 9:46 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 ` [PATCH 0/4] Add SDCA register map support Pierre-Louis Bossart
2025-02-21 9:46 ` Charles Keepax [this message]
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=Z7hLc647A8wUIQtO@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox