From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
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, seppo.ingalsuo@linux.intel.com
Subject: Re: [PATCH 0/4] ASoC: SOF: ipc4-topology: Fixes for pipelines with SRC
Date: Tue, 22 Aug 2023 17:33:19 +0100 [thread overview]
Message-ID: <169272199975.71502.8304091663464060005.b4-ty@kernel.org> (raw)
In-Reply-To: <20230821113629.5017-1-peter.ujfalusi@linux.intel.com>
On Mon, 21 Aug 2023 14:36:25 +0300, Peter Ujfalusi wrote:
> the SRC component in a pipeline provides flexibility on the sampling
> rate which was not handled previously.
>
> This series will improve the kernel side with the needed logic to be
> able to deal with the SRC type of components in pipelines.
>
> Regards,
> Peter
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] ASoC: SOF: ipc4-topology: Modify pipeline params based on SRC output format
commit: ef24388225f87f2604522fe86fafacc271ec4a29
[2/4] ASoC: SOF: ipc4-topology: Fix the output reference params for SRC
commit: 56ecc164040b3685f6cb36b4d513d73d0f88140b
[3/4] ASoC: SOF: ipc4-topology: Fix pipeline params at the output of copier
commit: 769e8f6cd7182c95d4bd37491e13300ff067c7a7
[4/4] ASoC: SOF: ipc4-topology: Modify the reference output valid_bits for copier
commit: 70b0924b22efe2135222a2c7141a83dfe0c78779
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
prev parent reply other threads:[~2023-08-22 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 11:36 [PATCH 0/4] ASoC: SOF: ipc4-topology: Fixes for pipelines with SRC Peter Ujfalusi
2023-08-21 11:36 ` [PATCH 1/4] ASoC: SOF: ipc4-topology: Modify pipeline params based on SRC output format Peter Ujfalusi
2023-08-21 11:36 ` [PATCH 2/4] ASoC: SOF: ipc4-topology: Fix the output reference params for SRC Peter Ujfalusi
2023-08-21 11:36 ` [PATCH 3/4] ASoC: SOF: ipc4-topology: Fix pipeline params at the output of copier Peter Ujfalusi
2023-08-21 11:36 ` [PATCH 4/4] ASoC: SOF: ipc4-topology: Modify the reference output valid_bits for copier Peter Ujfalusi
2023-08-22 16:33 ` Mark Brown [this message]
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=169272199975.71502.8304091663464060005.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=seppo.ingalsuo@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