diff options
| author | David S. Miller <davem@davemloft.net> | 2017-05-30 19:42:28 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-05-30 19:42:28 +0300 |
| commit | ae803902c71e4eb340a0d3178d65f757662b5298 (patch) | |
| tree | 8a67ce9ca2e09db703dc42d293efa1bed0051d28 /tools/perf/scripts/python | |
| parent | eb67e07ac63ca362d421bc44766140d9e008914d (diff) | |
| parent | 303d97713cedecad337260815690cd244e5ee4dc (diff) | |
| download | linux-ae803902c71e4eb340a0d3178d65f757662b5298.tar.xz | |
Merge branch 'net-phy-Support-managed-Cortina-phys'
Bogdan Purcareata says:
====================
net: phy: Support managed Cortina phys
So far, the Cortina family phys (CS4340 in this particular case) are only
supported in fixed link mode (via fixed_phy_register). The generic 10G
phy driver does not work well with the phylib state machine, when the phy
is registered via of_phy_connect. This prohibits the user from describing the
phy nodes in the device tree.
In order to support this scenario, and to properly describe the board
device tree, add a minimal Cortina driver that reads the status from the
right register. With the generic 10G C45 driver, the kernel will print
messages like:
[ 0.226521] mdio_bus 8b96000: Error while reading PHY16 reg at 1.6
[ 0.232780] mdio_bus 8b96000: Error while reading PHY16 reg at 1.5
v3 -> v4:
- Add trademark info.
- Minor documentation entry consistency nit.
v2 -> v3:
- Add documentation entry.
v1 -> v2:
- Change approach for getting the phy_id from hacking get_phy_c45_ids to
describing the device in the device tree via ethernet-phy-id.
More patch version changes per individual patches.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
