Message ID | 20240918082744.379610-1-ada@thorsis.com (mailing list archive) |
---|---|
Headers | show |
Series | spi: atmel-quadspi: Fix and add full CS delay support | expand |
On Wed, 18 Sep 2024 10:27:42 +0200, Alexander Dahl wrote: > when testing on a SAM9X60 based board with an FPGA implementing a custom > SPI-MEM protocol, we found the need to fully control the delay settings > the atmel/microchip QSPI controller offers. > > Greets > Alex > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/2] spi: atmel-quadspi: Avoid overwriting delay register settings commit: 329ca3eed4a9a161515a8714be6ba182321385c7 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
On Wed, 18 Sep 2024 10:27:42 +0200, Alexander Dahl wrote: > when testing on a SAM9X60 based board with an FPGA implementing a custom > SPI-MEM protocol, we found the need to fully control the delay settings > the atmel/microchip QSPI controller offers. > > Greets > Alex > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [2/2] spi: atmel-quadspi: Add cs_hold and cs_inactive setting support commit: 625de1881b5aee6a42a3130004e47dbd632429f8 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