From: Guenter Roeck <linux@roeck-us.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFT PATCH 1/2] net: dsa: mv88e6xxx: Add EEE support
Date: Mon, 23 Feb 2015 18:29:53 -0800 [thread overview]
Message-ID: <54EBE221.2000703@roeck-us.net> (raw)
In-Reply-To: <20150223.171947.1925831716804927748.davem@davemloft.net>
On 02/23/2015 02:19 PM, David Miller wrote:
> From: Guenter Roeck <linux@roeck-us.net>
> Date: Mon, 23 Feb 2015 08:26:09 -0800
>
>> + /* Don't call phy_init_eee for now. It fails if the link is down,
>> + * but that should not really be a reason to fail configuration.
>> + */
>
> I think there is some confusion about phy_init_eee().
>
> You invoke it after a link has been established. Because programming
> the MDIO registers that turn on EEE can only be done if the link
> is configured in a certain way.
>
> If you look at stmmac, it invokes phy_init_eee() via it's adjust_link
> callback passed to phy_connect(). This is basically how I would
> expect it to be used, in that any time a link parameter changes we
> rerun phy_init_eee() to check the link partner registers, duplex
> state, etc.
>
> SXGBE on the other hand seems to not be using phy_init_eee() properly,
> it only invokes it once per device open and that makes no sense at all
> because then you're stuck with the eee state resulting from the link
> state at open time.
>
That explains a lot. I suspect the use in bcm_sf2 and bcmgenet is also
not as intended.
Thanks,
Guenter
next prev parent reply other threads:[~2015-02-24 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 16:26 [RFT PATCH 1/2] net: dsa: mv88e6xxx: Add EEE support Guenter Roeck
2015-02-23 16:26 ` [RFT PATCH 2/2] net: dsa: mv88e6352: Add support for EEE Guenter Roeck
2015-02-23 17:45 ` [RFT PATCH 1/2] net: dsa: mv88e6xxx: Add EEE support Florian Fainelli
2015-02-23 18:52 ` Guenter Roeck
2015-02-23 21:25 ` Florian Fainelli
2015-02-23 22:19 ` David Miller
2015-02-24 2:29 ` Guenter Roeck [this message]
2015-02-24 2:34 ` Florian Fainelli
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=54EBE221.2000703@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).