public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Arthur Jones <ajones@riverbed.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] e1000e: workaround missing power down mii control bit on 82571
Date: Thu, 16 Dec 2010 18:56:37 +0000	[thread overview]
Message-ID: <1292525797.3253.8.camel@bwh-desktop> (raw)
In-Reply-To: <20101216182847.GA14985@ajones-laptop.nbttech.com>

On Thu, 2010-12-16 at 10:28 -0800, Arthur Jones wrote:
> Hi Jeff,  Re-sending w/ proper netdev email
> address.  Sorry about that...
> 
> Arthur
> 
> ---
> 
> On 82571 only, AFAICT, the PHY does not seem to
> store the MII control register 0 bit 11 (power
> down PHY). So that when we power down the PHY
> on dev_close() and then run ethtool on the closed
> dev, we end up turning the PHY back on even though
> the interface is down.  This pretty easy to repro:
> 
> $ ethtool -s eth0 wol d
> $ ifconfig eth0 up
> $ mii-tool eth0
> eth0: negotiated 100baseTx-FD, link ok
> $ ifconfig eth0 down
> $ mii-tool eth0
> eth0: no link
> $ ethtool -s eth0 autoneg on  (doesn't really matter what we do here)
> $ mii-tool eth0
> eth0: negotiated 100baseTx-FD, link ok (this should be: eth0: no link)
> 
> We fix this by tracking the power down bit that we
> write to the PHY control register and re-inserting
> it when we read it.
[...]

Adding this special case into MDIO access seems like a really nasty
hack.  Surely the callers that set the control register should take care
of this.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.


  reply	other threads:[~2010-12-16 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16 18:28 [PATCH] e1000e: workaround missing power down mii control bit on 82571 Arthur Jones
2010-12-16 18:56 ` Ben Hutchings [this message]
2010-12-16 19:04   ` Allan, Bruce W
2010-12-16 19:28     ` Allan, Bruce W
2010-12-16 20:04       ` Arthur Jones
2010-12-16 22:14         ` Arthur Jones
2010-12-17  1:46           ` Allan, Bruce W
2010-12-17 14:04             ` Arthur Jones
2010-12-17 15:53               ` Allan, Bruce W
2010-12-20 15:33                 ` Arthur Jones
2010-12-22 20:25                   ` Allan, Bruce W

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=1292525797.3253.8.camel@bwh-desktop \
    --to=bhutchings@solarflare.com \
    --cc=ajones@riverbed.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=netdev@vger.kernel.org \
    /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