Re: [PATCH v2 0/5] spi: spi-nxp-fspi: add DTR mode support

[Mark Brown <broonie@kernel.org>]

On Wed, 17 Sep 2025 15:27:05 +0800, Haibo Chen wrote:
> this patch set add DTR mode support for flexspi.
> For DTR mode, flexspi only support 8D-8D-8D mode.
> 
> Patch 1~2 extract nxp_fspi_dll_override(), prepare for adding the DTR mode.
>         in nor suspend, it will disable DTR mode, and enable DTR mode back
> 	in nor resume. this require the flexspi driver has the ability to
> 	set back to dll override mode in STR mode when clock rate < 100MHz.
> Patch 3 Add the DDR LUT command support. flexspi use LUT command to handle
> 	the dtr/str mode.
> Patch 4 add the logic of sample clock source selection for STR/DTR mode
> 	STR use the default mode 0, sample based on the internal dummy pad.
> 	DTR use the mode 3, sample based on the external DQS pad, so this
> 	board and device connect the DQS pad.
> 	adjust the clock rate for DTR mode, when detect the DDR LUT command,
> 	flexspi will automatically div 2 of the root clock and output to device.
> Patch 5 finally add the DTR support in default after the upper 4 patches's
> 	prepareation. Since lx2160a do not implement DQS pad, so can't support
> 	this DTR mode.
> 
> [...]

Applied to

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

Thanks!

[1/5] spi: spi-nxp-fspi: extract function nxp_fspi_dll_override()
      commit: 614180a54d5f21ccb4f60042d19744694d31d3f8
[2/5] spi: spi-nxp-fspi: set back to dll override mode when clock rate < 100MHz
      commit: a9888b3222ec73d055447a39cf9a0118f67497f4
[3/5] spi: spi-nxp-fspi: Add the DDR LUT command support
      commit: 3c1000e15fd0eb387fcca420c9fb36ae07887782
[4/5] spi: spi-nxp-fspi: add the support for sample data from DQS pad
      commit: c07f270323175b83779c2c2b80b360ed476baec5
[5/5] spi: spi-nxp-fspi: Add OCT-DTR mode support
      commit: 0f67557763accbdd56681f17ed5350735198c57b

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