From: Stefano Radaelli <stefano.radaelli21@gmail.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, pierluigi.p@variscite.com,
matthias.p@variscite.com,
Stefano Radaelli <stefano.r@variscite.com>,
Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v2 1/4] arm64: dts: ti: var-som-am62p: fix Ethernet PHY configuration
Date: Tue, 14 Jul 2026 09:39:29 +0200 [thread overview]
Message-ID: <alXnsYCluZiY0sYd@Lord-Beerus.station> (raw)
In-Reply-To: <178400918994.3109814.1083731005888044586.b4-reply@b4>
On Tue, Jul 14, 2026 at 11:36:29AM +0530, Vignesh Raghavendra wrote:
> On 2026-07-13 15:32:00+02:00, Stefano Radaelli wrote:
> > On Mon, Jul 13, 2026 at 04:02:34PM +0530, Vignesh Raghavendra wrote:
> >
> > > >
> > >
> > > So are the reset delays no longer required? Or they taken care of
> > > somewhere else?
> > >
> > >
> >
> > Hi Vignesh,
> >
> > No, because this GPIO actually is not used as a PHY reset.
> >
> > After reviewing the hardware, it turned out that this signal is a
> > board-level enable signal required for the PHY to operate, rather than
> > a reset line.
> > The previous reset-assert-us and reset-deassert-us values were
> > associated with the incorrect modelling of this GPIO as a reset, and
> > are not longer needed.
> >
>
> Along the same lines does [0] need update to how the cpsw3g_phy0 is
> described then as its seems very similar to what this patch is addressing?
>
> [0] https://lore.kernel.org/linux-arm-kernel/0a7bdfda80309eaa207b5b369d72f4bcb16e0604.1783864932.git.stefano.r@variscite.com/
>
> >
> > Best Regards,
> > Stefano
>
Hi Vignesh,
No, the AM62 DTS referenced in [0] does not need the same update.
The VAR-SOM-AM62 uses a different Ethernet PHY and has separate signals
for the PHY supply enable and PHY reset. In that design, GPIO0_45
controls the PHY 3.3 V supply, while GPIO0_46 is connected to the PHY
reset input, so the existing reset-gpios description is correct.
The issue addressed by this patch is specific to the VAR-SOM-AM62P.
Thank you for your review,
Best Regards,
Stefano
next prev parent reply other threads:[~2026-07-14 7:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 20:56 [PATCH v2 0/4] arm64: dts: am62p5-var-som-symphony: align DTS with hardware revision Stefano Radaelli
2026-06-28 20:56 ` [PATCH v2 1/4] arm64: dts: ti: var-som-am62p: fix Ethernet PHY configuration Stefano Radaelli
2026-07-13 10:32 ` Vignesh Raghavendra
2026-07-13 13:32 ` Stefano Radaelli
2026-07-14 6:06 ` Vignesh Raghavendra
2026-07-14 7:39 ` Stefano Radaelli [this message]
2026-06-28 20:56 ` [PATCH v2 2/4] arm64: dts: ti: var-som-am62p: update audio codec configuration Stefano Radaelli
2026-06-28 20:56 ` [PATCH v2 3/4] arm64: dts: am62p5-var-som-symphony: add touchscreen support Stefano Radaelli
2026-06-28 20:56 ` [PATCH v2 4/4] arm64: dts: am62p5-var-som-symphony: add TPM support Stefano Radaelli
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=alXnsYCluZiY0sYd@Lord-Beerus.station \
--to=stefano.radaelli21@gmail.com \
--cc=conor+dt@kernel.org \
--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=matthias.p@variscite.com \
--cc=nm@ti.com \
--cc=pierluigi.p@variscite.com \
--cc=robh@kernel.org \
--cc=stefano.r@variscite.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