Re: [PATCH v6 0/2] add support for Cadence's XSPI controller

From: Mark Brown
Date: Mon Sep 27 2021 - 13:47:06 EST


On Sun, 19 Sep 2021 10:04:28 +0200, Parshuram Thombare wrote:
> This patch series adds support for Cadence's XSPI controller.
> It supports 3 work modes.
> 1. ACMD (auto command) work mode
> ACMD name is because it uses auto command engine in the controller.
> It further has 2 modes PIO and CDMA (command DMA).
> The CDMA work mode is dedicated for high-performance application
> where very low software overhead is required. In this mode the
> Command Engine is programmed by the series of linked descriptors
> stored in system memory. These descriptors provide commands to execute
> and store status information for finished commands.
> The PIO mode work mode is dedicated for single operation where
> constructing a linked list of descriptors would require too
> much effort.
> 2. STIG (Software Triggered Instruction Generator) work mode
> In STIG mode, controller sends low-level instructions to memory.
> Each instruction is 128-bit width. There is special instruction
> DataSequence which carries information about data phase.
> Driver uses Slave DMA interface to transfer data as only this
> interface can be used in STIG work mode.
> 3. Direct work mode
> This work mode allows sending data without invoking any command through
> the slave interface.
> Currently only STIG work mode is enabled, remaining work modes will
> be added later.
>
> [...]

Applied to

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

Thanks!

[1/2] spi: cadence: add dt-bindings documentation for Cadence XSPI controller
commit: 1f01818b410ac05344c38f65e5ae135e034d47ce
[2/2] spi: cadence: add support for Cadence XSPI controller
commit: a16cc807762730a6291762d4bedd7b00624a6426

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