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: <172554742664.49204.15446673448032504147.b4-ty@kernel.org>
Date: Thu, 05 Sep 2024 15:43:46 +0100
From: Mark Brown <broonie@...nel.org>
To: claudiu.beznea@...on.dev, lgirdwood@...il.com, perex@...ex.cz, 
 tiwai@...e.com, nicolas.ferre@...rochip.com, alexandre.belloni@...tlin.com, 
 Andrei Simion <andrei.simion@...rochip.com>
Cc: alsa-devel@...a-project.org, linux-sound@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
 Codrin Ciubotariu <codrin.ciubotariu@...rochip.com>
Subject: Re: [PATCH] ASoC: atmel: mchp-i2s-mcc: Improve maxburst
 calculation for better performance

On Thu, 05 Sep 2024 12:56:33 +0300, Andrei Simion wrote:
> The period size represents the size of the DMA descriptor. To ensure all
> DMA descriptors start from a well-aligned address, the period size must
> be divided by (sample size * maxburst), not just by maxburst.
> This adjustment allows for computing a higher maxburst value, thereby
> increasing the performance of the DMA transfer.
> Previously, snd_pcm_lib_period_bytes() returned 0 because the runtime HW
> parameters are computed after the hw_params() callbacks are used.
> To address this, we now use params_*() functions to compute the period
> size accurately. This change optimizes the DMA transfer performance by
> ensuring proper alignment and efficient use of maxburst values.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: atmel: mchp-i2s-mcc: Improve maxburst calculation for better performance
      commit: 03667e3d4fbcaf6228fd642464467366f0b693de

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ