linux-kernel - Re: [PATCH] ASoC: codecs: lpass: Drop unused AIF

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <174947640900.126747.17690897321632994593.b4-ty@kernel.org>
Date: Mon, 09 Jun 2025 14:40:09 +0100
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srini@...nel.org>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, linux-sound@...r.kernel.org, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH] ASoC: codecs: lpass: Drop unused AIF_INVALID first DAI
 identifier

On Fri, 23 May 2025 14:18:12 +0200, Krzysztof Kozlowski wrote:
> All four Qualcomm SoC macro codecs define DAI IDs in an enum starting
> with AIF_INVALID=0, which is nowhere used in the code thus actual DAI
> IDs start from 1.  Drivers do not have their own of_xlate_dai_name(),
> thus snd_soc_get_dlc() expects the DTS to start numbering DAIs from 0,
> which creates confusing debugging scenario, e.g. DTS should use
> <&lpass_wsamacro 2> for WSA_MACRO_AIF_VI with dai->id=3.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: codecs: lpass: Drop unused AIF_INVALID first DAI identifier
      commit: bb4a0f497bc19558ba7fe9feac814286fc7ebe85

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