From: Roger Quadros <rogerq@kernel.org>
To: nm@ti.com, joe.hershberger@ni.com
Cc: robertcnelson@gmail.com, jkridner@beagleboard.org,
r-gunasekaran@ti.com, s-vadapalli@ti.com, srk@ti.com,
trini@konsulko.com, u-boot@lists.denx.de,
Roger Quadros <rogerq@kernel.org>
Subject: [PATCH 0/2] net: Fix Ethernet PHY detection on Beagleplay
Date: Tue, 22 Aug 2023 15:13:48 +0300 [thread overview]
Message-ID: <20230822121350.51324-1-rogerq@kernel.org> (raw)
Hi,
Beagleplay has a buggy Ethernet PHY implementation for the Gigabit
PHY in the sense that it is non responsive over MDIO immediately
after power-up/reset.
We need to either try multiple times or wait sufficiently long enough
(couple of 10s of ms?) before the PHY begins to respond correctly.
One theory is that the PHY is configured to operate on MDIO address 0
which it treats as a special broadcast address.
Datasheet states:
"PHYAD (config pins) sets the PHY address for the device.
The RTL8211F(I)/RTL8211FD(I) supports PHY addresses from 0x01 to 0x07.
Note 1: An MDIO command with PHY address=0 is a broadcast from the MAC;
each PHY device should respond."
This issue is not seen with the other PHY (different make) on the board
which is configured for address 0x1.
As a woraround we try to probe the PHY multiple times instead of giving
up on the first attempt.
cheers,
-roger
Roger Quadros (2):
net: ti: am65-cpsw-nuss: Workaround for buggy PHY/Board
net: phy: Change "PHY not found" message to debug()
drivers/net/phy/phy.c | 2 +-
drivers/net/ti/am65-cpsw-nuss.c | 19 ++++++++++++++-----
2 files changed, 15 insertions(+), 6 deletions(-)
base-commit: a169438411f9277cc689c14078151aa1d1caae3c
--
2.34.1
next reply other threads:[~2023-08-22 12:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 12:13 Roger Quadros [this message]
2023-08-22 12:13 ` [PATCH 1/2] net: ti: am65-cpsw-nuss: Workaround for buggy PHY/Board Roger Quadros
2023-08-23 4:35 ` Siddharth Vadapalli
2023-08-23 7:52 ` Roger Quadros
2023-08-23 8:02 ` Siddharth Vadapalli
2023-08-23 8:14 ` Roger Quadros
2023-08-23 8:35 ` Roger Quadros
2023-08-24 18:04 ` Siddharth Vadapalli
2023-08-24 18:24 ` Tom Rini
2023-08-24 19:09 ` Roger Quadros
2023-08-25 5:42 ` Siddharth Vadapalli
2023-08-25 7:52 ` Roger Quadros
2023-08-25 8:22 ` Siddharth Vadapalli
2023-08-22 12:13 ` [PATCH 2/2] net: phy: Change "PHY not found" message to debug() Roger Quadros
2023-08-23 4:54 ` Siddharth Vadapalli
2023-08-23 8:06 ` Roger Quadros
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=20230822121350.51324-1-rogerq@kernel.org \
--to=rogerq@kernel.org \
--cc=jkridner@beagleboard.org \
--cc=joe.hershberger@ni.com \
--cc=nm@ti.com \
--cc=r-gunasekaran@ti.com \
--cc=robertcnelson@gmail.com \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.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