From: Shawn Guo <shawnguo2@yeah.net>
To: Christoph Stoidner <c.stoidner@phytec.de>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, upstream@lists.phytec.de
Subject: Re: [PATCH v3] arm64: dts: freescale: imx93-phycore-som: Delay the phy reset by a gpio
Date: Wed, 20 Aug 2025 10:36:04 +0800 [thread overview]
Message-ID: <aKU0lPi485xA5SS9@dragon> (raw)
In-Reply-To: <20250524112315.695376-1-c.stoidner@phytec.de>
On Sat, May 24, 2025 at 01:23:15PM +0200, Christoph Stoidner wrote:
> According to the datasheet the phy needs to be held in reset until the
> reference clock got stable. Even though no issue was observed, fix this
> as the software should always comply with the specification.
>
> Use gpio4 23, which is connected to the phy reset pin. On the same pin
> RX_ER was used before, but this signal is optional and can be dropped.
>
> Note: This comes into effect with the phyCOREs SOM hardware revision 4.
> In revisions before, this gpio is not connected, and the phy reset is
> managed with the global hardware reset circuit.
>
> Signed-off-by: Christoph Stoidner <c.stoidner@phytec.de>
Applied, thanks!
prev parent reply other threads:[~2025-08-20 3:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 11:23 [PATCH v3] arm64: dts: freescale: imx93-phycore-som: Delay the phy reset by a gpio Christoph Stoidner
2025-05-24 17:44 ` Andrew Lunn
2025-05-24 21:37 ` AW: " Christoph Stoidner
2025-05-26 6:44 ` Stefan Wahren
2025-05-26 9:09 ` Christoph Stoidner
2025-05-26 9:24 ` Stefan Wahren
2025-05-26 10:04 ` Christoph Stoidner
2025-05-26 12:14 ` Stefan Wahren
2025-05-28 18:30 ` Christoph Stoidner
2025-05-28 19:29 ` Andrew Lunn
2025-05-30 13:40 ` Christoph Stoidner
2025-06-02 2:09 ` Andrew Lunn
2025-06-02 11:46 ` Christoph Stoidner
2025-06-02 12:26 ` Andrew Lunn
2025-07-08 8:35 ` [Upstream] " Primoz Fiser
2025-07-18 17:33 ` Christoph Stoidner
2025-07-18 17:47 ` Andrew Lunn
2025-08-07 12:53 ` Christoph Stoidner
2025-08-20 2:36 ` Shawn Guo [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=aKU0lPi485xA5SS9@dragon \
--to=shawnguo2@yeah.net \
--cc=c.stoidner@phytec.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=upstream@lists.phytec.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.