From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Jose Abreu <Jose.Abreu@synopsys.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: Clause 73 and USXGMII
Date: Thu, 8 Aug 2019 09:26:26 +0100 [thread overview]
Message-ID: <20190808082626.GB5193@shell.armlinux.org.uk> (raw)
In-Reply-To: <BN8PR12MB3266A710111427071814D371D3D70@BN8PR12MB3266.namprd12.prod.outlook.com>
Hi,
Have you tried enabling debug mode in phylink (add #define DEBUG at the
top of the file) ?
Thanks.
On Thu, Aug 08, 2019 at 08:17:29AM +0000, Jose Abreu wrote:
> ++ PHY Experts
>
> From: Jose Abreu <joabreu@synopsys.com>
> Date: Aug/07/2019, 16:46:23 (UTC+00:00)
>
> > Hello,
> >
> > I've some sample code for Clause 73 support using Synopsys based XPCS
> > but I would like to clarify some things that I noticed.
> >
> > I'm using USXGMII as interface and a single SERDES that operates at 10G
> > rate but MAC side is working at 2.5G. Maximum available bandwidth is
> > therefore 2.5Gbps.
> >
> > So, I configure USXGMII for 2.5G mode and it works but if I try to limit
> > the autoneg abilities to 2.5G max then it never finishes:
> > # ethtool enp4s0
> > Settings for enp4s0:
> > Supported ports: [ ]
> > Supported link modes: 1000baseKX/Full
> > 2500baseX/Full
> > Supported pause frame use: Symmetric Receive-only
> > Supports auto-negotiation: Yes
> > Supported FEC modes: Not reported
> > Advertised link modes: 1000baseKX/Full
> > 2500baseX/Full
> > Advertised pause frame use: Symmetric Receive-only
> > Advertised auto-negotiation: Yes
> > Advertised FEC modes: Not reported
> > Speed: Unknown!
> > Duplex: Unknown! (255)
> > Port: MII
> > PHYAD: 0
> > Transceiver: internal
> > Auto-negotiation: on
> > Supports Wake-on: ug
> > Wake-on: d
> > Current message level: 0x0000003f (63)
> > drv probe link timer ifdown ifup
> > Link detected: no
> >
> > When I do not limit autoneg and I say that maximum limit is 10G then I
> > get Link Up and autoneg finishes with this outcome:
> > # ethtool enp4s0
> > Settings for enp4s0:
> > Supported ports: [ ]
> > Supported link modes: 1000baseKX/Full
> > 2500baseX/Full
> > 10000baseKX4/Full
> > 10000baseKR/Full
> > Supported pause frame use: Symmetric Receive-only
> > Supports auto-negotiation: Yes
> > Supported FEC modes: Not reported
> > Advertised link modes: 1000baseKX/Full
> > 2500baseX/Full
> > 10000baseKX4/Full
> > 10000baseKR/Full
> > Advertised pause frame use: Symmetric Receive-only
> > Advertised auto-negotiation: Yes
> > Advertised FEC modes: Not reported
> > Link partner advertised link modes: 1000baseKX/Full
> > 2500baseX/Full
> > 10000baseKX4/Full
> > 10000baseKR/Full
> > Link partner advertised pause frame use: Symmetric Receive-only
> > Link partner advertised auto-negotiation: Yes
> > Link partner advertised FEC modes: Not reported
> > Speed: 2500Mb/s
> > Duplex: Full
> > Port: MII <- Never mind this, it's a SW issue
> > PHYAD: 0
> > Transceiver: internal
> > Auto-negotiation: on
> > Supports Wake-on: ug
> > Wake-on: d
> > Current message level: 0x0000003f (63)
> > drv probe link timer ifdown ifup
> > Link detected: yes
> >
> > I was expecting that, as MAC side is limited to 2.5G, I should set in
> > phylink the correct capabilities and then outcome of autoneg would only
> > have up to 2.5G modes. Am I wrong ?
> >
> > ---
> > Thanks,
> > Jose Miguel Abreu
>
>
> ---
> Thanks,
> Jose Miguel Abreu
>
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-08-08 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 15:46 Clause 73 and USXGMII Jose Abreu
2019-08-08 8:17 ` Jose Abreu
2019-08-08 8:26 ` Russell King - ARM Linux admin [this message]
2019-08-08 9:02 ` Jose Abreu
2019-08-08 9:23 ` Russell King - ARM Linux admin
2019-08-08 11:45 ` Jose Abreu
2019-08-08 12:09 ` Russell King - ARM Linux admin
2019-08-09 18:42 ` Jose Abreu
2019-08-09 19:25 ` Russell King - ARM Linux admin
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=20190808082626.GB5193@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Jose.Abreu@synopsys.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.