1. 19 9月, 2021 1 次提交
  2. 08 9月, 2021 1 次提交
    • N
      net: phylink: Update SFP selected interface on advertising changes · ea269a6f
      Nathan Rossi 提交于
      Currently changes to the advertising state via ethtool do not cause any
      reselection of the configured interface mode after the SFP is already
      inserted and initially configured.
      
      While it is not typical to change the advertised link modes for an
      interface using an SFP in certain use cases it is desirable. In the case
      of a SFP port that is capable of handling both SFP and SFP+ modules it
      will automatically select between 1G and 10G modes depending on the
      supported mode of the SFP. However if the SFP module is capable of
      working in multiple modes (e.g. a SFP+ DAC that can operate at 1G or
      10G), one end of the cable may be attached to a SFP 1000base-x port thus
      the SFP+ end must be manually configured to the 1000base-x mode in order
      for the link to be established.
      
      This change causes the ethtool setting of advertised mode changes to
      reselect the interface mode so that the link can be established.
      Additionally when a module is inserted the advertising mode is reset to
      match the supported modes of the module.
      Signed-off-by: NNathan Rossi <nathan.rossi@digi.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ea269a6f
  3. 07 9月, 2021 1 次提交
  4. 21 7月, 2021 1 次提交
  5. 20 7月, 2021 1 次提交
  6. 17 6月, 2021 2 次提交
  7. 13 6月, 2021 1 次提交
  8. 12 6月, 2021 2 次提交
  9. 16 3月, 2021 2 次提交
  10. 17 2月, 2021 1 次提交
  11. 18 11月, 2020 1 次提交
  12. 28 10月, 2020 1 次提交
  13. 01 9月, 2020 3 次提交
  14. 24 8月, 2020 1 次提交
  15. 22 7月, 2020 14 次提交
  16. 26 6月, 2020 2 次提交
  17. 24 6月, 2020 2 次提交
  18. 20 6月, 2020 1 次提交
  19. 27 5月, 2020 1 次提交
  20. 19 5月, 2020 1 次提交
    • D
      net: phy: simplify phy_link_change arguments · a307593a
      Doug Berger 提交于
      This function was introduced to allow for different handling of
      link up and link down events particularly with regard to the
      netif_carrier. The third argument do_carrier allowed the flag to
      be left unchanged.
      
      Since then the phylink has introduced an implementation that
      completely ignores the third parameter since it never wants to
      change the flag and the phylib always sets the third parameter
      to true so the flag is always changed.
      
      Therefore the third argument (i.e. do_carrier) is no longer
      necessary and can be removed. This also means that the phylib
      phy_link_down() function no longer needs its second argument.
      Signed-off-by: NDoug Berger <opendmb@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a307593a