1. 01 12月, 2021 1 次提交
  2. 24 8月, 2021 1 次提交
    • N
      net: dsa: mv88e6xxx: Update mv88e6393x serdes errata · 3b0720ba
      Nathan Rossi 提交于
      In early erratas this issue only covered port 0 when changing from
      [x]MII (rev A 3.6). In subsequent errata versions this errata changed to
      cover the additional "Hardware reset in CPU managed mode" condition, and
      removed the note specifying that it only applied to port 0.
      
      In designs where the device is configured with CPU managed mode
      (CPU_MGD), on reset all SERDES ports (p0, p9, p10) have a stuck power
      down bit and require this initial power up procedure. As such apply this
      errata to all three SERDES ports of the mv88e6393x.
      Signed-off-by: NNathan Rossi <nathan.rossi@digi.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3b0720ba
  3. 02 7月, 2021 1 次提交
  4. 28 4月, 2021 1 次提交
    • T
      net: dsa: mv88e6xxx: Fix 6095/6097/6185 ports in non-SERDES CMODE · 6066234a
      Tobias Waldekranz 提交于
      The .serdes_get_lane op used the magic value 0xff to indicate a valid
      SERDES lane and 0 signaled that a non-SERDES mode was set on the port.
      
      Unfortunately, "0" is also a valid lane ID, so even when these ports
      where configured to e.g. RGMII the driver would set them up as SERDES
      ports.
      
      - Replace 0xff with 0 to indicate a valid lane ID. The number is on
        the one hand just as arbitrary, but it is at least the first valid one
        and therefore less of a surprise.
      
      - Follow the other .serdes_get_lane implementations and return -ENODEV
        in the case where no SERDES is assigned to the port.
      
      Fixes: f5be107c ("net: dsa: mv88e6xxx: Support serdes ports on MV88E6097/6095/6185")
      Signed-off-by: NTobias Waldekranz <tobias@waldekranz.com>
      Reviewed-by: NAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6066234a
  5. 18 3月, 2021 2 次提交
  6. 26 11月, 2020 3 次提交
  7. 02 5月, 2020 2 次提交
  8. 16 3月, 2020 3 次提交
  9. 17 2月, 2020 2 次提交
  10. 28 12月, 2019 1 次提交
  11. 02 9月, 2019 10 次提交
  12. 30 8月, 2019 1 次提交
  13. 28 8月, 2019 4 次提交
  14. 24 6月, 2019 1 次提交
  15. 31 5月, 2019 1 次提交
  16. 05 3月, 2019 1 次提交
  17. 28 1月, 2019 1 次提交
  18. 12 11月, 2018 1 次提交
  19. 03 9月, 2018 1 次提交
  20. 15 8月, 2018 1 次提交
  21. 10 8月, 2018 1 次提交