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

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: <176055663624.243729.1614334756010588411.b4-ty@kernel.org>
Date: Wed, 15 Oct 2025 20:30:36 +0100
From: Mark Brown <broonie@...nel.org>
To: Han Xu <han.xu@....com>, Yogesh Gaur <yogeshgaur.83@...il.com>, 
 Miquel Raynal <miquel.raynal@...tlin.com>, Frank Li <Frank.Li@....com>, 
 Haibo Chen <haibo.chen@....com>
Cc: linux-spi@...r.kernel.org, imx@...ts.linux.dev, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] spi: spi-nxp-fspi: few fix for flexspi

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