From: Bryan Brattlof <bb@ti.com>
To: Paresh Bhagat <p-bhagat@ti.com>
Cc: <nm@ti.com>, <vigneshr@ti.com>, <praneeth@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<khasim@ti.com>, <v-singh1@ti.com>, <afd@ti.com>,
<devarsht@ti.com>, <s-vadapalli@ti.com>, <andrew@lunn.ch>
Subject: Re: [PATCH v5 4/4] arm64: dts: ti: Add support for AM62D2-EVM
Date: Tue, 1 Jul 2025 11:25:04 -0500 [thread overview]
Message-ID: <20250701162504.dck3763ik6kpo7ec@bryanbrattlof.com> (raw)
In-Reply-To: <20250627115753.2246881-5-p-bhagat@ti.com>
On June 27, 2025 thus sayeth Paresh Bhagat:
> AM62D-EVM evaluation module (EVM) is a low-cost expandable platform board
> designed for AM62D2 SoC from TI. It supports the following interfaces:
>
> * 4 GB LPDDR4 RAM
> * x2 Gigabit Ethernet expansion connectors
> * x4 3.5mm TRS Audio Jack Line In
> * x4 3.5mm TRS Audio Jack Line Out
> * x2 Audio expansion connectors
> * x1 Type-A USB 2.0, x1 Type-C dual-role device (DRD) USB 2.0
> * x1 UHS-1 capable micro SD card slot
> * 32 GB eMMC Flash
> * 512 Mb OSPI NOR flash
> * x4 UARTs via USB 2.0-B
> * XDS110 for onboard JTAG debug using USB
> * Temperature sensors, user push buttons and LEDs
>
> Although AM62D2 and AM62A7 differ in peripheral capabilities example
> multimedia, VPAC, and display subsystems, the core architecture remains
> same. To reduce duplication, AM62D support reuses the AM62A dtsi and the
> necessary overrides will be handled in SOC specific dtsi file and a
> board specific dts.
>
> Add basic support for AM62D2-EVM.
>
> Schematics Link - https://www.ti.com/lit/zip/sprcal5
>
> Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> ---
> arch/arm64/boot/dts/ti/Makefile | 3 +
> arch/arm64/boot/dts/ti/k3-am62d2-evm.dts | 599 +++++++++++++++++++++++
> arch/arm64/boot/dts/ti/k3-am62d2.dtsi | 25 +
> 3 files changed, 627 insertions(+)
> create mode 100644 arch/arm64/boot/dts/ti/k3-am62d2-evm.dts
> create mode 100644 arch/arm64/boot/dts/ti/k3-am62d2.dtsi
>
...
> diff --git a/arch/arm64/boot/dts/ti/k3-am62d2.dtsi
> b/arch/arm64/boot/dts/ti/k3-am62d2.dtsi
> new file mode 100644
> index 000000000000..70aeb40872a9
> --- /dev/null
> +++ b/arch/arm64/boot/dts/ti/k3-am62d2.dtsi
> @@ -0,0 +1,25 @@
> +// SPDX-License-Identifier: GPL-2.0-only OR MIT
> +/*
> + * Device Tree Source for AM62D2 SoC family in Quad core configuration
> + *
> + * TRM: https://www.ti.com/lit/pdf/sprujd4
> + *
> + * Copyright (C) 2025 Texas Instruments Incorporated - https://www.ti.com/
> + */
> +
> +/dts-v1/;
> +
> +#include "k3-am62a7.dtsi"
If we want to reuse the AM62A chassis I think we should probably reused
the AM62AX_IOPAD() macro instead of creating a new one.
> +
> +/ {
> + model = "Texas Instruments K3 AM62D SoC";
> + compatible = "ti,am62d2";
> +};
> +
> +&vpu {
> + status = "disabled";
> +};
> +
> +&e5010 {
> + status = "disabled";
> +};
So I could be a little out of date on the style guidelines here, but my
intuition is device trees, much like real trees, can only grow, so we
can't inherit the am62a.dtsi and remove things.
My understanding is we have to create a full am62d.dtsi with its
features that the am62a.dtsi can extend with the vpu{} and e5010{} nodes
~Bryan
next prev parent reply other threads:[~2025-07-01 16:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 11:57 [PATCH v5 0/4] Add support for AM62D2 SoC and EVM Paresh Bhagat
2025-06-27 11:57 ` [PATCH v5 1/4] arm64: dts: ti: Add bootph property to nodes at source for am62a Paresh Bhagat
2025-07-01 16:08 ` Bryan Brattlof
2025-07-03 5:53 ` Paresh Bhagat
2025-06-27 11:57 ` [PATCH v5 2/4] dt-bindings: arm: ti: Add AM62D2 SoC and Boards Paresh Bhagat
2025-06-27 11:57 ` [PATCH v5 3/4] arm64: dts: ti: Add pinctrl entries for AM62D2 family of SoCs Paresh Bhagat
2025-06-27 11:57 ` [PATCH v5 4/4] arm64: dts: ti: Add support for AM62D2-EVM Paresh Bhagat
2025-07-01 16:25 ` Bryan Brattlof [this message]
2025-07-03 6:42 ` Paresh Bhagat
2025-07-03 12:20 ` Bryan Brattlof
2025-07-04 9:00 ` Paresh Bhagat
2025-07-04 4:10 ` Vignesh Raghavendra
2025-07-04 8:46 ` Paresh Bhagat
2025-07-04 4:50 ` Vignesh Raghavendra
2025-07-04 8:49 ` 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=20250701162504.dck3763ik6kpo7ec@bryanbrattlof.com \
--to=bb@ti.com \
--cc=afd@ti.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=khasim@ti.com \
--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=p-bhagat@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--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
all inboxes | Powered by JetHome®