linux-kernel - Re: [PATCH] ASoC: soc-utils: allow sample rate up to 768kHz for the dummy dai

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: <171959441829.130075.12252644545432851916.b4-ty@kernel.org>
Date: Fri, 28 Jun 2024 18:06:58 +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
Subject: Re: [PATCH] ASoC: soc-utils: allow sample rate up to 768kHz for
 the dummy dai

On Fri, 28 Jun 2024 14:01:29 +0200, Jerome Brunet wrote:
> The dummy DAI should allow any (reasonable) rates possible.
> Make the rate continuous for dummy and set range from 5512Hz to 768kHz
> 
> The change is mostly cosmetic as dummy is skipped when setting
> the hwparams.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: soc-utils: allow sample rate up to 768kHz for the dummy dai
      commit: 4adf454ff62883ee64b0b9818b951f34aa078d5a

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