On Tue, 09 Jul 2024 15:12:02 -0700, Witold Sadowski wrote: > This patch series adds support for the second version of the Marvell > hardware overlay for the Cadence xSPI IP block. The overlay is a hardware > change made around the original xSPI block. It extends xSPI features with > clock configuration, interrupt masking, and full-duplex, variable-length SPI > operations. > > These functionalities allow the xSPI block to operate not only with memory > devices but also with simple SPI devices and TPM devices. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/9] spi: dt-bindings: cadence: Add Marvell overlay bindings documentation for Cadence XSPI commit: 49f63e6a89e94a757ef86340ec531668d26ecc30 [2/9] spi: cadence: Add static PHY configuration in Marvell overlay commit: b0d06169a7153f78b5356ca9e15cd836e43408dd [3/9] spi: cadence: Add clock configuration for Marvell xSPI overlay commit: 26d34fdc49712ddbd42b11102f5d9d78a0f42097 [4/9] spi: cadence: Add Marvell SDMA operations commit: 75128e2a14a9f443e8debdd30445f5934b5a7c83 [5/9] spi: cadence: Add Marvell xSPI interrupt changes commit: fa7279acef673f17550202d662f592672be26247 [6/9] spi: cadence: Add Marvell xfer operation support commit: 931e389ded0f1411cbf07ad50074dc2bcd49e1a8 [7/9] spi: cadence: Change resource mapping commit: 4b8cb7dcd8acd7a05354f0b458aca02e4497f2a6 [8/9] spi: cadence: Change cs property reading. commit: 8232f1e2584ac1eadd3282b035c306ebde87d8b4 [9/9] spi: cadence: Try to read spi-tx/rx-bus width property using ACPI commit: 9cabf4a487cd4035844b4928881a314334f348fe 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
