1. 10 9月, 2020 1 次提交
  2. 04 9月, 2020 6 次提交
  3. 24 8月, 2020 1 次提交
  4. 04 8月, 2020 1 次提交
  5. 26 7月, 2020 1 次提交
  6. 08 7月, 2020 1 次提交
  7. 04 7月, 2020 5 次提交
  8. 21 6月, 2020 4 次提交
  9. 19 6月, 2020 1 次提交
  10. 17 6月, 2020 1 次提交
  11. 16 6月, 2020 1 次提交
  12. 07 5月, 2020 1 次提交
  13. 15 3月, 2020 1 次提交
  14. 28 2月, 2020 2 次提交
  15. 06 1月, 2020 1 次提交
  16. 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
  17. 18 12月, 2019 1 次提交
  18. 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
  19. 24 11月, 2019 1 次提交
  20. 29 10月, 2019 3 次提交
  21. 03 10月, 2019 1 次提交
  22. 03 9月, 2019 2 次提交
    • M
      mvpp2: percpu buffers · 7d04b0b1
      Matteo Croce 提交于
      Every mvpp2 unit can use up to 8 buffers mapped by the BM (the HW buffer
      manager). The HW will place the frames in the buffer pool depending on the
      frame size: short (< 128 bytes), long (< 1664) or jumbo (up to 9856).
      
      As any unit can have up to 4 ports, the driver allocates only 2 pools,
      one for small and one long frames, and share them between ports.
      When the first port MTU is set higher than 1664 bytes, a third pool is
      allocated for jumbo frames.
      
      This shared allocation makes impossible to use percpu allocators,
      and creates contention between HW queues.
      
      If possible, i.e. if the number of possible CPU are less than 8 and jumbo
      frames are not used, switch to a new scheme: allocate 8 per-cpu pools for
      short and long frames and bind every pool to an RXQ.
      
      When the first port MTU is set higher than 1664 bytes, the allocation
      scheme is reverted to the old behaviour (3 shared pools), and when all
      ports MTU are lowered, the per-cpu buffers are allocated again.
      Signed-off-by: NMatteo Croce <mcroce@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      7d04b0b1
    • M
      mvpp2: refactor BM pool functions · 13616361
      Matteo Croce 提交于
      Refactor mvpp2_bm_pool_create(), mvpp2_bm_pool_destroy() and
      mvpp2_bm_pools_init() so that they accept a struct device instead
      of a struct platform_device, as they just need platform_device->dev.
      
      Removing such dependency makes the BM code more reusable in context
      where we don't have a pointer to the platform_device.
      Signed-off-by: NMatteo Croce <mcroce@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      13616361
  23. 15 8月, 2019 1 次提交
  24. 02 8月, 2019 1 次提交