From: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
To: lgirdwood@gmail.com, broonie@kernel.org, chao.song@linux.intel.com
Cc: alsa-devel@alsa-project.org, kai.vehmanen@linux.intel.com,
pierre-louis.bossart@linux.intel.com, rander.wang@intel.com,
ranjani.sridharan@linux.intel.com,
yung-chuan.liao@linux.intel.com
Subject: [PATCH 0/3] ASoC: SOF: ipc4-topology: Add widget queue support
Date: Mon, 7 Nov 2022 10:57:03 +0200 [thread overview]
Message-ID: <20221107085706.2550-1-peter.ujfalusi@linux.intel.com> (raw)
Hi,
with SOF topology2 for IPC4, widgets might have mutliple queues they can be
connected.
The queues to use between components are descibed in the topology file.
This series adds widget queue support (specify which pin to connect) for
ipc4-topology with topology2.
Note: currently queue 0 of a widget is used as hardwired default.
Regards,
Peter
---
Chao Song (3):
ASoC: SOF: Add support for parsing the number of sink/source pins
ASoC: SOF: Add support to parse pin binding array from topology
ASoC: SOF: topology: Add helper to get/put widget queue id
include/uapi/sound/sof/tokens.h | 9 ++
sound/soc/sof/ipc4-topology.c | 133 +++++++++++++++++++++---
sound/soc/sof/sof-audio.h | 42 ++++++++
sound/soc/sof/topology.c | 177 ++++++++++++++++++++++++++++++--
4 files changed, 340 insertions(+), 21 deletions(-)
--
2.38.1
next reply other threads:[~2022-11-07 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 8:57 Peter Ujfalusi [this message]
2022-11-07 8:57 ` [PATCH 1/3] ASoC: SOF: Add support for parsing the number of sink/source pins Peter Ujfalusi
2022-11-07 8:57 ` [PATCH 2/3] ASoC: SOF: Add support to parse pin binding array from topology Peter Ujfalusi
2022-11-07 8:57 ` [PATCH 3/3] ASoC: SOF: topology: Add helper to get/put widget queue id Peter Ujfalusi
2022-11-10 17:55 ` [PATCH 0/3] ASoC: SOF: ipc4-topology: Add widget queue support 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=20221107085706.2550-1-peter.ujfalusi@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=chao.song@linux.intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@intel.com \
--cc=ranjani.sridharan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox