linux-kernel - Re: [PATCH] ASoC: dmaengine_pcm: Add port_window

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: <175499672288.16031.6836246064105850327.b4-ty@kernel.org>
Date: Tue, 12 Aug 2025 12:05:22 +0100
From: Mark Brown <broonie@...nel.org>
To: lars@...afoo.de, perex@...ex.cz, tiwai@...e.com, lgirdwood@...il.com, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Chancel Liu <chancel.liu@....com>
Subject: Re: [PATCH] ASoC: dmaengine_pcm: Add port_window_size to DAI dma
 data struct

On Fri, 08 Aug 2025 15:17:41 +0900, Chancel Liu wrote:
> The port_window_size is a struct member of dma slave channel runtime
> config. It's the length of the register area in words the data need to
> be accessed on the device side. It is only used for devices which is
> using an area instead of a single register to send or receive the data.
> Typically the DMA loops in this area in order to transfer the data.
> 
> It's useful for cases that reading/writing multiple registers in DMA
> transactions.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: dmaengine_pcm: Add port_window_size to DAI dma data struct
      commit: 32dffd4c3e3129e3d9bb378af8d80bb57dc3038b

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