Hi Apurva Nandan, On Thu, 12 Jan 2023 19:57:21 +0530, Apurva Nandan wrote: > The J784S4 SoC belongs to the K3 Multicore SoC architecture > platform, providing advanced system integration in automotive, > ADAS and industrial applications requiring AI at the network edge. > This SoC extends the K3 Jacinto 7 family of SoCs with focus on > raising performance and integration while providing interfaces, > memory architecture and compute performance for multi-sensor, high > concurrency applications. > > [...] I have applied the following to branch ti-k3-next on [1]. Thank you! [1/4] dt-bindings: arm: ti: Add bindings for J784s4 SoC commit: 5e0a1e0d265cb11fca3464bbe9511740c46f759f [2/4] dt-bindings: pinctrl: k3: Introduce pinmux definitions for J784s4 commit: a0c01bc565332cff9183bd8a17b4db94732d645d [3/4] arm64: dts: ti: Add initial support for J784S4 SoC commit: 4664ebd8346adaa7530555a29b47392104b5ba6c [4/4] arm64: dts: ti: Add support for J784S4 EVM board commit: e20a06aca5c9d2d68354c340f96999d8dcb7128d All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant 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. [1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git -- Vignesh