[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166074666372.210979.8582498171681865301.b4-ty@kernel.org>
Date: Wed, 17 Aug 2022 15:31:03 +0100
From: Mark Brown <broonie@...nel.org>
To: alsa-devel@...a-project.org,
Daniel Baluta <daniel.baluta@....nxp.com>
Cc: laurentiu.mihalcea@....com, peter.ujfalusi@...ux.intel.com,
lgirdwood@...il.com, linux-kernel@...r.kernel.org,
yung-chuan.liao@...ux.intel.com, daniel.baluta@...il.com,
ranjani.sridharan@...ux.intel.com, kai.vehmanen@...ux.intel.com,
Daniel Baluta <daniel.baluta@....com>,
pierre-louis.bossart@...ux.intel.com
Subject: Re: [PATCH 0/4] Enable timestamp support for SOF compress driver
On Wed, 17 Aug 2022 11:05:25 +0300, Daniel Baluta wrote:
> From: Daniel Baluta <daniel.baluta@....com>
>
> This patchseries computes pcm_io_frames from the DAI position reported
> by SOF firmware.
>
> Using pcm_io_frames userspace applications can later compute timestamps
> for compressed stream.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] ASoC: SOF: compress: Remove byte offset computation
commit: bab10ec9fd9dc1537b705d0dd3862dd5982b921f
[2/4] ASoC: SOF: compress: Introduce sof_compr_stream
commit: e3091f0a3f563ad1c9b60c290752e1190b67ea97
[3/4] ASoC: SOF: compress: Save channel count and sample bytes
commit: 3ccbe6887747679d15e5c9524b23754281a24d9e
[4/4] ASoC: SOF: compress: Add support for computing timestamps
commit: c1a731c71359407eae4fd0a5fd675ef25a582764
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
Powered by blists - more mailing lists