linux-kernel - Re: [PATCH] ASoC: meson: axg-iface: set continuous 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: <172773159468.2197048.15947948691093286494.b4-ty@kernel.org>
Date: Mon, 30 Sep 2024 22:26:34 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Neil Armstrong <neil.armstrong@...aro.org>, 
 Kevin Hilman <khilman@...libre.com>, 
 Martin Blumenstingl <martin.blumenstingl@...glemail.com>, 
 Jerome Brunet <jbrunet@...libre.com>
Cc: alsa-devel@...a-project.org, linux-sound@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, linux-amlogic@...ts.infradead.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: meson: axg-iface: set continuous rates

On Fri, 20 Sep 2024 19:22:05 +0200, Jerome Brunet wrote:
> The axg TDM HW does not depend on a selected set of rates.
> The hardware itself, just takes an input clock and work with it, regardless
> of its rate. In this way, the rates TDM can take are continuous.
> 
> What might force the use of specific rate are the PLL available as clock
> and/or the codecs facing the TDM HW. Either way, this constraint does not
> belong in the TDM interface driver.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: meson: axg-iface: set continuous rates
      commit: 3a02cc576accdccb22ffd2d6ac1f9788c7b4c7ce

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