From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org, Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: daniel.baluta@nxp.com, ranjani.sridharan@linux.intel.com,
pierre-louis.bossart@linux.intel.com
Subject: Re: [PATCH 0/3] ASoC: SOF: multi core support for 5.10
Date: Fri, 04 Sep 2020 11:03:36 +0100 [thread overview]
Message-ID: <159921381111.42159.653916682345610756.b4-ty@kernel.org> (raw)
In-Reply-To: <20200902140756.1427005-1-kai.vehmanen@linux.intel.com>
On Wed, 2 Sep 2020 17:07:53 +0300, Kai Vehmanen wrote:
> This series extends the multi-core support in SOF. Capability
> to specify which core to use, on a per component basis, is added
> to topology. The topology load functionality in SOF is modified to
> power up/down host controlled cores based on the topology
> description.
>
> Guennadi Liakhovetski (2):
> ASoC: SOF: add a "core" parameter to widget loading functions
> ASoC: SOF: support topology components on secondary cores
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: SOF: add a "core" parameter to widget loading functions
commit: 0dcdf84289fbf61cd42cbb1e379e2150aa17e31e
[2/3] ASoC: SOF: support topology components on secondary cores
commit: d1c6c4a9fd3da5c735386b0cdb44d79667f10a1b
[3/3] ASoC: SOF: topology: fix core enable sequence
commit: 8c9ff1219aef657954540147522ceaecced71b2b
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:[~2020-09-04 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 14:07 [PATCH 0/3] ASoC: SOF: multi core support for 5.10 Kai Vehmanen
2020-09-02 14:07 ` [PATCH 1/3] ASoC: SOF: add a "core" parameter to widget loading functions Kai Vehmanen
2020-09-02 14:07 ` [PATCH 2/3] ASoC: SOF: support topology components on secondary cores Kai Vehmanen
2020-09-02 14:07 ` [PATCH 3/3] ASoC: SOF: topology: fix core enable sequence Kai Vehmanen
2020-09-04 10:03 ` 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=159921381111.42159.653916682345610756.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@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