diff options
| author | Alvaro Gamez Machado <alvaro.gamez@hazent.com> | 2018-06-08 12:23:39 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-06-10 21:38:03 +0200 |
| commit | b718e8c8f4f5920aaddc2e52d5e32f494c91129c (patch) | |
| tree | f7147d1b843d1f8219bba61bb006f3e0da6f6fec /Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.txt | |
| parent | socket: close race condition between sock_close() and sockfs_setattr() (diff) | |
| download | linux-b718e8c8f4f5920aaddc2e52d5e32f494c91129c.tar.xz linux-b718e8c8f4f5920aaddc2e52d5e32f494c91129c.zip | |
net: phy: dp83822: use BMCR_ANENABLE instead of BMSR_ANEGCAPABLE for DP83620
DP83620 register set is compatible with the DP83848, but it also supports
100base-FX. When the hardware is configured such as that fiber mode is
enabled, autonegotiation is not possible.
The chip, however, doesn't expose this information via BMSR_ANEGCAPABLE.
Instead, this bit is always set high, even if the particular hardware
configuration makes it so that auto negotiation is not possible [1]. Under
these circumstances, the phy subsystem keeps trying for autonegotiation to
happen, without success.
Hereby, we inspect BMCR_ANENABLE bit after genphy_config_init, which on
reset is set to 0 when auto negotiation is disabled, and so we use this
value instead of BMSR_ANEGCAPABLE.
[1] https://e2e.ti.com/support/interface/ethernet/f/903/p/697165/2571170
Signed-off-by: Alvaro Gamez Machado <alvaro.gamez@hazent.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.txt')
0 files changed, 0 insertions, 0 deletions