From: Igor Plyatov <plyatov@gmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
"Joe Perches" <joe@perches.com>,
"Luwei Zhou" <b45643@freescale.com>,
b38611@freescale.com,
"Richard Cochran" <richardcochran@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Fabio Estevam" <fabio.estevam@freescale.com>,
"Lothar Waßmann" <LW@KARO-electronics.de>,
"Frank Li" <Frank.Li@freescale.com>
Subject: Buggy cable detection on i.MX51, fec driver and LAN8700 PHY
Date: Mon, 27 Jul 2015 17:50:36 +0300 [thread overview]
Message-ID: <55B6453C.10500@gmail.com> (raw)
Dear all,
very often we observe issue with Ethernet cable detection during cable
unplugging and plugging.
We use Voipac i.MX51 SOMs (System On Modules). They are based on
Freescale i.MX51 CPU with LAN7800 PHY in MII mode. The schematic of PHY
connection is very similar to the Freescale i.MX51 Babbage board.
The Ethernet interface eth0 is configured statically for simplicity, but
same issue exists with DHCP configuration.
I did a lot of tests to determine stability of Ethernet cable detection
by the "fec" Ethernet driver.
In normal operation, if I unplug the Ethernet cable, then "fec" driver
prints "fec 83fec000.ethernet eth0: Link is Down" and green LED
(Ethernet medium detected) is OFF.
If I plug cable back, then "fec" driver print "fec 83fec000.ethernet
eth0: Link is Up - 100Mbps/Full - flow control off" and green LED is ON.
But sometimes, after cable plugging, "fec" driver does not print
anything on the console and green LED does not show detection of
Ethernet cable. Frequency of issue appearing is a random value.
Sometimes issue appears after second cable unplugging/plugging, but
sometimes - after 10-20 unplugging/plugging.
The issue was tested and exists on kernels from linux-3.8.5 till current
linux-4.2-rc4-cbfe8fa6cd672011c755c3cd85c9ffd4e2d10a6f.
Same tests was made with different versions of the Barebox bootloader
and cable detection works flawless.
Please, help to resolve issue with Linux drivers.
Best wishes.
--
Igor Plyatov
next reply other threads:[~2015-07-27 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 14:50 Igor Plyatov [this message]
2015-07-28 1:24 ` Buggy cable detection on i.MX51, fec driver and LAN8700 PHY Duan Andy
2015-07-28 1:51 ` Fabio Estevam
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=55B6453C.10500@gmail.com \
--to=plyatov@gmail.com \
--cc=Frank.Li@freescale.com \
--cc=LW@KARO-electronics.de \
--cc=b38611@freescale.com \
--cc=b45643@freescale.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=fabio.estevam@freescale.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=u.kleine-koenig@pengutronix.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;
as well as URLs for NNTP newsgroup(s).