linux-kernel - Re: [PATCH v1] ASoC: qcom: lpass-platform: Use SNDRV_DMA_TYPE

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: <167469294198.2696228.16654878670798627815.b4-ty@kernel.org>
Date:   Thu, 26 Jan 2023 00:29:01 +0000
From:   Mark Brown <broonie@...nel.org>
To:     srinivas.kandagatla@...aro.org, bgoswami@...eaurora.org,
        lgirdwood@...il.com, Judy Hsiao <judyhsiao@...omium.org>
Cc:     alsa-devel@...a-project.org, tiwai@...e.com,
        linux-kernel@...r.kernel.org,
        Banajit Goswami <bgoswami@...cinc.com>,
        Jaroslav Kysela <perex@...ex.cz>
Subject: Re: [PATCH v1] ASoC: qcom: lpass-platform: Use
 SNDRV_DMA_TYPE_NONCOHERENT page allocation

On Thu, 08 Dec 2022 08:42:00 +0000, Judy Hsiao wrote:
> Replace SNDRV_DMA_TYPE_DEV by SNDRV_DMA_TYPE_NONCOHERENT for pcm
> buffer allocation. We measured about 18x performance improvement
> when accessing the snd_pcm_mmap() buffer from userspace.
> 
> Eg: aarch64 with internal speaker
> ==
> SNDRV_DMA_TYPE_DEV
>     frames_per_second=66.4557M/s
>     max_time_per_4096_frames=106.094u
>     time_per_4096_frames=61.6351us
> 
> [...]

Applied to

   broonie/sound.git for-next

Thanks!

[1/1] ASoC: qcom: lpass-platform: Use SNDRV_DMA_TYPE_NONCOHERENT page allocation
      commit: 01270f905eea786f418cbc2040f7a52b969ef377

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