From: Meghana Malladi <m-malladi@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>
Cc: <conor+dt@kernel.org>, <krzk+dt@kernel.org>, <robh@kernel.org>,
<kristo@kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <netdev@vger.kernel.org>,
<srk@ti.com>, Roger Quadros <rogerq@kernel.org>,
<danishanwar@ti.com>, <m-malladi@ti.com>
Subject: [PATCH v2 0/2] Add ICSSG0 dual EMAC support for AM642 EVM
Date: Sat, 28 Feb 2026 17:02:01 +0530 [thread overview]
Message-ID: <20260228113203.498839-1-m-malladi@ti.com> (raw)
This series adds device tree overlay support for enabling ICSSG0 dual EMAC
on the AM642 EVM, along with the necessary PHY driver configuration.
The overlay enables both ICSSG0 Ethernet interfaces (port0 and port1) in
dual EMAC mode and can be combined with the existing ICSSG1 overlay to
enable all four ICSSG interfaces if needed.
The series also enables the DP83TG720 PHY driver required for the
DP83TG720-IND-SPE-EVM daughter card used with the ICSSG0 interface.
Meghana Malladi (2):
arm64: dts: ti: k3-am642-evm: Add ICSSG0 overlay for dual EMAC support
arm64: defconfig: Enable DP83TG720 PHY driver
arch/arm64/boot/dts/ti/Makefile | 4 +
.../boot/dts/ti/k3-am642-evm-icssg0.dtso | 203 ++++++++++++++++++
arch/arm64/configs/defconfig | 1 +
3 files changed, 208 insertions(+)
create mode 100644 arch/arm64/boot/dts/ti/k3-am642-evm-icssg0.dtso
base-commit: 4916f2e2f3fc9aef289fcd07949301e5c29094c2
--
2.43.0
next reply other threads:[~2026-02-28 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 11:32 Meghana Malladi [this message]
2026-02-28 11:32 ` [PATCH v2 1/2] arm64: dts: ti: k3-am642-evm: Add ICSSG0 overlay for dual EMAC support Meghana Malladi
2026-03-09 4:44 ` Vignesh Raghavendra
2026-02-28 11:32 ` [PATCH v2 2/2] arm64: defconfig: Enable DP83TG720 PHY driver Meghana Malladi
2026-03-04 15:32 ` [PATCH v2 0/2] Add ICSSG0 dual EMAC support for AM642 EVM Daolin Qiu
2026-03-04 15:44 ` Krzysztof Kozlowski
2026-03-07 0:21 ` Daolin Qiu
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=20260228113203.498839-1-m-malladi@ti.com \
--to=m-malladi@ti.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=srk@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