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,
rander.wang@intel.com
Subject: Re: [PATCH 0/5] ASoC: SOF: Intel/ipc4: Support for low power playback (d0i3)
Date: Tue, 14 Feb 2023 18:01:32 +0000 [thread overview]
Message-ID: <167639769261.3067697.3307769734340089930.b4-ty@kernel.org> (raw)
In-Reply-To: <20230214103345.30669-1-peter.ujfalusi@linux.intel.com>
On Tue, 14 Feb 2023 12:33:40 +0200, Peter Ujfalusi wrote:
> The following series will enable the the Low Power Audio (LPA) playback on Intel
> platforms when using IPC4.
>
> The support is closely follows how IPC3 supports similar use case.
>
> All depending patches are upstream and our CI have been testing this feature for
> some time without issues.
>
> [...]
Applied to
broonie/sound.git for-next
Thanks!
[1/5] ASoC: SOF: Introduce a new set_pm_gate() IPC PM op
commit: 167ca6a4fd87726e044df2db38fe86f6cb0fb907
[2/5] ASoC: SOF: Intel: hda-dsp: use set_pm_gate according to ipc version
commit: 3c168838fb0d64dd64f7d65cdbd7d127ce6112ef
[3/5] ASoC: SOF: ipc4: Wake up dsp core before sending ipc msg
commit: 1c91e927e55cef17bafd8903cb34a7d12968ae6d
[4/5] ASoC: SOF: Intel: Enable d0i3 work for ipc4
commit: 3e6b6ed34bda047a818003a8c06d368eb3596bba
[5/5] ASoC: SOF: Intel: hda-dsp: Set streaming flag for d0i3
commit: 6611b975eb87d7793e4632575649308762e7d01e
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-02-14 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 10:33 [PATCH 0/5] ASoC: SOF: Intel/ipc4: Support for low power playback (d0i3) Peter Ujfalusi
2023-02-14 10:33 ` [PATCH 1/5] ASoC: SOF: Introduce a new set_pm_gate() IPC PM op Peter Ujfalusi
2023-02-14 10:33 ` [PATCH 2/5] ASoC: SOF: Intel: hda-dsp: use set_pm_gate according to ipc version Peter Ujfalusi
2023-02-14 10:33 ` [PATCH 3/5] ASoC: SOF: ipc4: Wake up dsp core before sending ipc msg Peter Ujfalusi
2023-02-14 10:33 ` [PATCH 4/5] ASoC: SOF: Intel: Enable d0i3 work for ipc4 Peter Ujfalusi
2023-02-14 10:33 ` [PATCH 5/5] ASoC: SOF: Intel: hda-dsp: Set streaming flag for d0i3 Peter Ujfalusi
2023-02-14 18:01 ` 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=167639769261.3067697.3307769734340089930.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=rander.wang@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