From: Francois Romieu <romieu@fr.zoreil.com>
To: Darren Salt <linux@youmustbejoking.demon.co.uk>
Cc: akpm@osdl.org, hchacha@users.sourceforge.net, jeff@garzik.org,
syed.azam@hp.com, netdev@vger.kernel.org
Subject: Re: [patch 1/1] r8169 driver: corega support
Date: Sat, 21 Oct 2006 22:15:33 +0200 [thread overview]
Message-ID: <20061021201533.GA31768@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <4E79505750%linux@youmustbejoking.demon.co.uk>
Darren Salt <linux@youmustbejoking.demon.co.uk> :
[...]
> It does, but the patch causes the module to report that the reset failed even
> after reporting that it's done. A fix for this is attached.
Oops. Ok with the one below ?
r8169: perform a PHY reset before any other operation at boot time
Realtek's 8139/810x (0x8136) PCI-E comes with a touchy PHY.
A big heavy reset seems to calm it down.
Fix for http://bugzilla.kernel.org/show_bug.cgi?id=7378.
Signed-off-by: Francois Romieu <romieu@fr.zoreil.com>
Signed-off-by: Darren Salt <linux@youmustbejoking.demon.co.uk>
---
drivers/net/r8169.c | 18 ++++++++++++++++++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/drivers/net/r8169.c b/drivers/net/r8169.c
index c2c9a86..03c0dc5 100644
--- a/drivers/net/r8169.c
+++ b/drivers/net/r8169.c
@@ -1442,6 +1442,22 @@ static void rtl8169_release_board(struct
free_netdev(dev);
}
+static void rtl8169_phy_reset(struct net_device *dev,
+ struct rtl8169_private *tp)
+{
+ void __iomem *ioaddr = tp->mmio_addr;
+ int i;
+
+ tp->phy_reset_enable(ioaddr);
+ for (i = 0; i < 100; i++) {
+ if (!tp->phy_reset_pending(ioaddr))
+ return;
+ msleep(1);
+ }
+ if (netif_msg_link(tp))
+ printk(KERN_ERR "%s: PHY reset failed.\n", dev->name);
+}
+
static void rtl8169_init_phy(struct net_device *dev, struct rtl8169_private *tp)
{
void __iomem *ioaddr = tp->mmio_addr;
@@ -1470,6 +1486,8 @@ static void rtl8169_init_phy(struct net_
rtl8169_link_option(board_idx, &autoneg, &speed, &duplex);
+ rtl8169_phy_reset(dev, tp);
+
rtl8169_set_speed(dev, autoneg, speed, duplex);
if ((RTL_R8(PHYstatus) & TBI_Enable) && netif_msg_link(tp))
--
1.4.2.3
next prev parent reply other threads:[~2006-10-21 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200610202144.k9KLid8a003945@shell0.pdx.osdl.net>
2006-10-20 22:44 ` [patch 1/1] r8169 driver: corega support Francois Romieu
2006-10-21 13:52 ` Darren Salt
2006-10-21 20:15 ` Francois Romieu [this message]
2006-10-22 15:14 ` Darren Salt
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=20061021201533.GA31768@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=akpm@osdl.org \
--cc=hchacha@users.sourceforge.net \
--cc=jeff@garzik.org \
--cc=linux@youmustbejoking.demon.co.uk \
--cc=netdev@vger.kernel.org \
--cc=syed.azam@hp.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;
as well as URLs for NNTP newsgroup(s).