devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vignesh R <vigneshr@ti.com>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: <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: Thu, 23 Dec 2021 14:24:53 +0530	[thread overview]
Message-ID: <20211223085453.GD7862@uda0132425> (raw)
In-Reply-To: <163955230562.15251.10921015972649910083.b4-ty@ti.com>

[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]

On Wed, Dec 15, 2021 at 02:08:04PM +0530, Vignesh Raghavendra wrote:
> 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
>  

Dropped in favour of v4

-- 
Regards
Vignesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2021-12-23  8:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07  8:08 [PATCH v3 0/5] J721S2: Add initial support Aswath Govindraju
2021-12-07  8:09 ` [PATCH v3 1/5] dt-bindings: arm: ti: Add bindings for J721s2 SoC Aswath Govindraju
2021-12-07  8:09 ` [PATCH v3 2/5] dt-bindings: pinctrl: k3: Introduce pinmux definitions for J721S2 Aswath Govindraju
2021-12-07  8:09 ` [PATCH v3 3/5] arm64: dts: ti: Add initial support for J721S2 SoC Aswath Govindraju
2021-12-07  8:09 ` [PATCH v3 4/5] arm64: dts: ti: Add initial support for J721S2 System on Module Aswath Govindraju
2021-12-07  8:09 ` [PATCH v3 5/5] arch: arm64: ti: Add support J721S2 Common Processor Board Aswath Govindraju
2021-12-07  8:24 ` [PATCH v3 0/5] J721S2: Add initial support Kishon Vijay Abraham I
2021-12-15  8:38 ` Vignesh Raghavendra
2021-12-23  8:54   ` Vignesh R [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211223085453.GD7862@uda0132425 \
    --to=vigneshr@ti.com \
    --cc=a-govindraju@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).