On Mon, 18 Oct 2021 16:50:31 +0530, Vijendar Mukunda wrote: > Yellow Carp platform is new APU series based on acp6.x design. > This patch set adds an ASoC driver for the ACP (Audio CoProcessor) > block on AMD Yellow Carp APU with DMIC endpoint support. > > changes since v1: > - fixed SPDX commenting style in acp6x pci driver. > - fixed Copyright commenting style in acp6x pci driver, > pdm dma driver and machine driver files. > - fixed local variable check logic in acp6x_power_on() function. > - fixed Kconfig indentation issue > - removed irq_flag local variable in irq handler. > - add dmi info check in machine driver probe > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/13] ASoC: amd: add Yellow Carp ACP6x IP register header commit: 53880e382bb1323897f43f16f4b1b98ac5044871 [02/13] ASoC: amd: add Yellow Carp ACP PCI driver commit: c62442bd5d9f86575d74c77b891ef0df9e3cb6dd [03/13] ASoC: amd: add acp6x init/de-init functions commit: 8c7161f2c97b2dba018ecf0af8a0553e283a5c3e [04/13] ASoC: amd: add platform devices for acp6x pdm driver and dmic driver commit: fc329c1de49825a30d5381e18316a3fd45aac7a9 [05/13] ASoC: amd: add acp6x pdm platform driver commit: 7610174a5bfe6cf34eda8f972311e629ae6dc2d1 [06/13] ASoC: amd: add acp6x irq handler commit: cc0deaa2dc7300bb33e44e52cde0b6947a5d3a5d [07/13] ASoC: amd: add acp6x pdm driver dma ops commit: ceb4fcc13ae58102ad31aa4071d9e57e57eea3df [08/13] ASoC: amd: add acp6x pci driver pm ops commit: c8212df7bc0f2ed323ad1da96106792103ee94f1 [09/13] ASoC: amd: add acp6x pdm driver pm ops commit: 4c2e711af2193bc58f247f32edc30ee6a15e71f2 [10/13] ASoC: amd: enable Yellow carp acp6x drivers build commit: 89728d97db3f078aceb967ebe5ed2d0797b6a117 [11/13] ASoC: amd: create platform device for acp6x machine driver commit: 058dfdf37f25580423fd21d4b78d2daf217d0cf5 [12/13] ASoC: amd: add YC machine driver using dmic commit: fa991481b8b22a7797a828135ce62a73791bbe39 [13/13] ASoC: amd: enable Yellow Carp platform machine driver build commit: a80d7edadfa16fa1d4aca4a2253a0af921c3aaef 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
