From: Andrew Lunn <andrew@lunn.ch>
To: shh.xie@gmail.com
Cc: devicetree@vger.kernel.org, netdev@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, f.fainelli@gmail.com,
davem@davemloft.net, Shaohui Xie <Shaohui.Xie@freescale.com>
Subject: Re: [PATCH 1/3][v2] net: phy: introduce 1000BASE-KX and 10GBASE-KR
Date: Thu, 14 Jan 2016 17:44:18 +0100 [thread overview]
Message-ID: <20160114164418.GD19773@lunn.ch> (raw)
In-Reply-To: <1452759839-9874-1-git-send-email-shh.xie@gmail.com>
On Thu, Jan 14, 2016 at 04:23:59PM +0800, shh.xie@gmail.com wrote:
> From: Shaohui Xie <Shaohui.Xie@freescale.com>
>
> This commit adds necessary definitions for the PHY layer to recognize
> backplane Ethernet 1000BASE-KX and 10GBASE-KR as valid PHY interfaces,
> "1000base-kx" for 1000BASE-KX, "10gbase-kr" for 10GBASE-KR.
>
> Signed-off-by: Shaohui Xie <Shaohui.Xie@freescale.com>
> ---
> changes in v2:
> new patch.
>
> Documentation/devicetree/bindings/net/ethernet.txt | 4 ++--
> include/linux/phy.h | 6 ++++++
> 2 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/net/ethernet.txt b/Documentation/devicetree/bindings/net/ethernet.txt
> index 5d88f37..1166a5c 100644
> --- a/Documentation/devicetree/bindings/net/ethernet.txt
> +++ b/Documentation/devicetree/bindings/net/ethernet.txt
> @@ -11,8 +11,8 @@ The following properties are common to the Ethernet controllers:
> the maximum frame size (there's contradiction in ePAPR).
> - phy-mode: string, operation mode of the PHY interface; supported values are
> "mii", "gmii", "sgmii", "qsgmii", "tbi", "rev-mii", "rmii", "rgmii", "rgmii-id",
> - "rgmii-rxid", "rgmii-txid", "rtbi", "smii", "xgmii"; this is now a de-facto
> - standard property;
> + "rgmii-rxid", "rgmii-txid", "rtbi", "smii", "xgmii", "1000base-kx", "10gbase-kr";
> + this is now a de-facto standard property;
I know very little about this, so i'm just asking a question. None of
the other interface modes contain a bit rate. So is the bit rate
needed for your two new modes?
With a bit of googling, K means copper backplane, X means 4B/5B and R
means 64B/66B. Could there be a 10Gbps KX? a 1GBps KR? Do we actually
need the speed here, or is kx and kr sufficient?
Thanks
Andrew
next prev parent reply other threads:[~2016-01-14 17:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 8:23 [PATCH 1/3][v2] net: phy: introduce 1000BASE-KX and 10GBASE-KR shh.xie
2016-01-14 8:23 ` shh.xie
2016-01-14 16:44 ` Andrew Lunn [this message]
2016-01-15 4:01 ` Shaohui Xie
2016-01-15 4:01 ` Shaohui Xie
2016-01-15 22:57 ` Sebastian Hesselbarth
2016-01-16 2:59 ` Florian Fainelli
2016-01-16 2:59 ` Florian Fainelli
2016-01-18 7:23 ` Shaohui Xie
2016-01-18 7:23 ` Shaohui Xie
2016-01-18 8:05 ` Sebastian Hesselbarth
2016-01-18 8:50 ` Shaohui Xie
2016-01-18 8:50 ` Shaohui Xie
2016-01-18 15:15 ` Andrew Lunn
2016-01-18 15:15 ` Andrew Lunn
2016-01-19 5:00 ` Shaohui Xie
2016-01-19 5:00 ` Shaohui Xie
2016-01-21 21:12 ` Andrew Lunn
2016-01-21 21:12 ` Andrew Lunn
2016-01-22 8:15 ` Shaohui Xie
2016-01-22 8:15 ` Shaohui Xie
2016-01-22 9:26 ` Sebastian Hesselbarth
2016-01-22 9:26 ` Sebastian Hesselbarth
2016-01-22 10:05 ` Shaohui Xie
2016-01-22 10:05 ` Shaohui Xie
2016-01-22 14:09 ` Shaohui Xie
2016-01-22 14:09 ` Shaohui Xie
2016-01-22 14:38 ` Andrew Lunn
2016-01-22 14:38 ` Andrew Lunn
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=20160114164418.GD19773@lunn.ch \
--to=andrew@lunn.ch \
--cc=Shaohui.Xie@freescale.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=shh.xie@gmail.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 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.