diff options
author | 2022-06-23 20:26:47 -0700 | |
---|---|---|
committer | 2022-06-23 20:26:48 -0700 | |
commit | 0aeaaa8d9769393e9b76efce2bf051ae28d59ee7 (patch) | |
tree | 5ab7983915bb76bdec57803cf00256ccab66bf6d /drivers/net/phy/bcm-phy-lib.h | |
parent | Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (diff) | |
parent | net: dsa: mv88e6xxx: get rid of SPEED_MAX setting (diff) | |
download | linux-0aeaaa8d9769393e9b76efce2bf051ae28d59ee7.tar.gz linux-0aeaaa8d9769393e9b76efce2bf051ae28d59ee7.tar.bz2 linux-0aeaaa8d9769393e9b76efce2bf051ae28d59ee7.zip |
Merge branch 'net-dsa-mv88e6xxx-get-rid-of-speed_max'
Russell King says:
====================
net: dsa: mv88e6xxx: get rid of SPEED_MAX
This series does two things:
1. it gets rid of mv88e6065_port_set_speed_duplex() which is completely
unused (do we support this device? I couldn't find it in the tables
in chip.c) This has a max speed of 200Mbps which we don't support.
2. get rid of the SPEED_MAX constant, which is used to configure a DSA
or CPU port to their maximum speed during initialisation. We no
longer need this as we can derive the maximum port speed from the
mac_capabilities instead.
The reason for making this change is in preparation for phylink to be
used by DSA for CPU ports. This omission has come back to bite us with
the conversion of DSA drivers to phylink_pcs, since phylink_pcs won't
get used unless phylink is being used. Particularly with this driver,
it is very common for DT descriptions to omit the fixed-link details
which means "use maximum speed".
It will eventually be necessary to hoist the selection of "max speed"
into the DSA layer (trivial) and also have a way for the DSA driver
to tell the DSA layer which interface it should be using for these
ports.
====================
Link: https://lore.kernel.org/r/YrGQBssOvQBZiDS4@shell.armlinux.org.uk
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/net/phy/bcm-phy-lib.h')
0 files changed, 0 insertions, 0 deletions