From: Parvathi Pudi <parvathi@couthit.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: nm <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
afd <afd@ti.com>, Kevin Hilman <khilman@baylibre.com>,
rogerq <rogerq@kernel.org>, tony <tony@atomide.com>,
robh <robh@kernel.org>, krzk+dt <krzk+dt@kernel.org>,
conor+dt <conor+dt@kernel.org>,
richardcochran <richardcochran@gmail.com>,
aaro koskinen <aaro.koskinen@iki.fi>,
andreas <andreas@kemnade.info>, Andrew Lunn <andrew@lunn.ch>,
linux-omap <linux-omap@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
danishanwar <danishanwar@ti.com>, pratheesh <pratheesh@ti.com>,
j-rameshbabu <j-rameshbabu@ti.com>, praneeth <praneeth@ti.com>,
srk <srk@ti.com>, rogerq <rogerq@ti.com>,
krishna <krishna@couthit.com>, mohan <mohan@couthit.com>,
pmohan <pmohan@couthit.com>, basharath <basharath@couthit.com>,
Murali Karicheri <m-karicheri2@ti.com>
Subject: Re: [PATCH v4 2/2] arm: dts: ti: Adds support for AM335x and AM437x
Date: Thu, 26 Feb 2026 13:58:49 +0530 (IST) [thread overview]
Message-ID: <1885117045.525472.1772094529965.JavaMail.zimbra@couthit.local> (raw)
In-Reply-To: <B3077F98-CC5C-4093-8319-CF45EECEAE4D@goldelico.com>
Hi,
> Hi,
>
>> Am 05.01.2026 um 17:21 schrieb Parvathi Pudi <parvathi@couthit.com>:
>>
>> From: Roger Quadros <rogerq@ti.com>
>>
>> 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.
>>
>
> I am just wondering about the subject of this patch.
>
> It reads as if general AM335x and AM437x support is introduced for the first
> time.
> IMHO it should tell which subsystem/improvement is added.
>
Sure, we will address this in the next version.
Thanks and Regards,
Parvathi
prev parent reply other threads:[~2026-02-26 8:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 16:21 [PATCH v4 0/2] Add support for ICSSM Ethernet on AM57x, AM437x, and AM335x Parvathi Pudi
2026-01-05 16:21 ` [PATCH v4 1/2] arm: dts: ti: Adds device tree nodes for PRU Cores, IEP and eCAP modules of PRU-ICSS2 Instance Parvathi Pudi
2026-01-05 16:21 ` [PATCH v4 2/2] arm: dts: ti: Adds support for AM335x and AM437x Parvathi Pudi
2026-01-05 19:22 ` Andrew Davis
2026-01-08 12:02 ` Parvathi Pudi
2026-01-16 12:47 ` Parvathi Pudi
2026-01-16 13:55 ` Andrew Lunn
2026-02-24 8:09 ` Parvathi Pudi
2026-02-24 8:48 ` H. Nikolaus Schaller
2026-02-26 8:28 ` Parvathi Pudi [this message]
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=1885117045.525472.1772094529965.JavaMail.zimbra@couthit.local \
--to=parvathi@couthit.com \
--cc=aaro.koskinen@iki.fi \
--cc=afd@ti.com \
--cc=andreas@kemnade.info \
--cc=andrew@lunn.ch \
--cc=basharath@couthit.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=j-rameshbabu@ti.com \
--cc=khilman@baylibre.com \
--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=nm@ti.com \
--cc=pmohan@couthit.com \
--cc=praneeth@ti.com \
--cc=pratheesh@ti.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=rogerq@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