All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
Cc: broonie@kernel.org, lgirdwood@gmail.com,
	yung-chuan.liao@linux.intel.com, peter.ujfalusi@linux.intel.com,
	patches@opensource.cirrus.com, linux-sound@vger.kernel.org
Subject: Re: [PATCH 0/7] Add SDCA DAI ops helpers
Date: Wed, 16 Jul 2025 09:28:12 +0100	[thread overview]
Message-ID: <aHdinBnBvSsfx/nA@opensource.cirrus.com> (raw)
In-Reply-To: <4336e9c1-e05c-46d6-939a-53fefb8f9a14@linux.dev>

On Tue, Jul 15, 2025 at 07:58:32PM +0200, Pierre-Louis Bossart wrote:
> On 7/7/25 14:41, Charles Keepax wrote:
> > First, a couple of minor code fixups to already submitted code. Then
> > some patches to add new DAI ops helpers for the SDCA stuff, these allow
> > configuring things like the sample rate and finding out which SoundWire
> > port should be used for a specific SDCA streaming input/output terminal.
> > Still a few bits of outstanding work here (propogation of Cluster
> > information particularly) but his should be good enough to get some
> > basic use-cases working.
> 
> For the patchset:
> 
> Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
> 
> > Hopefully we are getting fairly close to completing a first version of
> > the SDCA work now. Should be one more series to add FDL (firmware
> > downloading), then we should be able to send a first version of the
> > actual SDCA class driver itself.
> 
> FDL is a very desirable feature, but shouldn't there be an UMP
> (Universal Message Passing) layer first? HID and FDL rely on UMP.
> I would have expected the ownership changes to be handled in
> a shared UMP library or set of helpers, no?

Yeah we are still working through the last iterations internally
on the FDL stuff. I think it probably does make sense to pull
out some UMP helpers (indeed I was have a look at it yesterday)
although they should be pretty simple so I imagine we will just
send them as part of the FDL set (subject to change as we work
through it).

Thanks,
Charles

  reply	other threads:[~2025-07-16  8:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 12:41 [PATCH 0/7] Add SDCA DAI ops helpers Charles Keepax
2025-07-07 12:41 ` [PATCH 1/7] ASoC: SDCA: Allow read-only controls to be deferrable Charles Keepax
2025-07-07 12:41 ` [PATCH 2/7] ASoC: SDCA: Remove overly chatty input pin list warning Charles Keepax
2025-07-07 12:41 ` [PATCH 3/7] ASoC: SDCA: Move SDCA search functions and export Charles Keepax
2025-07-07 12:41 ` [PATCH 4/7] ASoC: soc-dai: Add private data to snd_soc_dai Charles Keepax
2025-07-07 12:41 ` [PATCH 5/7] ASoC: SDCA: Add helper to add DAI constraints Charles Keepax
2025-07-07 12:41 ` [PATCH 6/7] ASoC: SDCA: Add a helper to get the SoundWire port number Charles Keepax
2025-07-07 12:41 ` [PATCH 7/7] ASoC: SDCA: Add hw_params() helper function Charles Keepax
2025-07-15 17:58 ` [PATCH 0/7] Add SDCA DAI ops helpers Pierre-Louis Bossart
2025-07-16  8:28   ` Charles Keepax [this message]
2025-07-21  9:55     ` Pierre-Louis Bossart
2025-07-16 18:41 ` 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=aHdinBnBvSsfx/nA@opensource.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --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 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.