netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: "David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH RFC v2 3/3] net: phy: allow EEE with SGMII interface modes
Date: Mon, 27 Mar 2017 12:48:26 -0700	[thread overview]
Message-ID: <705b10f9-6a0c-3a35-ddff-04b75c6f80ec@gmail.com> (raw)
In-Reply-To: <20170327194747.GS7909@n2100.armlinux.org.uk>

On 03/27/2017 12:47 PM, Russell King - ARM Linux wrote:
> On Mon, Mar 27, 2017 at 11:03:12AM -0700, Florian Fainelli wrote:
>> On 03/27/2017 10:00 AM, Russell King - ARM Linux wrote:
>>> On Mon, Mar 27, 2017 at 09:47:31AM -0700, Florian Fainelli wrote:
>>>> On 03/27/2017 02:59 AM, Russell King wrote:
>>>>> As EEE is able to work in SGMII mode as well, add it to the list of
>>>>> permissable EEE modes that phy_init_eee() will accept.  This is
>>>>> necessary so that EEE can work with an 88E1512 connected in SGMII mode.
>>>>
>>>> As you mention in your cover letter, we should probably reverse this
>>>> test and make it reject modes where EEE has no chance of being supported
>>>> at all.
>>>
>>> Want me to re-spin?  Any thought on which interface modes we should
>>> explicitly exclude?
>>
>> It actually sounds like we should just kill the check entirely, it does
>> not appear that any of the interface mode would not fundamentally be
>> able to support EEE, because the "lowest" mode we support is MII, and
>> even there it's quite possible to support EEE.
> 
> Right, so it looks like the test reduces down to just:
> 
> 	if (phydev->duplex == DUPLEX_FULL) {
> 
> agreed?

Yes indeed. Thanks!
-- 
Florian

  reply	other threads:[~2017-03-27 19:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27  9:58 [PATCH RFC v2 0/3] phylib EEE updates Russell King - ARM Linux
2017-03-27  9:58 ` [PATCH RFC v2 1/3] net: phy: avoid setting unsupported EEE advertisments Russell King
2017-03-27 18:04   ` Florian Fainelli
2017-03-27  9:58 ` [PATCH RFC v2 2/3] net: phy: restart phy autonegotiation after EEE advertisment change Russell King
2017-03-27 18:03   ` Florian Fainelli
2017-03-27  9:59 ` [PATCH RFC v2 3/3] net: phy: allow EEE with SGMII interface modes Russell King
2017-03-27 16:47   ` Florian Fainelli
2017-03-27 17:00     ` Russell King - ARM Linux
2017-03-27 18:03       ` Florian Fainelli
2017-03-27 19:47         ` Russell King - ARM Linux
2017-03-27 19:48           ` Florian Fainelli [this message]
2017-03-27 20:15             ` Russell King - ARM Linux
2017-03-27 22:42               ` Florian Fainelli
2017-03-27 22:47                 ` Russell King - ARM Linux

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=705b10f9-6a0c-3a35-ddff-04b75c6f80ec@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=linux@armlinux.org.uk \
    --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).