linux-kernel - Re: [PATCH] ASoC: tegra: Add support for S24

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: <172962586959.134224.13443393819264797768.b4-ty@kernel.org>
Date: Tue, 22 Oct 2024 20:37:49 +0100
From: Mark Brown <broonie@...nel.org>
To: perex@...ex.cz, tiwai@...e.com, linux-sound@...r.kernel.org, 
 "Sheetal ." <sheetal@...dia.com>
Cc: linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org, 
 lgirdwood@...il.com, jonathanh@...dia.com, thierry.reding@...il.com, 
 mkumard@...dia.com, spujar@...dia.com, Ritu Chaudhary <rituc@...dia.com>
Subject: Re: [PATCH] ASoC: tegra: Add support for S24_LE audio format

On Tue, 22 Oct 2024 04:13:30 +0000, Sheetal . wrote:
> Add support for S24_LE format for all internal and IO AHUB
> modules, except for ASRC (which is already supported).
> 
> The data flow happens as mentioned below:
> 
> - ADMAIF picks 24-bit valid data and converts it to 32-bit before
>   sending to internal AHUB modules. This makes the driver change
>   simpler for internal AHUB modules.
> - IO modules CIF converts the 32-bit data to 24-bit before sending it
>   to the external world.
> - To maintain consistency across modules, conversions between 24-bit
>   and 32-bit occur either at ADMAIF or at the IO modules CIF.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tegra: Add support for S24_LE audio format
      commit: 4204eccc7b2a4fb372ea6bafc80a765c98657a99

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