linux-kernel - Re: [PATCH 0/4] Add function to constrain rates

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: <173383775650.46965.9428255940556546352.b4-ty@kernel.org>
Date: Tue, 10 Dec 2024 13:35:56 +0000
From: Mark Brown <broonie@...nel.org>
To: shengjiu.wang@...il.com, Xiubo.Lee@...il.com, festevam@...il.com, 
 nicoleotsuka@...il.com, lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org, 
 linux-sound@...r.kernel.org, Chancel Liu <chancel.liu@....com>
Subject: Re: [PATCH 0/4] Add function to constrain rates

On Tue, 26 Nov 2024 20:54:36 +0900, Chancel Liu wrote:
> Platforms like i.MX93/91 only have one audio PLL. Some sample rates are
> not supported. If the PLL source is used for 8kHz series rates, then
> 11kHz series rates can't be supported. Add common function to constrain
> rates according to different clock sources.
> 
> In ASoC drivers switch to this new function.
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: fsl_utils: Add function to constrain rates
      commit: 820bcaeb1ff5705ba907563e554f17d0deecc3fa
[2/4] ASoC: fsl_micfil: Switch to common sample rate constraint function
      commit: daf7a173fc7c4b652f3fe69d3b5aa520976a7d63
[3/4] ASoC: fsl_xcvr: Add sample rate constraint
      commit: b622b677d255b41cbfce20b66535723933a6b640
[4/4] ASoC: fsl_sai: Add sample rate constraint
      commit: 4edc98598be43634f87af5d3876ebec6c274d2cb

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