From: Chunhao Lin <hau@realtek.com>
To: <netdev@vger.kernel.org>
Cc: <nic_swsd@realtek.com>, <linux-kernel@vger.kernel.org>,
Chunhao Lin <hau@realtek.com>
Subject: [PATCH net-next 5/9] r8169:update rtl8168fb ephy parameter
Date: Wed, 10 Dec 2014 00:45:59 +0800 [thread overview]
Message-ID: <1418143563-7652-6-git-send-email-hau@realtek.com> (raw)
In-Reply-To: <1418143563-7652-1-git-send-email-hau@realtek.com>
Update rtl8168fb ephy parameter to improve pcie compatibility.
Signed-off-by: Chunhao Lin <hau@realtek.com>
---
drivers/net/ethernet/realtek/r8169.c | 28 ++++++++++++++++++++++++++--
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/realtek/r8169.c b/drivers/net/ethernet/realtek/r8169.c
index bb5a3ba..2ff8b73 100644
--- a/drivers/net/ethernet/realtek/r8169.c
+++ b/drivers/net/ethernet/realtek/r8169.c
@@ -5889,7 +5889,9 @@ static void rtl_hw_start_8168f_1(struct rtl8169_private *tp)
{ 0x06, 0x00c0, 0x0020 },
{ 0x08, 0x0001, 0x0002 },
{ 0x09, 0x0000, 0x0080 },
- { 0x19, 0x0000, 0x0224 }
+ { 0x19, 0x0000, 0x0224 },
+ { 0x00, 0x0000, 0x0008 },
+ { 0x0c, 0x3df0, 0x0200 }
};
rtl_hw_start_8168f(tp);
@@ -5902,6 +5904,26 @@ static void rtl_hw_start_8168f_1(struct rtl8169_private *tp)
RTL_W8(EEE_LED, RTL_R8(EEE_LED) & ~0x07);
}
+static void rtl_hw_start_8168f_2(struct rtl8169_private *tp)
+{
+ void __iomem *ioaddr = tp->mmio_addr;
+ static const struct ephy_info e_info_8168f_2[] = {
+ { 0x09, 0x0000, 0x0080 },
+ { 0x19, 0x0000, 0x0224 },
+ { 0x00, 0x0000, 0x0008 },
+ { 0x0c, 0x3df0, 0x0200 }
+ };
+
+ rtl_hw_start_8168f(tp);
+
+ rtl_ephy_init(tp, e_info_8168f_2, ARRAY_SIZE(e_info_8168f_2));
+
+ rtl_w0w1_eri(tp, 0x0d4, ERIAR_MASK_0011, 0x0c00, 0xff00, ERIAR_EXGMAC);
+
+ /* Adjust EEE LED frequency */
+ RTL_W8(EEE_LED, RTL_R8(EEE_LED) & ~0x07);
+}
+
static void rtl_hw_start_8411(struct rtl8169_private *tp)
{
static const struct ephy_info e_info_8411[] = {
@@ -6320,9 +6342,11 @@ static void rtl_hw_start_8168(struct net_device *dev)
break;
case RTL_GIGA_MAC_VER_35:
- case RTL_GIGA_MAC_VER_36:
rtl_hw_start_8168f_1(tp);
break;
+ case RTL_GIGA_MAC_VER_36:
+ rtl_hw_start_8168f_2(tp);
+ break;
case RTL_GIGA_MAC_VER_38:
rtl_hw_start_8411(tp);
--
1.9.1
next prev parent reply other threads:[~2014-12-09 16:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 16:45 [PATCH net-next 0/9] r8169:update hardware ephy parameter Chunhao Lin
2014-12-09 16:45 ` [PATCH net-next 1/9] r8169:update rtl8168g " Chunhao Lin
2014-12-09 16:45 ` [PATCH net-next 2/9] r8169:update rtl8168gu " Chunhao Lin
2014-12-09 16:45 ` [PATCH net-next 3/9] r8169:update rtl8411b " Chunhao Lin
2014-12-09 16:45 ` [PATCH net-next 4/9] r8169:update rtl8411 " Chunhao Lin
2014-12-09 16:45 ` Chunhao Lin [this message]
2014-12-09 23:48 ` [PATCH net-next 5/9] r8169:update rtl8168fb " Francois Romieu
2014-12-09 16:46 ` [PATCH net-next 6/9] r8169:update rtl8168e-vl " Chunhao Lin
2014-12-09 16:46 ` [PATCH net-next 7/9] r8169:update rtl8168dp " Chunhao Lin
2014-12-09 23:50 ` Francois Romieu
2014-12-09 16:46 ` [PATCH net-next 8/9] r8169:update rtl8105e " Chunhao Lin
2014-12-09 16:46 ` [PATCH net-next 9/9] r8169:update rtl8402 " Chunhao Lin
2014-12-09 23:35 ` [PATCH net-next 0/9] r8169:update hardware " David Miller
2014-12-10 7:17 ` Hau
2014-12-09 23:47 ` Francois Romieu
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=1418143563-7652-6-git-send-email-hau@realtek.com \
--to=hau@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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