From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Cc: linux-sound@vger.kernel.org, kai.vehmanen@linux.intel.com,
ranjani.sridharan@linux.intel.com,
yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev,
jyri.sarha@linux.intel.com
Subject: Re: [PATCH] ASoC: sof: ipc4-topology: Add support to sched_domain attribute
Date: Fri, 29 Aug 2025 23:19:21 +0100 [thread overview]
Message-ID: <175650596145.395832.10404747327113318803.b4-ty@kernel.org> (raw)
In-Reply-To: <20250829151101.27327-1-peter.ujfalusi@linux.intel.com>
On Fri, 29 Aug 2025 18:11:01 +0300, Peter Ujfalusi wrote:
> Add SOF_TKN_COMP_SCHED_DOMAIN and connect it to struct snd_sof_widget
> comp_domain member, with new get_token_comp_domain() function.
>
> The logic is such that if the topology attribute is not present in the
> widget node the corresponding IPC4 extension value is taken from the
> module's manifest like before. But if the attribute is found and
> recognized its value overrides what is there in the manifest.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: sof: ipc4-topology: Add support to sched_domain attribute
commit: 3d439e1ec3368fae17db379354bd7a9e568ca0ab
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:[~2025-08-29 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 15:11 [PATCH] ASoC: sof: ipc4-topology: Add support to sched_domain attribute Peter Ujfalusi
2025-08-29 22:19 ` 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=175650596145.395832.10404747327113318803.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=jyri.sarha@linux.intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).