[RFC PATCH v2 0/5] Add initial support for AM62D2-EVM

Paresh Bhagat p-bhagat at ti.com
Thu Sep 18 15:50:55 CEST 2025


Hi Tom,


On 10/09/25 03:33, Tom Rini wrote:
> 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).


Thanks for the review. Will take into account in the next revision.
In case of am62d, I could reuse the same yaml file as am62a. That should 
reduce the patch size at-least.
For a generic solution across boards, we need to have a right usage 
model something that will need more discussion. Same with the case of 
ddr config here.
>


More information about the U-Boot mailing list