From: "Anwar, Md Danish" <a0501179@ti.com>
To: Parvathi Pudi <parvathi@couthit.com>, <tony@atomide.com>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<richardcochran@gmail.com>
Cc: <linux-omap@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<danishanwar@ti.com>, <pratheesh@ti.com>, <prajith@ti.com>,
<vigneshr@ti.com>, <praneeth@ti.com>, <srk@ti.com>,
<rogerq@ti.com>, <krishna@couthit.com>, <mohan@couthit.com>,
<pmohan@couthit.com>, <basharath@couthit.com>,
"Andrew F . Davis" <afd@ti.com>,
Murali Karicheri <m-karicheri2@ti.com>
Subject: Re: [PATCH 1/2] arm: dts: ti: Adds device tree nodes for PRU Cores, IEP and eCAP modules of PRU-ICSS2 Instance.
Date: Mon, 13 Oct 2025 19:17:52 +0530 [thread overview]
Message-ID: <463668d1-a6a7-4606-af05-25384eb97caa@ti.com> (raw)
In-Reply-To: <20251013125401.1435486-2-parvathi@couthit.com>
On 10/13/2025 6:22 PM, Parvathi Pudi wrote:
> From: Roger Quadros <rogerq@ti.com>
>
> The TI Sitara AM57xx series of devices consists of 2 PRU-ICSS instances
> (PRU-ICSS1 and PRU-ICSS2). This patch adds the device tree nodes for the
> PRU-ICSS2 instance to support DUAL-MAC mode of operation.
>
> Each PRU-ICSS instance consists of two PRU cores along with various
> peripherals such as the Interrupt Controller (PRU_INTC), the Industrial
> Ethernet Peripheral(IEP), the Real Time Media Independent Interface
> controller (MII_RT), and the Enhanced Capture (eCAP) event module.
>
> am57-pruss.dtsi - Adds IEP and eCAP peripheral as child nodes of
> the PRUSS subsystem node.
>
> am57xx-idk-common.dtsi - Adds PRU-ICSS2 instance node along with
> PRU eth port information and corresponding port configuration. It includes
> interrupt mapping for packet reception, HW timestamp collection, and
> PRU Ethernet ports in MII mode.
>
> am571x-idk.dts, am572x-idk.dts and am574x-idk.dts - GPIO configuration
> along with delay configuration for individual PRU Ethernet port.
>
> Reviewed-by: Mohan Reddy Putluru <pmohan@couthit.com>
Please don't carry internal review tags in upstream patches.
--
Thanks and Regards,
Md Danish Anwar
next prev parent reply other threads:[~2025-10-13 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 12:52 [PATCH 0/2] Add support for ICSSM Ethernet on AM57x, AM437x, and AM335x Parvathi Pudi
2025-10-13 12:52 ` [PATCH 1/2] arm: dts: ti: Adds device tree nodes for PRU Cores, IEP and eCAP modules of PRU-ICSS2 Instance Parvathi Pudi
2025-10-13 13:47 ` Anwar, Md Danish [this message]
2025-10-15 13:13 ` Parvathi Pudi
2025-10-13 14:44 ` Andrew Lunn
2025-10-15 13:29 ` Parvathi Pudi
2025-11-03 11:08 ` Parvathi Pudi
2025-10-13 12:52 ` [PATCH 2/2] arm: dts: ti: Adds support for AM335x and AM437x Parvathi Pudi
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=463668d1-a6a7-4606-af05-25384eb97caa@ti.com \
--to=a0501179@ti.com \
--cc=afd@ti.com \
--cc=basharath@couthit.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=krishna@couthit.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=mohan@couthit.com \
--cc=netdev@vger.kernel.org \
--cc=parvathi@couthit.com \
--cc=pmohan@couthit.com \
--cc=prajith@ti.com \
--cc=praneeth@ti.com \
--cc=pratheesh@ti.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=rogerq@ti.com \
--cc=srk@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).