From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Cezary Rojewski <cezary.rojewski@intel.com>, linux-sound@vger.kernel.org
Cc: broonie@kernel.org, tiwai@suse.com, perex@perex.cz,
amade@asmblr.net, linux-kernel@vger.kernel.org, vkoul@kernel.org,
yung-chuan.liao@linux.intel.com
Subject: Re: [PATCH v2 0/7] ASoC: Intel: avs: Soundwire support
Date: Tue, 3 Nov 2026 18:20:48 +0100 [thread overview]
Message-ID: <bcfe64de-359c-4f16-9014-5d6f8bf30c40@linux.dev> (raw)
In-Reply-To: <20261103134958.2089136-1-cezary.rojewski@intel.com>
> Also, the existing code fetches the PDIs based on pre-defined "dai_id".
> That's not the case for the avs-driver. It simply asks: "is any PDI
> free?" and assigns it for the substream if one is found.
> No predefining. Again, this aligns with how HDAudio streaming is done.
Yeah but at the end of the day there's a 1:1 mapping between cpu_dai and
PDI, no?
All PDIs are created equal, a dynamic mapping doesn't make things more
efficient. It just makes things more complex to debug since you don't
have a fixed mapping between dailinks/stream/cpu_dai/PDI.
Put differently, couldn't the AVS driver work around that fixed mapping
to avoid changes to legacy platforms that have shipped many moons ago?
prev parent reply other threads:[~2026-11-03 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 13:49 Cezary Rojewski
2026-11-03 13:49 ` [PATCH v2 1/7] soundwire: intel: Define stubs when library is disabled Cezary Rojewski
2026-11-03 13:49 ` [PATCH v2 2/7] soundwire: intel: Allow for dynamic assignment of PDIs Cezary Rojewski
2026-11-03 13:49 ` [PATCH v2 3/7] soundwire: intel: Split PDIs and DAIs initialization Cezary Rojewski
2026-11-03 13:49 ` [PATCH v2 4/7] ASoC: Intel: avs: Pass irq to dsp_interrupt callback Cezary Rojewski
2026-11-03 13:49 ` [PATCH v2 5/7] ASoC: Intel: avs: SoundWire support Cezary Rojewski
2026-11-03 13:49 ` [PATCH v2 6/7] ASoC: Intel: avs: Expose common PCM functions Cezary Rojewski
2026-11-03 13:49 ` [PATCH v2 7/7] ASoC: Intel: avs: SoundWire PCM BE operations Cezary Rojewski
2026-11-03 17:20 ` 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=bcfe64de-359c-4f16-9014-5d6f8bf30c40@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®