From: Parvathi Pudi <parvathi@couthit.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: parvathi <parvathi@couthit.com>, tony <tony@atomide.com>,
robh <robh@kernel.org>, krzk+dt <krzk+dt@kernel.org>,
conor+dt <conor+dt@kernel.org>,
richardcochran <richardcochran@gmail.com>,
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>,
Prajith Jayarajan <prajith@ti.com>,
Vignesh Raghavendra <vigneshr@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>, afd <afd@ti.com>,
m-karicheri2 <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: Wed, 15 Oct 2025 18:59:25 +0530 (IST) [thread overview]
Message-ID: <1064878067.81811.1760534965853.JavaMail.zimbra@couthit.local> (raw)
In-Reply-To: <8cfc5ece-6c2e-48d9-a65c-3edbcc9edc39@lunn.ch>
Hi,
>> + interrupt-names = "rx", "emac_ptp_tx",
>> + "hsr_ptp_tx";
>
> Something looks wrong with the indentation here. The same happens in
> at least one other place.
>
we will correct the indentation of the interrupt-names property to properly
align the continuation line as shown below.
interrupt-names = "rx", "emac_ptp_tx",
"hsr_ptp_tx";
We will make sure to address this in all the applicable places and include
this fix in the next version.
>> +&pruss2_mdio {
>> + status = "okay";
>> + pruss2_eth0_phy: ethernet-phy@0 {
>> + reg = <0>;
>> + interrupt-parent = <&gpio3>;
>> + interrupts = <30 IRQ_TYPE_EDGE_FALLING>;
>> + };
>> +
>> + pruss2_eth1_phy: ethernet-phy@1 {
>> + reg = <1>;
>> + interrupt-parent = <&gpio3>;
>> + interrupts = <31 IRQ_TYPE_EDGE_FALLING>;
>> + };
>
>
> PHY interrupts are 99% level, not edge, because they represent an
> interrupt controller in the PHY, and you need to clear all the
> interrupts in the controller before it deasserts the interrupt pin.
>
> Andrew
Sure, we will check and come back with more details on this.
Thanks and Regards,
Parvathi.
next prev parent reply other threads:[~2025-10-15 13:29 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
2025-10-15 13:13 ` Parvathi Pudi
2025-10-13 14:44 ` Andrew Lunn
2025-10-15 13:29 ` Parvathi Pudi [this message]
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=1064878067.81811.1760534965853.JavaMail.zimbra@couthit.local \
--to=parvathi@couthit.com \
--cc=afd@ti.com \
--cc=andrew@lunn.ch \
--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=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