From: "Michael Walle" <mwalle@kernel.org>
To: "Vignesh Raghavendra" <vigneshr@ti.com>,
"Vaishnav Achath" <vaishnav.a@ti.com>,
"Andrew Davis" <afd@ti.com>, <nm@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: Thu, 15 Feb 2024 17:29:42 +0100 [thread overview]
Message-ID: <CZ5SMYXNTTOP.3MZ8P9N5BY4SH@kernel.org> (raw)
In-Reply-To: <40e15761-70b3-4343-a4b3-653bc4e6637e@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 2186 bytes --]
Hi,
On Wed Feb 14, 2024 at 10:42 AM CET, Vignesh Raghavendra wrote:
> On 14/02/24 13:13, Vaishnav Achath wrote:
> > On 12/02/24 21:32, Michael Walle wrote:
> >> 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.
> >>
> >
> > Both names are correct, for other Jacinto devices J721S2 and J784S4, the
> > industrial variants (AM68, AM69 respectively) and those boards were
> > announced at a later point of time and since the automotive/J7 variants
> > were introduced first, the SoC dtsi and files have the J7XX names, for
> > AM62/AM64 there is no confusion in naming, in this case the initial TRM
> > itself mentions J722S and AM67 variants with similar capabilities, the
> > reasoning behind continuing with the J722S name is because the initial
> > support is being added for J722S EVM (the top marking on the SoC package
> > populated on the EVM say XJ722SAMW, this can be seen in the schematics
> > also), please let know if this clarifies the confusion.
> >
>
> AM64,AM62x/A/P are from different product line (Sitara) and don't have
> any other aliases.
>
> On the other hand, Jacinto SoCs have both J7xx variant and AM6xx part
> numbers. Its being really unpredictable wrt when AM6xx variants of
> Jacinto devices come out. So as a general rule, we name the DTS files
> based on the name of the first device that comes out in the market which
> has consistently been J7xx.
Thanks for the explanation. I just noticed that any k3-am6[89]*
device trees will include the j7xx SoC dtsi. That would have been my
next question: Boards with the AMxx will have the "correct" name
k3-amNN-*.
-michael
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Walle" <mwalle@kernel.org>
To: "Vignesh Raghavendra" <vigneshr@ti.com>,
"Vaishnav Achath" <vaishnav.a@ti.com>,
"Andrew Davis" <afd@ti.com>, <nm@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: Thu, 15 Feb 2024 17:29:42 +0100 [thread overview]
Message-ID: <CZ5SMYXNTTOP.3MZ8P9N5BY4SH@kernel.org> (raw)
In-Reply-To: <40e15761-70b3-4343-a4b3-653bc4e6637e@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2186 bytes --]
Hi,
On Wed Feb 14, 2024 at 10:42 AM CET, Vignesh Raghavendra wrote:
> On 14/02/24 13:13, Vaishnav Achath wrote:
> > On 12/02/24 21:32, Michael Walle wrote:
> >> 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.
> >>
> >
> > Both names are correct, for other Jacinto devices J721S2 and J784S4, the
> > industrial variants (AM68, AM69 respectively) and those boards were
> > announced at a later point of time and since the automotive/J7 variants
> > were introduced first, the SoC dtsi and files have the J7XX names, for
> > AM62/AM64 there is no confusion in naming, in this case the initial TRM
> > itself mentions J722S and AM67 variants with similar capabilities, the
> > reasoning behind continuing with the J722S name is because the initial
> > support is being added for J722S EVM (the top marking on the SoC package
> > populated on the EVM say XJ722SAMW, this can be seen in the schematics
> > also), please let know if this clarifies the confusion.
> >
>
> AM64,AM62x/A/P are from different product line (Sitara) and don't have
> any other aliases.
>
> On the other hand, Jacinto SoCs have both J7xx variant and AM6xx part
> numbers. Its being really unpredictable wrt when AM6xx variants of
> Jacinto devices come out. So as a general rule, we name the DTS files
> based on the name of the first device that comes out in the market which
> has consistently been J7xx.
Thanks for the explanation. I just noticed that any k3-am6[89]*
device trees will include the j7xx SoC dtsi. That would have been my
next question: Boards with the AMxx will have the "correct" name
k3-amNN-*.
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2024-02-15 16:30 UTC|newest]
Thread overview: 22+ 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 ` 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 ` 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 ` 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-06 10:06 ` Vaishnav Achath
2024-02-12 16:02 ` Michael Walle
2024-02-12 16:02 ` Michael Walle
2024-02-14 7:43 ` Vaishnav Achath
2024-02-14 7:43 ` Vaishnav Achath
2024-02-14 9:42 ` Vignesh Raghavendra
2024-02-14 9:42 ` Vignesh Raghavendra
2024-02-15 16:29 ` Michael Walle [this message]
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-08 8:58 ` Vaishnav Achath
2024-02-12 8:44 ` Manorit Chawdhry
2024-02-12 8:44 ` Manorit Chawdhry
2024-02-16 6:31 ` Vignesh Raghavendra
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=CZ5SMYXNTTOP.3MZ8P9N5BY4SH@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.