mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: broonie@kernel.org, tiwai@suse.com, perex@perex.cz,
	amade@asmblr.net, linux-kernel@vger.kernel.org,
	yung-chuan.liao@linux.intel.com, vkoul@kernel.org,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>
Subject: Re: [PATCH v3 7/7] ASoC: Intel: avs: SoundWire PCM BE operations
Date: Tue, 10 Nov 2026 09:02:41 +0100	[thread overview]
Message-ID: <68fe056b-7351-4033-81ac-3dd346154842@linux.dev> (raw)
In-Reply-To: <5fa0ba39-cd95-4644-8b7c-8327a3e75f7e@intel.com>


>>> +
>>> +	pdi = sdw_cdns_assign_pdi(codec->bus, dir);
>>> +	if (!pdi) {
>>> +		ret = -EBUSY;
>>> +		goto err_assign_pdi;
>>> +	}
>>> +
>>> +	/* Fulfill the codec needs by setting the sdw_stream. */
>>> +	codec_dai = snd_soc_rtd_to_codec(rtd, 0);
>>> +	snd_soc_dai_set_stream(codec_dai, sdw_stream, substream->stream);
>>
>> That absolutely does not scale to the case where you have multiple
>> cpu_dais and multiple codec_dais.
>>
>> Please take a look at the sof_sdw machine driver (same solution used by
>> AMD), and please use the sdw_utils library to deal with all the stream
>> management.
> 
> 
> I believe you are talking about aggregation.  No intention to support
> that with this code.
> 
> After reading the read I have an impression that the expectation of this
> patchset is: full brown SoundWire support.  I wish I could agree with
> you.  The reality is: standard PCM over codecs with and without SDCA.
> If I get a user and an external release on top of that, I'll come back
> and revisit.  The code present here provides simple implementation of
> the goal, basically mirroring what's done for HDA in pcm.c nicely making
> it easy to follow.
well, I find it interesting that you are suggesting changes that impact
existing to SoundWire *products* for what appears to be an experimental
setup that will have to be changed *again* if and when there's a user.

It's ok to push background changes ahead of time to prepare the future.
I am not sure what to think of your approach.

a) Mirroring HDaudio is not the goal, if that comes with a substandard
way of using the SoundWire subsystem and capabilities does all this
belong in the mainline? My take is that support for two amps is a
standard feature, be they on the same link or not.
b) At the very least you should have disclosed your goals, limitations
of your approach, and be mindful of reviewer time.

      reply	other threads:[~2026-11-10  8:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 12:15 [PATCH v3 0/7] ASoC: Intel: avs: Soundwire support Cezary Rojewski
2026-11-06 12:15 ` [PATCH v3 1/7] soundwire: intel: Define stubs when library is disabled Cezary Rojewski
2026-11-06 12:15 ` [PATCH v3 2/7] soundwire: intel: Allow for dynamic assignment of PDIs Cezary Rojewski
2026-11-06 12:32   ` Cezary Rojewski
2026-11-06 19:59   ` kernel test robot
2026-11-06 12:15 ` [PATCH v3 3/7] soundwire: intel: Split PDIs and DAIs initialization Cezary Rojewski
2026-11-06 12:15 ` [PATCH v3 4/7] ASoC: Intel: avs: Pass irq to dsp_interrupt callback Cezary Rojewski
2026-11-06 12:15 ` [PATCH v3 5/7] ASoC: Intel: avs: SoundWire support Cezary Rojewski
2026-11-06 12:15 ` [PATCH v3 6/7] ASoC: Intel: avs: Expose common PCM functions Cezary Rojewski
2026-11-06 12:15 ` [PATCH v3 7/7] ASoC: Intel: avs: SoundWire PCM BE operations Cezary Rojewski
2026-11-06 12:55   ` Pierre-Louis Bossart
2026-11-09  9:09     ` Cezary Rojewski
2026-11-10  8:02       ` Pierre-Louis Bossart [this message]

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=68fe056b-7351-4033-81ac-3dd346154842@linux.dev \
    --to=pierre-louis.bossart@linux.dev \
    --cc=amade@asmblr.net \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=vkoul@kernel.org \
    --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

all inboxes | Powered by JetHome®