From: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
To: lgirdwood@gmail.com, broonie@kernel.org
Cc: alsa-devel@alsa-project.org,
pierre-louis.bossart@linux.intel.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
yung-chuan.liao@linux.intel.com
Subject: [PATCH 0/3] ASoC: SOF: pcm/Intel: Handle IPC dependent sequencing correctly
Date: Wed, 22 Mar 2023 11:43:43 +0200 [thread overview]
Message-ID: <20230322094346.6019-1-peter.ujfalusi@linux.intel.com> (raw)
Hi,
IPC3 and IPC4 firmwares handle and execute tasks at different stages, like
managing DMAs.
In most cases these are aligned, but we have few exceptions that needs to be
handled differently.
This series introduces flags to handle the differing cases to make sure that
the correct sequencing is used regerless of the IPC version.
Regards,
Peter
---
Ranjani Sridharan (3):
ASoC: SOF: Intel: hda-dai: Do not perform DMA cleanup during stop
ASoC: SOF: pcm: Make hw_params reset conditional for IPC3
ASoC: SOF: pcm: Improve the pcm trigger sequence
sound/soc/sof/intel/hda-dai.c | 1 -
sound/soc/sof/ipc3-pcm.c | 1 +
sound/soc/sof/ipc4-pcm.c | 3 ++-
sound/soc/sof/pcm.c | 29 ++++++++++++++++++++++-------
sound/soc/sof/sof-audio.h | 6 ++++++
5 files changed, 31 insertions(+), 9 deletions(-)
--
2.40.0
next reply other threads:[~2023-03-22 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 9:43 Peter Ujfalusi [this message]
2023-03-22 9:43 ` [PATCH 1/3] ASoC: SOF: Intel: hda-dai: Do not perform DMA cleanup during stop Peter Ujfalusi
2023-03-22 9:43 ` [PATCH 2/3] ASoC: SOF: pcm: Make hw_params reset conditional for IPC3 Peter Ujfalusi
2023-03-22 9:43 ` [PATCH 3/3] ASoC: SOF: pcm: Improve the pcm trigger sequence Peter Ujfalusi
2023-03-22 18:47 ` [PATCH 0/3] ASoC: SOF: pcm/Intel: Handle IPC dependent sequencing correctly Mark Brown
2023-06-30 6:33 ` Sam Edwards
2023-06-30 6:59 ` Pierre-Louis Bossart
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=20230322094346.6019-1-peter.ujfalusi@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.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