[PATCH 0/3] spi: spi-nxp-fspi: few fix for flexspi

Haibo Chen posted 3 patches 4 months, 2 weeks ago
drivers/spi/spi-nxp-fspi.c | 32 +++++++++++++++++++++++++++-----
1 file changed, 27 insertions(+), 5 deletions(-)
[PATCH 0/3] spi: spi-nxp-fspi: few fix for flexspi
Posted by Haibo Chen 4 months, 2 weeks ago
PATCH 1: different operations maybe require different max frequency, so
         add flexspi to handle such case, re-config the clock rate when
	 new coming operation require new clock frequency.
Patch 2: add workaround for erratum ERR050272. Since only add 4us dealy
	 in nxp_fspi_dll_calibration(), so do not distinguish different
	 platforms.
Patch 3: add max frequency limitation for different sample clock source
         selection. Datasheet give max 66MHz for mode 0 and 166MHz for 
	 mode 3. And IC suggest to add this limitation on all SoCs for
	 safety and stability.

Signed-off-by: Haibo Chen <haibo.chen@nxp.com>
---
Haibo Chen (2):
      spi: spi-nxp-fspi: re-config the clock rate when operation require new clock rate
      spi: spi-nxp-fspi: limit the clock rate for different sample clock source selection

Han Xu (1):
      spi: spi-nxp-fspi: add extra delay after dll locked

 drivers/spi/spi-nxp-fspi.c | 32 +++++++++++++++++++++++++++-----
 1 file changed, 27 insertions(+), 5 deletions(-)
---
base-commit: 12c28f647e5eefd08796c7b161acc9c46bd7057a
change-id: 20250922-fspi-fix-14d4e071df7d

Best regards,
-- 
Haibo Chen <haibo.chen@nxp.com>
Re: [PATCH 0/3] spi: spi-nxp-fspi: few fix for flexspi
Posted by Mark Brown 3 months, 3 weeks ago
On Mon, 22 Sep 2025 16:47:12 +0800, Haibo Chen wrote:
> PATCH 1: different operations maybe require different max frequency, so
>          add flexspi to handle such case, re-config the clock rate when
> 	 new coming operation require new clock frequency.
> Patch 2: add workaround for erratum ERR050272. Since only add 4us dealy
> 	 in nxp_fspi_dll_calibration(), so do not distinguish different
> 	 platforms.
> Patch 3: add max frequency limitation for different sample clock source
>          selection. Datasheet give max 66MHz for mode 0 and 166MHz for
> 	 mode 3. And IC suggest to add this limitation on all SoCs for
> 	 safety and stability.
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: spi-nxp-fspi: re-config the clock rate when operation require new clock rate
      commit: a89103f67112453fa36c9513e951c19eed9d2d92
[2/3] spi: spi-nxp-fspi: add extra delay after dll locked
      commit: b93b4269791fdebbac2a9ad26f324dc2abb9e60f
[3/3] spi: spi-nxp-fspi: limit the clock rate for different sample clock source selection
      commit: f43579ef3500527649b1c233be7cf633806353aa

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