From: Anshul Dalal <anshuld@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: Anshul Dalal <anshuld@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v1 0/4] Add support for TI AM6254atl SiP
Date: Thu, 14 Aug 2025 19:15:26 +0530 [thread overview]
Message-ID: <20250814134531.2743874-1-anshuld@ti.com> (raw)
Hi all,
This patch series adds support for AM6254atl SiP (or AM62x SiP for short)
to the linux device-tree.
The OPN (Orderable Part Number) 'AM6254atl' expands as follows[1]:
AM6254atl
||||
|||+-- Feature Lookup (L indicates 512MiB of integrated LPDDR4)
||+--- Device Speed Grade (T indicates 1.25GHz/1.4GHz on the A53 cores)
|+---- Silicon PG Revision (A indicates SR 1.0)
+----- Core configuration (4 indicates A53's in Quad core config)
AM62x SiP provides the existing AM62x SoC with 512MiB of DDR integrated in a
single packages.
This patch set adds the new 'k3-am6254atl' SoC level dtsi alongside the
'k3-am6254atl-sk' dts for the EVM (Evaluation Module board). The newly added
'k3-am625-sk-common' dtsi includes the common hardware between the existing
AM62x EVM and the new EVM for AM62x SiP.
Regards,
Anshul
---
[1]: https://www.ti.com/lit/ds/symlink/am625sip.pdf Page#21
Product Page:
https://www.ti.com/product/AM625SIP/part-details/AM6254ATLHJAMKR
---
Anshul Dalal (4):
arm64: dts: ti: k3-am62*: remove SoC dtsi from common dtsi
dt-bindings: arm: ti: Add binding for AM625 SiP
arm64: dts: ti: Introduce base support for AM6254atl SiP
arm64: dts: ti: Add support for AM6254atl SiP SK
.../devicetree/bindings/arm/ti/k3.yaml | 7 +
arch/arm64/boot/dts/ti/Makefile | 1 +
arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts | 8 +
.../arm64/boot/dts/ti/k3-am625-sk-common.dtsi | 296 +++++++++++++++++
arch/arm64/boot/dts/ti/k3-am625-sk.dts | 301 +-----------------
arch/arm64/boot/dts/ti/k3-am6254atl-sk.dts | 15 +
arch/arm64/boot/dts/ti/k3-am6254atl.dtsi | 23 ++
.../arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 8 -
8 files changed, 354 insertions(+), 305 deletions(-)
create mode 100644 arch/arm64/boot/dts/ti/k3-am625-sk-common.dtsi
create mode 100644 arch/arm64/boot/dts/ti/k3-am6254atl-sk.dts
create mode 100644 arch/arm64/boot/dts/ti/k3-am6254atl.dtsi
--
2.50.1
next reply other threads:[~2025-08-14 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 13:45 Anshul Dalal [this message]
2025-08-14 13:45 ` [PATCH v1 1/4] arm64: dts: ti: k3-am62*: remove SoC dtsi from common dtsi Anshul Dalal
2025-08-14 13:45 ` [PATCH v1 2/4] dt-bindings: arm: ti: Add binding for AM625 SiP Anshul Dalal
2025-08-14 20:46 ` Conor Dooley
2025-08-14 13:45 ` [PATCH v1 3/4] arm64: dts: ti: Introduce base support for AM6254atl SiP Anshul Dalal
2025-08-14 13:45 ` [PATCH v1 4/4] arm64: dts: ti: Add support for AM6254atl SiP SK Anshul Dalal
2025-08-29 12:35 ` [PATCH v1 0/4] Add support for TI AM6254atl SiP Bryan Brattlof
2025-09-12 9:48 ` Nishanth Menon
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=20250814134531.2743874-1-anshuld@ti.com \
--to=anshuld@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@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