linux-kernel - Re: [PATCH 1/5] spi-geni-qcom: remove manual CS control

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: <176580716950.161463.18012619677965135620.b4-ty@kernel.org>
Date: Mon, 15 Dec 2025 22:59:29 +0900
From: Mark Brown <broonie@...nel.org>
To: linux-arm-msm@...r.kernel.org, Jonathan Marek <jonathan@...ek.ca>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/5] spi-geni-qcom: remove manual CS control

On Thu, 20 Nov 2025 16:11:58 -0500, Jonathan Marek wrote:
> The GPI_DMA mode already uses automatic CS control, to use automatic CS
> control for non-GPI case all that's needed is to set the FRAGMENTATION flag
> using the same logic as setup_gsi_xfer(). (note clearing SPI_TRANS_CFG's
> CS_TOGGLE bit enables automatic CS control, the comment was wrong)
> 
> spi_geni_set_cs() is slow, so this is a big performance improvement.
> 
> [...]

Applied to

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

Thanks!

[1/5] spi-geni-qcom: remove manual CS control
      commit: b99181cdf9fa0247dda3ba1228b4578286ab7ecd
[2/5] spi-geni-qcom: don't set max clock in setup_fifo_params
      commit: 7ba2e0edb18b3ccee7339315be47080832a3c355
[3/5] spi-geni-qcom: use xfer->bits_per_word for can_dma()
      commit: fb2bbe3838728f572485706677590e4fc41eec5c
[4/5] spi-geni-qcom: initialize mode related registers to 0
      commit: 739062a9f1e9a77a9687c8fd30f8e5dd12ec70be
[5/5] spi-geni-qcom: rework setup_fifo_params
      commit: 781c3e71c94c80e1b33a7d84b970907dd32abc10

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