linux-kernel - Re: [PATCH v5] spi: imx: fix the burst length at DMA mode and CPU mode

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: <170715522367.847267.14071106009498726230.b4-ty@kernel.org>
Date: Mon, 05 Feb 2024 17:47:03 +0000
From: Mark Brown <broonie@...nel.org>
To: shawnguo@...nel.org, s.hauer@...gutronix.de, kernel@...gutronix.de, 
 linux-imx@....com, benjamin@...ler.one, stefanmoring@...il.com, 
 carlos.song@....com
Cc: linux-spi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5] spi: imx: fix the burst length at DMA mode and CPU
 mode

On Sun, 04 Feb 2024 17:19:12 +0800, carlos.song@....com wrote:
> For DMA mode, the bus width of the DMA is equal to the size of data
> word, so burst length should be configured as bits per word.
> 
> For CPU mode, because of the spi transfer len is in byte, so calculate
> the total number of words according to spi transfer len and bits per
> word, burst length should be configured as total data bits.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: imx: fix the burst length at DMA mode and CPU mode
      commit: c712c05e46c8ce550842951e9e2606e24dbf0475

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