From: Andrew Lunn <andrew@lunn.ch>
To: Madalin-cristian Bucur <madalin.bucur@nxp.com>
Cc: Bhaskar Upadhaya <bhaskar.upadhaya@nxp.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Shengzhou Liu <shengzhou.liu@nxp.com>,
York Sun <york.sun@nxp.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
Anji Jagarlmudi <anji.jagarlmudi@nxp.com>,
Calvin Johnson <calvin.johnson@nxp.com>,
Poonam Aggrwal <poonam.aggrwal@nxp.com>,
Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
Subject: Re: [RFC] Support for SGMII 2500
Date: Tue, 28 Nov 2017 15:13:04 +0100 [thread overview]
Message-ID: <20171128141304.GE20797@lunn.ch> (raw)
In-Reply-To: <DB3PR0402MB3849622655E5A7A8283F425CEC3A0@DB3PR0402MB3849.eurprd04.prod.outlook.com>
> Hi Andrew,
>
> Bhaskar is working on enabling a PFE [1] MAC connected to an Aquantia AQR107
> PHY [2] on a LS1012AQDS board. Initially I've indicated 2500Base-X too, but it
> seems the HW actually works in SGMII mode. The QDS boards are lower volume,
> higher spec boards than the RDBs [3], they exercise most of the HW capabilities.
The webpage for the AQR107 lists 2500Base-X, so i assume the issue is
with the MAC? Ideally you want to use 2500Base-X, since this is wider
known.
Anyway, you seem to have a legitimate need for it.
However, i would prefer a different name. The convention is to put the
number first. So PHY_INTERFACE_MODE_2500SGMII.
Andrew
next prev parent reply other threads:[~2017-11-28 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 7:25 [RFC] Support for SGMII 2500 Madalin-cristian Bucur
2017-11-28 7:27 ` Bhaskar Upadhaya
2017-11-28 8:16 ` Prabhakar Kushwaha
2017-11-28 13:30 ` Andrew Lunn
2017-11-28 13:55 ` Madalin-cristian Bucur
2017-11-28 14:13 ` Andrew Lunn [this message]
2017-11-28 15:37 ` Madalin-cristian Bucur
2017-11-28 17:51 ` 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=20171128141304.GE20797@lunn.ch \
--to=andrew@lunn.ch \
--cc=anji.jagarlmudi@nxp.com \
--cc=bhaskar.upadhaya@nxp.com \
--cc=calvin.johnson@nxp.com \
--cc=f.fainelli@gmail.com \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=poonam.aggrwal@nxp.com \
--cc=prabhakar.kushwaha@nxp.com \
--cc=shengzhou.liu@nxp.com \
--cc=u-boot@lists.denx.de \
--cc=york.sun@nxp.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).