From: Maxime Ripard <maxime@cerno.tech>
To: Doug Berger <opendmb@gmail.com>, Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: GENET and UNIMAC MDIO probe issue?
Date: Fri, 22 Oct 2021 16:33:37 +0200 [thread overview]
Message-ID: <20211022143337.jorflirdb6ctc5or@gilmour> (raw)
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
Hi Florian, Doug,
I'm currently trying to make the RaspberryPi CM4 IO board probe its
ethernet controller, and it looks like genet doesn't manage to find its
PHY and errors out with:
[ 3.240435] libphy: Fixed MDIO Bus: probed
[ 3.248849] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
[ 3.259118] libphy: bcmgenet MII bus: probed
[ 3.278420] mdio_bus unimac-mdio--19: MDIO device at address 1 is missing.
[ 3.285661] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
....
[ 13.082281] could not attach to PHY
[ 13.089762] bcmgenet fd580000.ethernet eth0: failed to connect to PHY
[ 74.739621] could not attach to PHY
[ 74.746492] bcmgenet fd580000.ethernet eth0: failed to connect to PHY
Here's the full boot log:
https://pastebin.com/8RhuezSn
It looks like it's related to the following bugzilla entry:
https://bugzilla.kernel.org/show_bug.cgi?id=213485
However, that commit has been merged for a while apparently, and even
next-20211022 shows that behavior, both with the drivers built-in or as
modules. The other suggested fix to set probe_type to
PROBE_FORCE_SYNCHRONOUS doesn't seem to fix it either.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2021-10-22 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 14:33 Maxime Ripard [this message]
2021-10-22 15:35 ` GENET and UNIMAC MDIO probe issue? Stefan Wahren
2021-10-22 15:58 ` Maxime Ripard
2021-10-26 4:03 ` Cyril Brulebois
2021-10-22 16:27 ` Florian Fainelli
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=20211022143337.jorflirdb6ctc5or@gilmour \
--to=maxime@cerno.tech \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nsaenz@kernel.org \
--cc=opendmb@gmail.com \
--cc=stefan.wahren@i2se.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