linux-kernel - Re: [PATCH] spi: spi-cadence: enable SPI_CONTROLLER_MUST

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: <176850252392.1337956.14416489658978740904.b4-ty@kernel.org>
Date: Thu, 15 Jan 2026 18:42:03 +0000
From: Mark Brown <broonie@...nel.org>
To: peter.chen@...tech.com, fugang.duan@...tech.com, 
 Jun Guo <jun.guo@...tech.com>
Cc: 455.rodrigo.alencar@...il.com, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: spi-cadence: enable SPI_CONTROLLER_MUST_TX

On Thu, 15 Jan 2026 17:19:24 +0800, Jun Guo wrote:
> During an SPI read operation, even if the xspi->txbuf passed to the
> cdns_spi_writerinterface is empty, it is still necessary to call
> cdns_spi_write(xspi, CDNS_SPI_TXD, txw); otherwise, the read operation
> will fail to obtain data correctly due to a lack of clocks.
> 
> 

Applied to

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

Thanks!

[1/1] spi: spi-cadence: enable SPI_CONTROLLER_MUST_TX
      commit: f6b625639e39bc384a7bddbf134a698d40258b3b

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