Message ID | 20220629102304.65712-1-chanho61.park@samsung.com (mailing list archive) |
---|---|
Headers | show |
Series | spi support for Exynos Auto v9 SoC | expand |
On Wed, 29 Jun 2022 19:23:00 +0900, Chanho Park wrote: > Add to support Exynos Auto v9 SoC's spi. By supporting USI(Universal > Serial Interface) mode, the SoC can support up to 12 spi ports. Thus, we > need to increase MAX_SPI_PORTS from 6 to 12. The spi of the SoC can > support loopback mode unlike previous exynos SoCs. To separate the > feature, we need to add .has_loopback to the s3c64xx_spi_port_config. > Furthermore, it uses 4 as the default internal clock divider. We also > need to clk_div field of the structure and assign "2" as the default > value to the existing SoC's port config. > Device tree definitions of exynosautov9-spi will be added in separated > patchset to include usi(i2c/uart/spi) nodes all together. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/4] spi: s3c64xx: support loopback mode commit: ffb7bcd3b27e86fa7bdbabf4488060064ec9d00d [2/4] spi: s3c64xx: support custom value of internal clock divider commit: bfcd27dcb7b93bd1f3b89d03d8b90207876d635f [3/4] dt-bindings: samsung,spi: define exynosautov9 compatible commit: 9dbeef8ad5f8e7d2cab7b888853b4abe9db87ffd [4/4] spi: s3c64xx: add spi port configuration for Exynos Auto v9 SoC commit: 11d50d853dceb2df8d28bf772d3e928c1c5b137a 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