1. 14 11月, 2020 1 次提交
  2. 28 9月, 2020 1 次提交
  3. 14 9月, 2020 1 次提交
  4. 11 9月, 2020 1 次提交
    • A
      net: mvpp2: ptp: Fix unused variables · cdd0a379
      Alex Dewar 提交于
      In the functions mvpp2_isr_handle_xlg() and
      mvpp2_isr_handle_gmac_internal(), the bool variable link is assigned a
      true value in the case that a given bit of val is set. However, if the
      bit is unset, no value is assigned to link and it is then passed to
      mvpp2_isr_handle_link() without being initialised. Fix by assigning to
      link the value of the bit test.
      
      Build-tested on x86.
      
      Fixes: 36cfd3a6 ("net: mvpp2: restructure "link status" interrupt handling")
      Signed-off-by: NAlex Dewar <alex.dewar90@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      cdd0a379
  5. 10 9月, 2020 6 次提交
  6. 04 9月, 2020 6 次提交
  7. 24 8月, 2020 1 次提交
  8. 04 8月, 2020 1 次提交
  9. 26 7月, 2020 1 次提交
  10. 08 7月, 2020 1 次提交
  11. 04 7月, 2020 5 次提交
  12. 21 6月, 2020 4 次提交
  13. 19 6月, 2020 1 次提交
  14. 17 6月, 2020 1 次提交
  15. 16 6月, 2020 1 次提交
  16. 07 5月, 2020 1 次提交
  17. 15 3月, 2020 1 次提交
  18. 28 2月, 2020 2 次提交
  19. 06 1月, 2020 1 次提交
  20. 20 12月, 2019 1 次提交
    • R
      net: mvpp2: cycle comphy to power it down · 6791c102
      Russell King 提交于
      Presently, at boot time, the comphys are enabled. For firmware
      compatibility reasons, the comphy driver does not power down the
      comphys at boot. Consequently, the ethernet comphys are left active
      until the network interfaces are brought through an up/down cycle.
      
      If the port is never used, the port wastes power needlessly. Arrange
      for the ethernet comphys to be cycled by the mvpp2 driver as if the
      interface went through an up/down cycle during driver probe, thereby
      powering them down.
      
      This saves:
        270mW per 10G SFP+ port on the Macchiatobin Single Shot (eth0/eth1)
        370mW per 10G PHY port on the Macchiatobin Double Shot (eth0/eth1)
        160mW on the SFP port on either Macchiatobin flavour (eth3)
      Signed-off-by: NRussell King <rmk+kernel@armlinux.org.uk>
      Acked-by: NAntoine Tenart <antoine.tenart@bootlin.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6791c102
  21. 18 12月, 2019 1 次提交
  22. 15 12月, 2019 1 次提交
    • R
      net: marvell: mvpp2: phylink requires the link interrupt · f3f2364e
      Russell King 提交于
      phylink requires the MAC to report when its link status changes when
      operating in inband modes.  Failure to report link status changes
      means that phylink has no idea when the link events happen, which
      results in either the network interface's carrier remaining up or
      remaining permanently down.
      
      For example, with a fiber module, if the interface is brought up and
      link is initially established, taking the link down at the far end
      will cut the optical power.  The SFP module's LOS asserts, we
      deactivate the link, and the network interface reports no carrier.
      
      When the far end is brought back up, the SFP module's LOS deasserts,
      but the MAC may be slower to establish link.  If this happens (which
      in my tests is a certainty) then phylink never hears that the MAC
      has established link with the far end, and the network interface is
      stuck reporting no carrier.  This means the interface is
      non-functional.
      
      Avoiding the link interrupt when we have phylink is basically not
      an option, so remove the !port->phylink from the test.
      
      Fixes: 4bb04326 ("net: mvpp2: phylink support")
      Tested-by: NSven Auhagen <sven.auhagen@voleatech.de>
      Tested-by: NAntoine Tenart <antoine.tenart@bootlin.com>
      Signed-off-by: NRussell King <rmk+kernel@armlinux.org.uk>
      Signed-off-by: NJakub Kicinski <jakub.kicinski@netronome.com>
      f3f2364e