From: Andrew Lunn <andrew@lunn.ch>
To: Shaohui Xie <shaohui.xie@nxp.com>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"shh.xie@gmail.com" <shh.xie@gmail.com>,
"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>
Subject: Re: [PATCH 1/3][v2] net: phy: introduce 1000BASE-KX and 10GBASE-KR
Date: Fri, 22 Jan 2016 15:38:12 +0100 [thread overview]
Message-ID: <20160122143812.GP9991@lunn.ch> (raw)
In-Reply-To: <VI1PR04MB1664B669925ADB21D3A13594E8C40@VI1PR04MB1664.eurprd04.prod.outlook.com>
> The reason I mentioned maybe I should put the backplane property in
> fsl's binding is because the backplane implementation is really
> vendor specific, it's heavily relay how hardware implements the
> feature, maybe another vendor's hardware only needs a boolean
> property for driver to tell it should work in backplane, hardware
> can deal with different modes, or even no any special property
> needed if the hardware is strong enough to handle any connections, I
> cannot assume. But I know what fsl's hardware needs to support
> backplane.
This is the key point really. We don't really care about the Freescale
PCS. We want a generic solution for 1000BASE-KX and 10GBASE-KR,
independent of who makes it, Marvell, Micrel, Broadcom, or Acme.
So, what generic properties are needed for 1000BASE-KX and 10GBASE-KR?
Properties that most/all manufactures are likely to need?
Andrew
prev parent reply other threads:[~2016-01-22 14:38 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
2016-01-15 4:01 ` Shaohui Xie
2016-01-15 22:57 ` Sebastian Hesselbarth
2016-01-16 2:59 ` Florian Fainelli
2016-01-18 7:23 ` Shaohui Xie
2016-01-18 8:05 ` Sebastian Hesselbarth
2016-01-18 8:50 ` Shaohui Xie
2016-01-18 15:15 ` Andrew Lunn
2016-01-19 5:00 ` Shaohui Xie
2016-01-21 21:12 ` Andrew Lunn
2016-01-22 8:15 ` Shaohui Xie
2016-01-22 9:26 ` Sebastian Hesselbarth
2016-01-22 10:05 ` Shaohui Xie
2016-01-22 14:09 ` Shaohui Xie
2016-01-22 14:38 ` Andrew Lunn [this message]
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=20160122143812.GP9991@lunn.ch \
--to=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=sebastian.hesselbarth@gmail.com \
--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).