linux-kernel - Re: [PATCH] spi: omap2-mcspi: drive SPI_CLK on transfer

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: <175861512446.967375.4560580577067542022.b4-ty@kernel.org>
Date: Tue, 23 Sep 2025 10:12:04 +0200
From: Mark Brown <broonie@...nel.org>
To: "Bastien Curutchet (Schneider Electric)" <bastien.curutchet@...tlin.com>
Cc: Thomas Petazzoni <thomas.petazzoni@...tlin.com>, 
 Miquèl Raynal <miquel.raynal@...tlin.com>, 
 Pascal Eberhard <pascal.eberhard@...com>, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: omap2-mcspi: drive SPI_CLK on transfer_setup()

On Fri, 12 Sep 2025 09:08:58 +0200, Bastien Curutchet (Schneider Electric) wrote:
> If the cached contents of the CHCONF register doesn't have the FORCE bit
> set, the setup() function failed to set the relevant idle state of the
> SPI_CLK pin. In such case, the SPI_CLK's idle state is reached later with
> set_cs(), but it's too late for the first SPI transfer which fails since
> the CS is asserted before the clock reaching its idle state.
> 
> Add a first write in setup() that always sets the FORCE bit.
> Keep the current write afterwards to ensure the FORCE bit won't stay in
> the cached contents of the CHCONF register unless it's intended.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: omap2-mcspi: drive SPI_CLK on transfer_setup()
      commit: 398a8a4e51dbd03e4103ea596ea4ea037fe67175

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