[0/5] Add tdm support in acp machine driver

Message

Venkata Prasad Potturu Dec. 20, 2022, 7:27 a.m. UTC

This patch set is to add new cpu dai, refactor dai format
implementation and add tdm support in acp machine driver.

Venkata Prasad Potturu (5):
  ASoC: amd: acp: Refactor i2s bclk calculation
  ASoC: amd: acp: Add new cpu dai's in machine driver
  ASoC: amd: acp: Refactor dai format implementation
  ASoC: amd: acp: Add tdm support in machine driver
  ASoC: amd: acp: Enable tdm support for skyrim platforms

 sound/soc/amd/acp/acp-legacy-mach.c |  13 ++
 sound/soc/amd/acp/acp-mach-common.c | 275 +++++++++++++++++++++++-----
 sound/soc/amd/acp/acp-mach.h        |   4 +
 sound/soc/amd/acp/acp-sof-mach.c    |  14 ++
 4 files changed, 256 insertions(+), 50 deletions(-)

Comments

Mark Brown Jan. 12, 2023, 3:12 p.m. UTC | #1

On Tue, 20 Dec 2022 12:57:00 +0530, Venkata Prasad Potturu wrote:
> This patch set is to add new cpu dai, refactor dai format
> implementation and add tdm support in acp machine driver.
> 
> Venkata Prasad Potturu (5):
>   ASoC: amd: acp: Refactor i2s bclk calculation
>   ASoC: amd: acp: Add new cpu dai's in machine driver
>   ASoC: amd: acp: Refactor dai format implementation
>   ASoC: amd: acp: Add tdm support in machine driver
>   ASoC: amd: acp: Enable tdm support for skyrim platforms
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/5] ASoC: amd: acp: Refactor i2s bclk calculation
      (no commit info)
[2/5] ASoC: amd: acp: Add new cpu dai's in machine driver
      commit: 099b923fc15d8faa91c5fc1b46cbc483d034f5dc
[3/5] ASoC: amd: acp: Refactor dai format implementation
      commit: af830fc44a2d273b163e76b17f51b128ce694481
[4/5] ASoC: amd: acp: Add tdm support in machine driver
      (no commit info)
[5/5] ASoC: amd: acp: Enable tdm support for skyrim platforms
      (no commit info)

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