From: Jerome Forissier <jerome.forissier@arm.com>
To: U-boot Openlist <u-boot@lists.denx.de>,
Boon Khai Ng <boon.khai.ng@altera.com>
Cc: Andrew Goodbody <andrew.goodbody@linaro.org>,
Heiko Schocher <hs@nabladev.com>,
Nikunj Kela <nikunj.kela@sima.ai>,
Peter Robinson <pbrobinson@gmail.com>,
Tien Fong Chee <tien.fong.chee@altera.com>,
Tom Rini <trini@konsulko.com>,
Dinesh Maniyam <dinesh.maniyam@altera.com>,
Alif Zakuan Yuslaimi <alif.zakuan.yuslaimi@altera.com>,
Chen Huei Lok <chen.huei.lok@altera.com>,
Kok Kiang Hea <kok.kiang.hea@altera.com>,
nd@arm.com
Subject: Re: [PATCH v1] net: dwc_eth_xgmac: Return -ENODEV when phy_connect() fails
Date: Mon, 20 Jul 2026 13:13:32 +0200 [thread overview]
Message-ID: <8454b1d7-4ecc-4fdf-962f-c483fa5e4ed8@arm.com> (raw)
In-Reply-To: <20260714071927.27877-1-boon.khai.ng@altera.com>
On Tue, 14 Jul 2026 15:19:27 +0800, Boon Khai Ng wrote:
> When multiple Ethernet controllers are enabled in the device tree,
> but only one controller is actually present in hardware, the
> non-existent controller still attempts to connect to a PHY.
>
> In this case, phy_connect() may return NULL without setting an
> error code. The current driver only logs the failure but does not
> propagate an error, causing the initialization flow to continue
> with an invalid PHY handle.
>
> [...]
Applied to u-boot-net/for-master, thanks!
[1/1] net: dwc_eth_xgmac: Return -ENODEV when phy_connect() fails
commit: 41913031b3411d523302fdc9acd4dc3dd4f02677
Best regards,
--
Jerome Forissier <jerome.forissier@arm.com>
prev parent reply other threads:[~2026-07-20 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 7:19 [PATCH v1] net: dwc_eth_xgmac: Return -ENODEV when phy_connect() fails Boon Khai Ng
2026-07-20 11:13 ` Jerome Forissier [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=8454b1d7-4ecc-4fdf-962f-c483fa5e4ed8@arm.com \
--to=jerome.forissier@arm.com \
--cc=alif.zakuan.yuslaimi@altera.com \
--cc=andrew.goodbody@linaro.org \
--cc=boon.khai.ng@altera.com \
--cc=chen.huei.lok@altera.com \
--cc=dinesh.maniyam@altera.com \
--cc=hs@nabladev.com \
--cc=kok.kiang.hea@altera.com \
--cc=nd@arm.com \
--cc=nikunj.kela@sima.ai \
--cc=pbrobinson@gmail.com \
--cc=tien.fong.chee@altera.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox