linux-kernel - Re: [PATCH] ASoC: meson: axg: extend TDM maximum sample rate to 384kHz

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: <169447666857.2387538.11157727345218045709.b4-ty@kernel.org>
Date:   Tue, 12 Sep 2023 00:57:48 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Jerome Brunet <jbrunet@...libre.com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        linux-amlogic@...ts.infradead.org
Subject: Re: [PATCH] ASoC: meson: axg: extend TDM maximum sample rate to
 384kHz

On Thu, 07 Sep 2023 11:09:10 +0200, Jerome Brunet wrote:
> The TDM HW on the axg SoC families and derivatives actually supports
> 384kHz sampling rate.
> 
> Update the fifo and tdm interface constraints accordingly.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: meson: axg: extend TDM maximum sample rate to 384kHz
      commit: 43f2d432e47ebf2d7518fdef50d7cc70da376b0e

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