Currently, cadence-xspi depends on 64BIT. This dependency isn't from
cadence xspi controller itself, but from marvell support code and 64bit
slave dma interface performance optimization.

This series tries to remove the 64BIT dependency.
patch1 is the preparation patch to move some code so we can group
marvell support code together. No functionality change.
patch2 and patch3 remove the two causes of 64BIT dependency.
patch4 finally removes the 64BIT Kconfig dependency.

Jisheng Zhang (4):
  spi: cadence-xspi: group marvell support code together
  spi: cadence-xspi: put marvell support code under CONFIG_64BIT
  spi: cadence-xspi: only use readsq/writesq under 64BIT
  spi: cadence-xspi: remove 64BIT Kconfig dependency

 drivers/spi/Kconfig            |   2 +-
 drivers/spi/spi-cadence-xspi.c | 475 +++++++++++++++++----------------
 2 files changed, 246 insertions(+), 231 deletions(-)

-- 
2.53.0

On Mon, 03 Aug 2026 22:07:24 +0800, Jisheng Zhang wrote:
> spi: cadence-xspi: remove 64BIT dependency
> 
> Currently, cadence-xspi depends on 64BIT. This dependency isn't from
> cadence xspi controller itself, but from marvell support code and 64bit
> slave dma interface performance optimization.
> 
> This series tries to remove the 64BIT dependency.
> patch1 is the preparation patch to move some code so we can group
> marvell support code together. No functionality change.
> patch2 and patch3 remove the two causes of 64BIT dependency.
> patch4 finally removes the 64BIT Kconfig dependency.
> 
> [...]

Applied to

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

Thanks!

[1/4] spi: cadence-xspi: group marvell support code together
      https://git.kernel.org/broonie/spi/c/94d031d26168
[2/4] spi: cadence-xspi: put marvell support code under CONFIG_64BIT
      https://git.kernel.org/broonie/spi/c/63371e187e9d
[3/4] spi: cadence-xspi: only use readsq/writesq under 64BIT
      https://git.kernel.org/broonie/spi/c/0ab32c1c2b6d
[4/4] spi: cadence-xspi: remove 64BIT Kconfig dependency
      https://git.kernel.org/broonie/spi/c/54a6b7fe101c

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