Re: [PATCH v9 00/10] ASoC: qcom: Add QAIF driver for Shikra audio platform

[Mark Brown]

On Tue, 13 Oct 2026 11:21:23 +0530, Harendra Gautam wrote:
> ASoC: qcom: Add QAIF driver for Shikra audio platform
> 
> This series introduces the Qualcomm Audio Interface (QAIF) driver for
> the Shikra audio platform.
> 
> Hardware IP Overview
> ====================
> QAIF (Qualcomm Audio Interface) is a fully configurable DMA-based audio
> subsystem used to transmit and receive audio data over serial audio
> interfaces (PCM, TDM, MI2S) and to provide a DMA interface for internal
> codec connections. It manages two independent data paths:
> 
> [...]

Applied to

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

Thanks!

[01/10] ASoC: dt-bindings: qcom,shikra-qaif-cpu: Add binding
        https://git.kernel.org/broonie/sound/c/f7b6fe0a9bd3
[02/10] ASoC: qcom: Add QAIF shared data structures and variant interface
        https://git.kernel.org/broonie/sound/c/6a07ff8dd304
[03/10] ASoC: qcom: Add QAIF hardware register map
        https://git.kernel.org/broonie/sound/c/6a0d1c361ec5
[04/10] ASoC: qcom: Add QAIF CPU DAI ops, regmap, DT parsing and platform init
        https://git.kernel.org/broonie/sound/c/dd77abdd3496
[05/10] ASoC: soc-core: Add snd_soc_of_xlate_dai_name() generic helper
        https://git.kernel.org/broonie/sound/c/02298cc296e6
[06/10] ASoC: qcom: Switch lpass-cpu and qaif-cpu to snd_soc_of_xlate_dai_name()
        https://git.kernel.org/broonie/sound/c/76c5ecd4cafe
[07/10] ASoC: qcom: Add QAIF PCM operations
        https://git.kernel.org/broonie/sound/c/6381a4f9c633
[08/10] ASoC: qcom: Add QAIF IRQ handling and platform register
        https://git.kernel.org/broonie/sound/c/abe10d275660
[09/10] ASoC: qcom: Add Shikra QAIF support
        https://git.kernel.org/broonie/sound/c/871b3a7574f9
[10/10] MAINTAINERS: Add Qualcomm QAIF driver entry
        https://git.kernel.org/broonie/sound/c/9a810aa9f105

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