summaryrefslogtreecommitdiff
path: root/include/linux/mlx5/mlx5_ifc.h
diff options
context:
space:
mode:
authorPaolo Abeni <pabeni@redhat.com>2023-07-25 16:02:05 +0300
committerPaolo Abeni <pabeni@redhat.com>2023-07-25 16:02:05 +0300
commit9e10fb4cab17d646f440e63751e2a379f05a250a (patch)
treefce474b9fd0a9ec9de8d1adf3ae7dbb49f93c77d /include/linux/mlx5/mlx5_ifc.h
parentec87f05402f592d27507e1aa6b2fd21c486f2cc0 (diff)
parentc5714f68a76bcad3d2dbaafc5a7e98096f3b4c75 (diff)
downloadlinux-9e10fb4cab17d646f440e63751e2a379f05a250a.tar.xz
Merge branch 'remove-legacy-phylink-behaviour'
Russell King says: ==================== Remove legacy phylink behaviour This series removes the - as far as I can tell - unreachable code in mtk_eth_soc that relies upon legacy phylink behaviour, and then removes the support in phylink for this legacy behaviour. Patch 1 removes the clocking configuration from mtk_eth_soc for non- TRGMII, non-serdes based interface modes, and disables those interface modes prior to phylink configuration. Patch 2 removes the mac_pcs_get_state() method from mtk_eth_soc which I believe is also not used - mtk_eth_soc appears not to be used with SFPs (which would use a kind of in-band mode) nor does any DT appear to specify in-band mode for any non-serdes based interface mode. With both of those dealt with, the kernel is now free of any driver relying on the phylink legacy mode. Therefore, patch 3 removes support for this. Finally, with the advent of a new driver being submitted today that makes use of state->speed in the mac_config() path, patch 4 ensures that any phylink_link_state member that should not be used in mac_config is either cleared or set to an invalid value. ==================== Link: https://lore.kernel.org/r/ZLw8DoRskRXLQK37@shell.armlinux.org.uk Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'include/linux/mlx5/mlx5_ifc.h')
0 files changed, 0 insertions, 0 deletions