diff options
| author | David S. Miller | 2018-11-23 20:14:48 +0100 |
|---|---|---|
| committer | David S. Miller | 2018-11-23 20:14:48 +0100 |
| commit | 2882b06ddaa5fbfaf1e65c1beaed8819fb7a0440 (patch) | |
| tree | 93984ff1c11cf410a8bfdac9b1ca27180b37183f /drivers/soc/fsl/qbman/qman.c | |
| parent | cxgb4: use new fw interface to get the VIN and smt index (diff) | |
| parent | ravb: Clean up duplex handling (diff) | |
| download | kernel-qcow2-linux-2882b06ddaa5fbfaf1e65c1beaed8819fb7a0440.tar.gz kernel-qcow2-linux-2882b06ddaa5fbfaf1e65c1beaed8819fb7a0440.tar.xz kernel-qcow2-linux-2882b06ddaa5fbfaf1e65c1beaed8819fb7a0440.zip | |
Merge branch 'ravb-Duplex-handling-update-V3'
Magnus Damm says:
====================
ravb: Duplex handling update V3
[PATCH v3 01/02] ravb: Do not announce HDX as supported
[PATCH v3 02/02] ravb: Clean up duplex handling
This series is V3 of duplex handling improvements for the Ethernet-AVB driver.
Previous versions of this series have been posted to linux-renesas-soc as RFC
so V3 is the first actual version to make it to netdev.
Based on the latest data sheet for R-Car Gen3 [1] and R-Car Gen2 [2]
the following information is part of the EthernetAVB-IF overview page:
Transfer speed: Supports transfer at 100 and 1000 Mbps
Mode: Full-duplex mode
It seems that the driver implementation is not matching the information
provided in the friendly data sheet, and on top of this during run-time
when changing PHY configuration of the link partner the Ethernet-AVB PHY
seems to want to announce unsupported modes.
[1] R-Car Series, 3rd Generation Rev.1.00 (Apr 2018)
[2] R-Car Series, 2nd Generation Rev.2.00 (Feb 2016)
Changes since V2:
- Updated patch 1/2 to make use of phy_remove_link_mode()
- Added Reviewed-by from Sergei - thanks!
Changes since V1:
- Updated patches to reflect input from Sergei and Geert - thanks!
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/soc/fsl/qbman/qman.c')
0 files changed, 0 insertions, 0 deletions