From: Nishanth Menon <nm@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Marc Zyngier <maz@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>
Subject: Re: [PATCH v3 0/5] arm64: Initial support for Texas Instruments AM62 Platform
Date: Mon, 28 Feb 2022 05:37:48 -0600 [thread overview]
Message-ID: <20220228113748.nmoduketo72eaoql@pulse> (raw)
In-Reply-To: <164604791648.14181.3995342010827414573.b4-ty@ti.com>
On 05:32-20220228, Nishanth Menon wrote:
> Hi Vignesh Raghavendra,
>
> On Fri, 25 Feb 2022 17:32:34 +0530, Vignesh Raghavendra wrote:
> > This adds AM62 SoC support.
> >
> > The AM62 SoC family is the follow on AM335x built on K3 Multicore SoC
> > architecture platform, providing ultra-low-power modes, dual display,
> > multi-sensor edge compute, security and other BOM-saving integration.
> > The AM62 SoC targets broad market to enable applications such as
> > Industrial HMI, PLC/CNC/Robot control, Medical Equipment, Building
> > Automation, Appliances and more.
> >
> > [...]
>
> I have applied the following to branch ti-k3-dts-next on [1].
> Thank you!
>
> [1/5] soc: ti: k3-socinfo: Add AM62x JTAG ID
> commit: c1f284b8207bb4e33d021e34dd3be525abc39b8f
> [2/5] dt-bindings: arm: ti: Add bindings for AM625 SoC
> commit: 52b7a9c87a72aa9798051b271fa7e4fb62910624
> [3/5] dt-bindings: pinctrl: k3: Introduce pinmux definitions for AM62
> commit: 67cf6b691ec36da1318051c6776ff3523200ebc7
> [4/5] arm64: dts: ti: Introduce base support for AM62x SoC
> commit: c8c226192205cf536e3e975301b5ad2fcfb2de36
> [5/5] arm64: dts: ti: Add support for AM62-SK
> commit: e32f766b6e378ec3b6095470b1cd54fdc79792c6
Just a headsup -> I split the patches into two branches. [1/5] is
available in ti-drivers-soc-next Vs the rest in ti-k3-dts-next
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D)/Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2022-02-28 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 12:02 [PATCH v3 0/5] arm64: Initial support for Texas Instruments AM62 Platform Vignesh Raghavendra
2022-02-25 12:02 ` [PATCH v3 1/5] soc: ti: k3-socinfo: Add AM62x JTAG ID Vignesh Raghavendra
2022-02-25 12:02 ` [PATCH v3 2/5] dt-bindings: arm: ti: Add bindings for AM625 SoC Vignesh Raghavendra
2022-02-25 12:02 ` [PATCH v3 3/5] dt-bindings: pinctrl: k3: Introduce pinmux definitions for AM62 Vignesh Raghavendra
2022-02-25 12:02 ` [PATCH v3 4/5] arm64: dts: ti: Introduce base support for AM62x SoC Vignesh Raghavendra
2022-02-25 12:02 ` [PATCH v3 5/5] arm64: dts: ti: Add support for AM62-SK Vignesh Raghavendra
2022-02-26 17:54 ` [PATCH v3 0/5] arm64: Initial support for Texas Instruments AM62 Platform Bryan Brattlof
2022-02-28 11:32 ` Nishanth Menon
2022-02-28 11:37 ` Nishanth Menon [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=20220228113748.nmoduketo72eaoql@pulse \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.com \
/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).