From: Tom Rini <trini@konsulko.com>
To: Paresh Bhagat <p-bhagat@ti.com>
Cc: vigneshr@ti.com, praneeth@ti.com, nm@ti.com,
u-boot@lists.denx.de, bb@ti.com, khasim@ti.com, v-singh1@ti.com,
afd@ti.com, anshuld@ti.com
Subject: Re: [RFC PATCH v2 0/5] Add initial support for AM62D2-EVM
Date: Tue, 9 Sep 2025 16:03:12 -0600 [thread overview]
Message-ID: <20250909220312.GD124814@bill-the-cat> (raw)
In-Reply-To: <20250909053429.444854-1-p-bhagat@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2845 bytes --]
On Tue, Sep 09, 2025 at 11:04:24AM +0530, Paresh Bhagat wrote:
> The AM62D2 SoC, part of the K3 architecture, is built for high-performance
> DSP tasks in automotive audio, pro audio, radar, sonar, and medical
> imaging. It features up to four Cortex-A53 cores (1.4GHz), two Cortex-R5F
> cores, and a C7x DSP with 2 TOPS MMA. Key interfaces include multi-channel
> McASP audio, TSN-capable Gigabit Ethernet, and a range of peripherals
> (UART, SPI, I2C, CAN, USB, eMMC/SD, OSPI, CSI). It supports LPDDR4/DDR4,
> secure boot with hardware security, and low-power modes with
> CAN/GPIO/UART wakeup.
[snip]
> arch/arm/dts/Makefile | 2 +
> arch/arm/dts/k3-am62d-ddr-1866mhz-32bit.dtsi | 2802 ++++++++++++++++++
> arch/arm/dts/k3-am62d-evm-binman.dtsi | 262 ++
> arch/arm/dts/k3-am62d2-evm-u-boot.dtsi | 14 +
> arch/arm/dts/k3-am62d2-r5-evm.dts | 82 +
> arch/arm/mach-k3/am62ax/Kconfig | 25 +
> board/ti/am62dx/Kconfig | 26 +
> board/ti/am62dx/MAINTAINERS | 8 +
> board/ti/am62dx/Makefile | 7 +
> board/ti/am62dx/am62dx.env | 21 +
> board/ti/am62dx/board-cfg.yaml | 36 +
> board/ti/am62dx/evm.c | 37 +
> board/ti/am62dx/pm-cfg.yaml | 12 +
> board/ti/am62dx/rm-cfg.yaml | 1047 +++++++
> board/ti/am62dx/sec-cfg.yaml | 379 +++
> board/ti/am62dx/tifs-rm-cfg.yaml | 903 ++++++
> configs/am62dx_evm_a53_defconfig | 22 +
> configs/am62dx_evm_r5_defconfig | 20 +
> 18 files changed, 5705 insertions(+)
> create mode 100644 arch/arm/dts/k3-am62d-ddr-1866mhz-32bit.dtsi
> create mode 100644 arch/arm/dts/k3-am62d-evm-binman.dtsi
> create mode 100644 arch/arm/dts/k3-am62d2-evm-u-boot.dtsi
> create mode 100644 arch/arm/dts/k3-am62d2-r5-evm.dts
> create mode 100644 board/ti/am62dx/Kconfig
> create mode 100644 board/ti/am62dx/MAINTAINERS
> create mode 100644 board/ti/am62dx/Makefile
> create mode 100644 board/ti/am62dx/am62dx.env
> create mode 100644 board/ti/am62dx/board-cfg.yaml
> create mode 100644 board/ti/am62dx/evm.c
> create mode 100644 board/ti/am62dx/pm-cfg.yaml
> create mode 100644 board/ti/am62dx/rm-cfg.yaml
> create mode 100644 board/ti/am62dx/sec-cfg.yaml
> create mode 100644 board/ti/am62dx/tifs-rm-cfg.yaml
> create mode 100644 configs/am62dx_evm_a53_defconfig
> create mode 100644 configs/am62dx_evm_r5_defconfig
This isn't architecture and board, it's just a board, it should be a
single patch. In that some of these yaml files are big, it would be good
to figure out as a generic problem how to reduce that if possible (I
don't know if it is).
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-09-09 22:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 5:34 [RFC PATCH v2 0/5] Add initial support for AM62D2-EVM Paresh Bhagat
2025-09-09 5:34 ` [RFC PATCH v2 1/5] board: ti: Introduce the basic files needed to support am62d Paresh Bhagat
2025-09-09 5:34 ` [RFC PATCH v2 2/5] board: ti: am62dx: Add board configs for am62d Paresh Bhagat
2025-09-09 5:34 ` [RFC PATCH v2 3/5] arch: mach-k3: Introduce support for AM62D2-EVM Paresh Bhagat
2025-09-09 13:54 ` Andrew Davis
2025-09-18 11:24 ` Paresh Bhagat
2025-09-09 5:34 ` [RFC PATCH v2 4/5] arm: dts: Introduce AM62D2-EVM dtbs Paresh Bhagat
2025-09-10 4:38 ` Anshul Dalal
2025-09-18 13:18 ` Paresh Bhagat
2025-09-09 5:34 ` [RFC PATCH v2 5/5] configs: Introduce configs for the AM62D2-EVM Paresh Bhagat
2025-09-09 22:03 ` Tom Rini [this message]
2025-09-18 13:50 ` [RFC PATCH v2 0/5] Add initial support for AM62D2-EVM Paresh Bhagat
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=20250909220312.GD124814@bill-the-cat \
--to=trini@konsulko.com \
--cc=afd@ti.com \
--cc=anshuld@ti.com \
--cc=bb@ti.com \
--cc=khasim@ti.com \
--cc=nm@ti.com \
--cc=p-bhagat@ti.com \
--cc=praneeth@ti.com \
--cc=u-boot@lists.denx.de \
--cc=v-singh1@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.