[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166256096652.159155.11970501436356826295.b4-ty@kernel.org>
Date: Wed, 07 Sep 2022 15:29:26 +0100
From: Mark Brown <broonie@...nel.org>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
Cc: pierre-louis.bossart@...ux.intel.com, yc.hung@...iatek.com,
ranjani.sridharan@...ux.intel.com, Allen-KH.Cheng@...iatek.com,
trevor.wu@...iatek.com, perex@...ex.cz, matthias.bgg@...il.com,
lgirdwood@...il.com, geert@...ux-m68k.org,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
daniel.baluta@....com, chunxu.li@...iatek.com,
linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, kai.vehmanen@...ux.intel.com,
yung-chuan.liao@...ux.intel.com,
sound-open-firmware@...a-project.org, kernel@...labora.com,
peter.ujfalusi@...ux.intel.com, wenst@...omium.org,
tzungbi@...gle.com, tiwai@...e.com
Subject: Re: [PATCH 0/5] ASoC: Fixes for MT8195 SOF support
On Tue, 6 Sep 2022 11:27:22 +0200, AngeloGioacchino Del Regno wrote:
> This series fixes Sound Open Firmware support for MT8195 by making
> sure that the sound card driver is actually able to probe and IPC
> can finally happen.
> It is now possible to get DSP support for audio.
>
> Tested on MT8195 Tomato - Acer Chromebook Spin 513 CP513-2H (Pipewire).
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] ASoC: mediatek: mt8195-mt6359: Properly register sound card for SOF
commit: 64ec924c781ee846bd469be8d1d6bbed78c0f439
[2/5] ASoC: SOF: mediatek: mt8195: Import namespace SND_SOC_SOF_MTK_COMMON
commit: 404bec4c8f6c38ae5fa208344f1086d38026e93d
[3/5] ASoC: SOF: mediatek: mt8195: Add mailbox generic callbacks for IPC
commit: c2186a9b3a98f1ff814996aa52a019158bfad9c9
[4/5] ASoC: SOF: mediatek: mt8195: Add generic pcm_{open,close} callbacks
commit: cf84edeeb95ee8e76f12bb02a7444876d031bea7
[5/5] ASoC: SOF: mediatek: mt8195: Add devicetree support to select topologies
commit: 8a7d5d85ed2161869452ddb9ec45345dad665f52
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