From: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
To: lgirdwood@gmail.com, broonie@kernel.org,
pierre-louis.bossart@linux.intel.com,
yung-chuan.liao@linux.intel.com, rander.wang@intel.com
Cc: alsa-devel@alsa-project.org, daniel.baluta@nxp.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com
Subject: [PATCH 0/3] ASoC: SOF: IPC4: Introduce message handling functionality
Date: Thu, 5 May 2022 12:48:15 +0300 [thread overview]
Message-ID: <20220505094818.10346-1-peter.ujfalusi@linux.intel.com> (raw)
Hi,
The series adds the basic IPC4 message handling code, implementing the ipc
callbacks.
Due to the difference between IPC3 and IPC4 messaging we need to introduce new
message container for IPC4, but the SOF internal callbacks and structures can be
kept as they were and leaving it for the IPC specific code to handle the
differences.
The series provides the foundation for both lowe level (sound/soc/sof/intel) and
high level IPC4 implementation (topologies, firmware loading, control handling,
etc).
Regards,
Peter
---
Peter Ujfalusi (3):
ASoC: SOF: Add rx_data pointer to snd_sof_ipc_msg struct
ASoC: SOF: Add initial header file for ipc4
ASoC: SOF: ipc4: Add support for mandatory message handling
functionality
include/sound/sof/ipc4/header.h | 460 ++++++++++++++++++++++++
sound/soc/sof/Makefile | 3 +-
sound/soc/sof/ipc4.c | 604 ++++++++++++++++++++++++++++++++
sound/soc/sof/sof-priv.h | 4 +
4 files changed, 1070 insertions(+), 1 deletion(-)
create mode 100644 include/sound/sof/ipc4/header.h
create mode 100644 sound/soc/sof/ipc4.c
--
2.36.0
next reply other threads:[~2022-05-05 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 9:48 Peter Ujfalusi [this message]
2022-05-05 9:48 ` [PATCH 1/3] ASoC: SOF: Add rx_data pointer to snd_sof_ipc_msg struct Peter Ujfalusi
2022-05-05 9:48 ` [PATCH 2/3] ASoC: SOF: Add initial header file for ipc4 Peter Ujfalusi
2022-05-05 9:48 ` [PATCH 3/3] ASoC: SOF: ipc4: Add support for mandatory message handling functionality Peter Ujfalusi
2022-05-05 15:12 ` [PATCH 0/3] ASoC: SOF: IPC4: Introduce " 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=20220505094818.10346-1-peter.ujfalusi@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.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