linux-kernel - Re: [PATCH] firmware: cs_dsp: Remove redundant download buffer allocator

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: <176418436134.117076.16200821055578141148.b4-ty@kernel.org>
Date: Wed, 26 Nov 2025 19:12:41 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH] firmware: cs_dsp: Remove redundant download buffer
 allocator

On Wed, 26 Nov 2025 13:15:01 +0000, Richard Fitzgerald wrote:
> Now that cs_dsp uses regmap_raw_write() instead of regmap_raw_write_async()
> it doesn't need to keep multiple DMA-safe buffers of every chunk of data
> it wrote.
> 
> See commit fe08b7d5085a ("firmware: cs_dsp: Remove async regmap writes")
> 
> Only one write can be in progress at a time, so one DMA-safe buffer can be
> re-used. The single DMA-safe buffer is reallocated if the next write chunk
> is larger. Reallocation size is rounded up to reduce the amount of churn.
> PAGE_SIZE is used as a convenient size multiple. Typically for .wmfw files
> the first chunk is the largest.
> 
> [...]

Applied to

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

Thanks!

[1/1] firmware: cs_dsp: Remove redundant download buffer allocator
      commit: 900baa6e7bb08ab3d24388cf945c7be063ac1b89

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