Message ID | 20200914162231.2535-1-lokeshvutla@ti.com (mailing list archive) |
---|---|
Headers | show |
Series | arm64: Initial support for Texas Instrument's J7200 Platform | expand |
On 21:52-20200914, Lokesh Vutla wrote: > This series adds initial support for latest new SoC, J7200, from Texas Instruments. > [..] > > Lokesh Vutla (5): > arm64: dts: ti: Makefile: Use ARCH_K3 for building dtbs > dt-bindings: arm: ti: Convert K3 board/soc bindings to DT schema > dt-bindings: arm: ti: Add bindings for J7200 SoC > arm64: dts: ti: Add support for J7200 SoC > arm64: dts: ti: Add support for J7200 Common Processor Board > > .../devicetree/bindings/arm/ti/k3.txt | 26 -- > .../devicetree/bindings/arm/ti/k3.yaml | 35 +++ > Series looks fine to me at least.. but the binding changes, will be great if DT maintainers could review it.
On Mon, 14 Sep 2020 21:52:26 +0530, Lokesh Vutla wrote: > This series adds initial support for latest new SoC, J7200, from Texas Instruments. > > The J7200 SoC is a part of the K3 Multicore SoC architecture platform. > It is targeted for for automotive gateway, vehicle compute systems, > Vehicle-to-Vehicle (V2V) and Vehicle-to-Everything (V2X) applications. > The SoC aims to meet the complex processing needs of modern embedded products. > > [...] Hi Lokesh Vutla, I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [1/5] arm64: dts: ti: Makefile: Use ARCH_K3 for building dtbs commit: 21bb8c83c94923f1f996e1cb57c4744ea1163eed [2/5] dt-bindings: arm: ti: Convert K3 board/soc bindings to DT schema commit: 66e06509aa37bcf089ce341ec9c027922f105155 [3/5] dt-bindings: arm: ti: Add bindings for J7200 SoC commit: 214b0eb35e55d9d726ad02ffec62f087c09864fb [4/5] arm64: dts: ti: Add support for J7200 SoC commit: d361ed88455feae5f7e555828b0d8104588cc53d [5/5] arm64: dts: ti: Add support for J7200 Common Processor Board commit: 26bd3f312c2ece0e8860c80fc64a112df5a620c6 NOTE: I have edited the patch to address the trivial comment 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] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git