From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Koki Sanagi <sanagi.koki@jp.fujitsu.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"Wyborny, Carolyn" <carolyn.wyborny@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"Skidmore, Donald C" <donald.c.skidmore@intel.com>,
"Rose, Gregory V" <gregory.v.rose@intel.com>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
"Ronciak, John" <john.ronciak@intel.com>
Subject: Re: [PATCH net-next v2] igb: reset PHY after recovering from PHY power down
Date: Wed, 21 Dec 2011 22:46:04 -0800 [thread overview]
Message-ID: <1324536364.2327.39.camel@jtkirshe-mobl> (raw)
In-Reply-To: <4EEE9248.8020009@jp.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
On Sun, 2011-12-18 at 17:24 -0800, Koki Sanagi wrote:
> According to 82576_Datasheet.pdf, PHY setting is lost after PHY power
> down.
> So resetting PHY is needed when recovering from PHY power down to set
> a default
> setting to PHY register.
> Owing to this lack, NIC doesn't link up in some rare situation.
>
> Signed-off-by: Koki Sanagi <sanagi.koki@jp.fujitsu.com>
I have added this patch to my queue. Thanks Koki!
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-12-22 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 1:24 [PATCH net-next v2] igb: reset PHY after recovering from PHY power down Koki Sanagi
2011-12-20 16:05 ` Wyborny, Carolyn
2011-12-22 6:46 ` Jeff Kirsher [this message]
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=1324536364.2327.39.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=davem@davemloft.net \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gregory.v.rose@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=sanagi.koki@jp.fujitsu.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).