From: Tom Rini <trini@konsulko.com>
To: Anshul Dalal <anshuld@ti.com>
Cc: u-boot@lists.denx.de, Beleswar Padhi <b-padhi@ti.com>,
Nishanth Menon <nm@ti.com>, Andrew Davis <afd@ti.com>,
Bryan Brattlof <bb@ti.com>, Vignesh R <vigneshr@ti.com>
Subject: Re: [PATCH v2 0/8] Add support for TI AM6254atl SiP
Date: Fri, 24 Oct 2025 12:02:19 -0600 [thread overview]
Message-ID: <20251024180219.GS6688@bill-the-cat> (raw)
In-Reply-To: <20251024-62sip_support-v2-0-23d4948af70c@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1808 bytes --]
On Fri, Oct 24, 2025 at 02:02:54PM +0530, Anshul Dalal wrote:
> Hi all,
>
> This patch series adds support for AM6254atl SiP (or AM62x SiP for
> short) to U-Boot.
>
> 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 on 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. The first 4 patches in the series
> are cherry-picked from the devicetree-rebasing repository at
> 'v6.18-rc2-dts'.
>
> Signed-off-by: Anshul Dalal <anshuld@ti.com>
> ---
> Changes in v2:
> - Add a new-line at the end of env file
> - Update the dependencies and rebase to master
> - Remove bloblist addr from the A53 defconfig
> - Link to v1:
> https://lore.kernel.org/r/20251022-62sip_support-v1-0-eed08d15e76d@ti.com
>
> ---
> Anshul Dalal (7):
> arm64: dts: ti: k3-am62*: remove SoC dtsi from common dtsi
> arm64: dts: ti: Introduce base support for AM6254atl SiP
> arm64: dts: ti: Add support for AM6254atl SiP SK
These are cherry-picks and should be separate and as-is, good.
> arm: dts: add support for AM6254atl at R5 SPL
> configs: add defconfigs for AM6254atl
> board: am62x: add env file for AM6254atl
> doc: add documentation for AM6254atl SiP
This should just be a commit that adds AM6254atl SiP support, not 4
commits.
> Beleswar Padhi (1):
> arm64: dts: ti: k3-am6*-boards: Add label to reserved-memory node
And this being separate makes sense.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-10-24 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 8:32 [PATCH v2 0/8] Add support for TI AM6254atl SiP Anshul Dalal
2025-10-24 8:32 ` [PATCH v2 1/8] arm64: dts: ti: k3-am6*-boards: Add label to reserved-memory node Anshul Dalal
2025-10-24 8:32 ` [PATCH v2 2/8] arm64: dts: ti: k3-am62*: remove SoC dtsi from common dtsi Anshul Dalal
2025-10-24 8:32 ` [PATCH v2 3/8] arm64: dts: ti: Introduce base support for AM6254atl SiP Anshul Dalal
2025-10-24 8:32 ` [PATCH v2 4/8] arm64: dts: ti: Add support for AM6254atl SiP SK Anshul Dalal
2025-10-24 8:32 ` [PATCH v2 5/8] arm: dts: add support for AM6254atl at R5 SPL Anshul Dalal
2025-10-24 8:33 ` [PATCH v2 6/8] configs: add defconfigs for AM6254atl Anshul Dalal
2025-10-24 8:33 ` [PATCH v2 7/8] board: am62x: add env file " Anshul Dalal
2025-10-24 8:33 ` [PATCH v2 8/8] doc: add documentation for AM6254atl SiP Anshul Dalal
2025-10-24 18:02 ` Tom Rini [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=20251024180219.GS6688@bill-the-cat \
--to=trini@konsulko.com \
--cc=afd@ti.com \
--cc=anshuld@ti.com \
--cc=b-padhi@ti.com \
--cc=bb@ti.com \
--cc=nm@ti.com \
--cc=u-boot@lists.denx.de \
--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