linux-kernel - Re: [PATCH 0/2] SPI: omap2-mcspi: Fix SPI CS behaviour around cs

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: <174949762925.256775.674413382110648047.b4-ty@kernel.org>
Date: Mon, 09 Jun 2025 20:33:49 +0100
From: Mark Brown <broonie@...nel.org>
To: Louis Chauvet <louis.chauvet@...tlin.com>, 
 Félix Piédallu <felix.piedallu@....se.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 pascal.eberhard@...com
Subject: Re: [PATCH 0/2] SPI: omap2-mcspi: Fix SPI CS behaviour around
 cs_change in SPI transfers

On Fri, 06 Jun 2025 15:37:23 +0200, Félix Piédallu wrote:
> These patches fix the behaviour of the SPI Chip Select of the OMAP2 MCSPI
> driver used on TI SoCs.
> 
> The omap2-mcspi driver supports the use of multi mode (multichannel in TI
> documentation). In this mode, the CS is asserted and deasserted by the
> hardware.
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: omap2-mcspi: Disable multi mode when CS should be kept asserted after message
      commit: a5bf5272295d3f058adeee025d2a0b6625f8ba7b
[2/2] spi: omap2-mcspi: Disable multi-mode when the previous message kept CS asserted
      commit: 10c24e0d2f7cd2bc8a847cf750f01301ce67dbc8

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