public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] ASoC fixes for v6.11-merge-window
Date: Thu, 25 Jul 2024 16:54:44 +0100	[thread overview]
Message-ID: <5a2e9c948bd527794d6e05160e201744.broonie@kernel.org> (raw)

The following changes since commit c51cba4755609ad97ba97713210c16f043c73224:

  Fix the unbalanced pm_runtime_enable in wcd937x-sdw (2024-07-12 17:38:18 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v6.11-merge-window

for you to fetch changes up to ab53dfdcdd1ec8df8729890aefa5b0e3c900afbb:

  ASoC: fsl-asoc-card: Dynamically allocate memory for snd_soc_dai_link_components (2024-07-25 14:20:30 +0100)

----------------------------------------------------------------
ASoC: Fixes for v6.11

A selection of routine fixes and quirks that came in since the merge
window.  The fsl-asoc-card change is a fix for systems with multiple
cards where updating templates in place leaks data from one card to
another.

----------------------------------------------------------------
Arnd Bergmann (1):
      ASoC: tegra: select CONFIG_SND_SIMPLE_CARD_UTILS

Curtis Malainey (1):
      ASoC: Intel: Fix RT5650 SSP lookup

Dan Carpenter (1):
      ASoC: TAS2781: Fix tasdev_load_calibrated_data()

Daniel Baluta (1):
      ASoC: SOF: imx8m: Fix DSP control regmap retrieval

Peter Ujfalusi (2):
      ASoC: SOF: ipc4-topology: Only handle dai_config with HW_PARAMS for ChainDMA
      ASoC: SOF: ipc4-topology: Preserve the DMA Link ID for ChainDMA on unprepare

Pierre-Louis Bossart (2):
      ASOC: SOF: Intel: hda-loader: only wait for HDaudio IOC for IPC4 devices
      ASoC: Intel: use soc_intel_is_byt_cr() only when IOSF_MBI is reachable

Shengjiu Wang (1):
      ASoC: fsl-asoc-card: Dynamically allocate memory for snd_soc_dai_link_components

Takashi Iwai (1):
      ASoC: amd: yc: Support mic on Lenovo Thinkpad E16 Gen 2

Venkata Prasad Potturu (1):
      ASoC: sof: amd: fix for firmware reload failure in Vangogh platform

 sound/soc/amd/yc/acp6x-mach.c                      |  7 ++++
 sound/soc/codecs/tas2781-fmwlib.c                  |  2 +-
 sound/soc/fsl/fsl-asoc-card.c                      | 46 ++++++++++++++--------
 sound/soc/intel/common/soc-acpi-intel-ssp-common.c |  9 +++++
 sound/soc/intel/common/soc-intel-quirks.h          |  2 +-
 sound/soc/sof/amd/pci-vangogh.c                    |  1 -
 sound/soc/sof/imx/imx8m.c                          |  2 +-
 sound/soc/sof/intel/hda-loader.c                   | 20 ++++++----
 sound/soc/sof/intel/hda.c                          | 17 ++++----
 sound/soc/sof/ipc4-topology.c                      | 18 +++++++--
 sound/soc/tegra/Kconfig                            |  1 +
 11 files changed, 85 insertions(+), 40 deletions(-)

             reply	other threads:[~2024-07-25 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 15:54 Mark Brown [this message]
2024-07-25 16:05 ` [GIT PULL] ASoC fixes for v6.11-merge-window Takashi Iwai

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=5a2e9c948bd527794d6e05160e201744.broonie@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=tiwai@suse.de \
    /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