From: Paresh Bhagat <p-bhagat@ti.com>
To: Anshul Dalal <anshuld@ti.com>
Cc: <u-boot@lists.denx.de>, <bb@ti.com>, <khasim@ti.com>,
<v-singh1@ti.com>, <afd@ti.com>,
"Raghavendra, Vignesh" <vigneshr@ti.com>,
"Bajjuri, Praneeth" <praneeth@ti.com>,
"Menon, Nishanth" <nm@ti.com>
Subject: Re: [RFC PATCH v2 4/5] arm: dts: Introduce AM62D2-EVM dtbs
Date: Thu, 18 Sep 2025 18:48:46 +0530 [thread overview]
Message-ID: <8ad2c8b4-e4e4-48c4-9502-964705aa33c4@ti.com> (raw)
In-Reply-To: <DCOUCTBZ6JGI.QNZEO4LYIKR6@ti.com>
Hi Anshul,
On 10/09/25 10:08, Anshul Dalal wrote:
>
> On Tue Sep 9, 2025 at 11:04 AM IST, Paresh Bhagat wrote:
>> Introduce the base dts files needed for u-boot or to augment the linux
>> dtbs for use in the u-boot-spl and u-boot binaries. Support added for
>> HS-SE and HS-FS boot binaries for AM62dx via binman.
>>
>> Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
>> ---
>> 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 +
>> 5 files changed, 3162 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
>>
> [snip]
>> diff --git a/arch/arm/dts/k3-am62d2-evm-u-boot.dtsi b/arch/arm/dts/k3-am62d2-evm-u-boot.dtsi
>> new file mode 100644
>> index 00000000000..d1b17e8f83f
>> --- /dev/null
>> +++ b/arch/arm/dts/k3-am62d2-evm-u-boot.dtsi
>> @@ -0,0 +1,14 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +/*
>> + * Common AM62D EVM dts file for SPLs
>> + * Copyright (C) 2025 Texas Instruments Incorporated - https://www.ti.com/
>> + */
>> +
>> +#include "k3-am62d-evm-binman.dtsi"
>> +
>> +/ {
>> + chosen {
>> + stdout-path = "serial2:115200n8";
>> + tick-timer = &main_timer0;
>> + };
>> +};
Since serial_present is enabled, it checks for stdout in the specified
format.
Also we need to define timer property for r5, so does not make sense to
move it to kernel dts.
> The chosen node is already part of the kernel dt for the AM62d, why not
> move this addition to the kernel dt directly?
>
> Regards,
> Anshul
next prev parent reply other threads:[~2025-09-18 13:18 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 [this message]
2025-09-09 5:34 ` [RFC PATCH v2 5/5] configs: Introduce configs for the AM62D2-EVM Paresh Bhagat
2025-09-09 22:03 ` [RFC PATCH v2 0/5] Add initial support for AM62D2-EVM Tom Rini
2025-09-18 13:50 ` 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=8ad2c8b4-e4e4-48c4-9502-964705aa33c4@ti.com \
--to=p-bhagat@ti.com \
--cc=afd@ti.com \
--cc=anshuld@ti.com \
--cc=bb@ti.com \
--cc=khasim@ti.com \
--cc=nm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox