From: "Michael Walle" <mwalle@kernel.org>
To: "Andrew Davis" <afd@ti.com>,
"Vaishnav Achath" <vaishnav.a@ti.com>, <nm@ti.com>,
<vigneshr@ti.com>, <conor+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <kristo@kernel.org>,
<robh+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <u-kumar1@ti.com>,
<j-choudhary@ti.com>
Subject: Re: [PATCH v2 3/3] arm64: dts: ti: Add support for TI J722S Evaluation Module
Date: Mon, 12 Feb 2024 17:02:31 +0100 [thread overview]
Message-ID: <CZ386ITQ83KH.1KNOV5MXLXPBF@kernel.org> (raw)
In-Reply-To: <20240206100608.127702-4-vaishnav.a@ti.com>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
Hi,
On Tue Feb 6, 2024 at 11:06 AM CET, Vaishnav Achath wrote:
> +# Boards with J722s SoC
> +dtb-$(CONFIG_ARCH_K3) += k3-j722s-evm.dtb
I'm a bit confused by your names. What are the new/correct ones now?
Some seem to use the amXX names and some the jXX ones. I've read [1]
and it appears it was suggested to use the am67 names for the device
trees. Esp. because there is already, am62, am64, am65, am68 and
am69 in as names for the device trees.
The TRM you've linked in the cover letter doesn't shed much light
either. It just lists both.
-michael
[1] https://lore.kernel.org/all/81f90d13-da10-4a68-a0e7-95212f40b3e8@ti.com/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2024-02-12 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 10:06 [PATCH v2 0/3] arm64: dts: ti: Introduce J722S SoC and EVM Vaishnav Achath
2024-02-06 10:06 ` [PATCH v2 1/3] dt-bindings: arm: ti: Add bindings for J722S SoCs Vaishnav Achath
2024-02-06 10:06 ` [PATCH v2 2/3] arm64: dts: ti: Introduce J722S family of SoCs Vaishnav Achath
2024-02-06 10:06 ` [PATCH v2 3/3] arm64: dts: ti: Add support for TI J722S Evaluation Module Vaishnav Achath
2024-02-12 16:02 ` Michael Walle [this message]
2024-02-14 7:43 ` Vaishnav Achath
2024-02-14 9:42 ` Vignesh Raghavendra
2024-02-15 16:29 ` Michael Walle
2024-02-08 8:58 ` [PATCH v2 0/3] arm64: dts: ti: Introduce J722S SoC and EVM Vaishnav Achath
2024-02-12 8:44 ` Manorit Chawdhry
2024-02-16 6:31 ` Vignesh Raghavendra
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=CZ386ITQ83KH.1KNOV5MXLXPBF@kernel.org \
--to=mwalle@kernel.org \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-choudhary@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vaishnav.a@ti.com \
--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).