From:   Vignesh Raghavendra <vigneshr@ti.com>
To:     Aswath Govindraju <a-govindraju@ti.com>
CC:     Vignesh Raghavendra <vigneshr@ti.com>,
        <linux-arm-kernel@lists.infradead.org>,
        Rob Herring <robh+dt@kernel.org>,
        <linux-kernel@vger.kernel.org>,
        Kishon Vijay Abraham I <kishon@ti.com>,
        Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
        <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] J721S2: Add initial support
Date:   Wed, 15 Dec 2021 14:08:04 +0530
Message-ID: <163955230562.15251.10921015972649910083.b4-ty@ti.com>
In-Reply-To: <20211207080904.14324-1-a-govindraju@ti.com>
References: <20211207080904.14324-1-a-govindraju@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi Aswath Govindraju,
 
On Tue, 7 Dec 2021 13:38:59 +0530, Aswath Govindraju wrote:
> The J721S2 SoC belongs to the K3 Multicore SoC architecture platform,
> providing advanced system integration in automotive ADAS applications and
> industrial applications requiring AI at the network edge. This SoC extends
> the Jacinto 7 family of SoCs with focus on lowering system costs and power
> while providing interfaces, memory architecture and compute performance for
> single and multi-sensor applications.
> 
> [...]
 
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
 
[1/5] dt-bindings: arm: ti: Add bindings for J721s2 SoC
      commit: 6b1caf4dea3e0a961b7a11cff6757ff74c1c34ea
[2/5] dt-bindings: pinctrl: k3: Introduce pinmux definitions for J721S2
      commit: beba81faad86fc2bad567b1c029d6a000a43ca78
[3/5] arm64: dts: ti: Add initial support for J721S2 SoC
      commit: b8545f9d3a5426a5f76814c8aaebc5cb46a3213a
[4/5] arm64: dts: ti: Add initial support for J721S2 System on Module
      commit: d502f852d22af1ca33e7a2fedd7426831f6dbaef
[5/5] arch: arm64: ti: Add support J721S2 Common Processor Board
      commit: effb32e931dd4feb8aa3cee7b5b4ddda43c8b701
 
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