From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Shaohui Xie <shaohui.xie@nxp.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
"shh.xie@gmail.com" <shh.xie@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"davem@davemloft.net" <davem@davemloft.net>,
Shaohui Xie <Shaohui.Xie@freescale.com>
Subject: Re: [PATCH 1/3][v2] net: phy: introduce 1000BASE-KX and 10GBASE-KR
Date: Mon, 18 Jan 2016 09:05:38 +0100 [thread overview]
Message-ID: <569C9CD2.10301@gmail.com> (raw)
In-Reply-To: <VI1PR04MB16645A2F24DB515D86136BE2E8C00@VI1PR04MB1664.eurprd04.prod.outlook.com>
On 18.01.2016 08:23, Shaohui Xie wrote:
>>> If you look at the list of possible values for "phy-mode" you'd see
>>> that none of it describes a PHY-to-PHY connection but all are for
>>> MAC-to-PHY connections. Also, names above suggest it already: MII is
>>> short for media _independent_ interface.
>>>
>>> I copy Andrew's concerns and think that neither 10000base-kx nor
>>> 10gbase-kr belong in the list of phy-mode properties.
>>
>> I concur with that as well, if the phy connection does not really matter here,
>> or does not seem like a good fit, maybe we should have a different property, or
>> just define the hardware interface a little differently?
> Right, 'phy-mode' is not a good fit for backplanes, how about a new property like
> 'backplane-mode' or something, like below:
Hmm. We already have a speed property for that you can use for
1000, 10000, 40000. Leaves the media-type, e.g. copper or whatever.
Currently, you fail to convince me that it is required to describe
the media type at all. We have come a long way with different media
without describing the PHY-to-PHY media type.
What makes the backplane setup so special?
Sebastian
>
> --- a/Documentation/devicetree/bindings/net/phy.txt
> +++ b/Documentation/devicetree/bindings/net/phy.txt
> @@ -33,6 +33,9 @@ Optional Properties:
> - broken-turn-around: If set, indicates the PHY device does not correctly
> release the turn around line low at the end of a MDIO transaction.
>
> +- backplane-mode: string, operation mode of the backplane PHY;
> + must be "1000base-kx" for 1000BASE-KX, or "10gbase-kr" for 10GBASE-KR.
> +
> Example:
>
> ethernet-phy@0 {
>
> Thank you!
>
> Shaohui
>
next prev parent reply other threads:[~2016-01-18 8:05 UTC|newest]
Thread overview: 16+ 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 16:44 ` Andrew Lunn
[not found] ` <20160114164418.GD19773-g2DYL2Zd6BY@public.gmane.org>
2016-01-15 4:01 ` Shaohui Xie
2016-01-15 22:57 ` Sebastian Hesselbarth
[not found] ` <56997951.90304-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-01-16 2:59 ` Florian Fainelli
[not found] ` <5699B211.5070602-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-01-18 7:23 ` Shaohui Xie
2016-01-18 8:05 ` Sebastian Hesselbarth [this message]
2016-01-18 8:50 ` Shaohui Xie
[not found] ` <VI1PR04MB1664AB0E483F01F1641059FFE8C00-mr6QIVyDiCHTAO9RNConP89NdZoXdze2vxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2016-01-18 15:15 ` Andrew Lunn
[not found] ` <20160118151500.GD923-g2DYL2Zd6BY@public.gmane.org>
2016-01-19 5:00 ` Shaohui Xie
[not found] ` <VI1PR04MB1664DFBC53F08C5CE7EBF22AE8C10-mr6QIVyDiCHTAO9RNConP89NdZoXdze2vxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2016-01-21 21:12 ` Andrew Lunn
2016-01-22 8:15 ` Shaohui Xie
[not found] ` <VI1PR04MB1664BAFB4EE494CB14830BCCE8C40-mr6QIVyDiCHTAO9RNConP89NdZoXdze2vxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2016-01-22 9:26 ` Sebastian Hesselbarth
2016-01-22 10:05 ` Shaohui Xie
[not found] ` <VI1PR04MB1664AD70D26C452F5A33595AE8C40-mr6QIVyDiCHTAO9RNConP89NdZoXdze2vxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2016-01-22 14:09 ` Shaohui Xie
[not found] ` <VI1PR04MB1664B669925ADB21D3A13594E8C40-mr6QIVyDiCHTAO9RNConP89NdZoXdze2vxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
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=569C9CD2.10301@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=Shaohui.Xie@freescale.com \
--cc=andrew@lunn.ch \
--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=shaohui.xie@nxp.com \
--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 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).