From: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
To: lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz
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 v3 0/9] ASoC: SOF: core/ipc4/mtl: Add support for PCM delay reporting
Date: Thu, 2 Feb 2023 15:29:45 +0200 [thread overview]
Message-ID: <20230202132954.26773-1-peter.ujfalusi@linux.intel.com> (raw)
Hi,
Changes since v2:
- Use div64_u64_rem() to make the code compile and work on non 64bit architectures
Changes since v1:
- The delay calculation updated to take into account the counter wrapping on both
ends (host and link side).
The following series adds support for the PCM delay reporting in SOF core level
and implements the needed infrastructure with IPC4 to finally enable it for MTL.
Currently this is only supported on MTL (and via IPC4), but with the
infrastructure in place it will be possible to support other platforms with
DeepBuffer.
Regards,
Peter
---
Rander Wang (9):
ASoC: SOF: add ipc4_fw_reg header file
ASoC: SOF: add fw_info_box support
ASoC: SOF: add time info structure for ipc4 path
ASoC: SOF: ipc4-pcm: allocate time info for pcm delay feature
ASoC: SOF: ipc4-pcm: add hw_params
ASoC: SOF: add delay function support in sof framework
ASoC: SOF: add get_stream_position ops for pcm delay
ASoC: SOF: Intel: mtl: add get_stream_position support
ASoC: SOF: ipc4-pcm: add delay function support
sound/soc/sof/intel/mtl.c | 14 +++
sound/soc/sof/intel/mtl.h | 6 +
sound/soc/sof/ipc4-fw-reg.h | 155 ++++++++++++++++++++++++
sound/soc/sof/ipc4-pcm.c | 232 ++++++++++++++++++++++++++++++++++++
sound/soc/sof/ipc4-priv.h | 15 +++
sound/soc/sof/ipc4.c | 3 +
sound/soc/sof/ops.h | 10 ++
sound/soc/sof/pcm.c | 13 ++
sound/soc/sof/sof-audio.h | 6 +
sound/soc/sof/sof-priv.h | 10 ++
10 files changed, 464 insertions(+)
create mode 100644 sound/soc/sof/ipc4-fw-reg.h
--
2.39.1
next reply other threads:[~2023-02-02 13:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 13:29 Peter Ujfalusi [this message]
2023-02-02 13:29 ` [PATCH v3 1/9] ASoC: SOF: add ipc4_fw_reg header file Peter Ujfalusi
2023-02-02 13:29 ` [PATCH v3 2/9] ASoC: SOF: add fw_info_box support Peter Ujfalusi
2023-02-02 13:29 ` [PATCH v3 3/9] ASoC: SOF: add time info structure for ipc4 path Peter Ujfalusi
2023-02-02 13:29 ` [PATCH v3 4/9] ASoC: SOF: ipc4-pcm: allocate time info for pcm delay feature Peter Ujfalusi
2023-02-02 13:29 ` [PATCH v3 5/9] ASoC: SOF: ipc4-pcm: add hw_params Peter Ujfalusi
2023-02-02 13:29 ` [PATCH v3 6/9] ASoC: SOF: add delay function support in sof framework Peter Ujfalusi
2023-02-02 13:29 ` [PATCH v3 7/9] ASoC: SOF: add get_stream_position ops for pcm delay Peter Ujfalusi
2023-02-02 13:29 ` [PATCH v3 8/9] ASoC: SOF: Intel: mtl: add get_stream_position support Peter Ujfalusi
2023-02-02 13:29 ` [PATCH v3 9/9] ASoC: SOF: ipc4-pcm: add delay function support Peter Ujfalusi
2023-02-03 15:07 ` [PATCH v3 0/9] ASoC: SOF: core/ipc4/mtl: Add support for PCM delay reporting 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=20230202132954.26773-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=perex@perex.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.