Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 22 2月, 2019 2 次提交
  3. 18 2月, 2019 1 次提交
  5. 15 2月, 2019 1 次提交
  7. 14 2月, 2019 3 次提交
  9. 11 2月, 2019 1 次提交
  11. 10 2月, 2019 1 次提交
    • A
      net: phy: Add support for asking the PHY its abilities · efbdfdc2
      由 Andrew Lunn 提交于 
      Add support for runtime determination of what the PHY supports, by
adding a new function to the phy driver. The get_features call should
set the phydev->supported member with the features the PHY supports.
It is only called if phydrv->features is NULL.

This requires minor changes to pause. The PHY driver should not set
pause abilities, except for when it has odd cause capabilities, e.g.
pause cannot be disabled. With this change, phydev->supported already
contains the drivers abilities, including pause. So rather than
considering phydrv->features, look at the phydev->supported, and
enable pause if neither of the pause bits are already set.
Signed-off-by: NAndrew Lunn <andrew@lunn.ch>
[hkallweit1@gmail.com: fixed small checkpatch complaint in one comment]
Signed-off-by: NHeiner Kallweit <hkallweit1@gmail.com>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      efbdfdc2
  13. 08 2月, 2019 1 次提交
    • H
      net: phy: let genphy_c45_read_link manage the devices to check · 998a8a83
      由 Heiner Kallweit 提交于 
      Let genphy_c45_read_link manage the devices to check, this removes
overhead from callers. Add C22EXT to the list of excluded devices
because it doesn't implement the status register. According to the
802.3 clause 45 spec registers 29.0 - 29.4 are reserved.

At the moment we have very few clause 45 PHY drivers, so we are
lacking experience whether other drivers will have to exclude further
devices, or may need to check PHY XS. If we should figure out that
list of devices to check needs to be configurable, I think best will
be to add a device list member to struct phy_driver.

v2:
- adjusted commit message
- exclude also device C22EXT from link checking
Signed-off-by: NHeiner Kallweit <hkallweit1@gmail.com>
Reviewed-by: NAndrew Lunn <andrew@lunn.ch>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      998a8a83
  15. 07 2月, 2019 1 次提交
  17. 25 1月, 2019 1 次提交
  19. 20 1月, 2019 1 次提交
  21. 19 1月, 2019 2 次提交
  23. 18 1月, 2019 1 次提交
  25. 17 1月, 2019 1 次提交
  27. 28 12月, 2018 1 次提交
  29. 19 12月, 2018 1 次提交
    • H
      net: phy: improve phy state checking · 2b3e88ea
      由 Heiner Kallweit 提交于 
      Add helpers phy_is_started() and __phy_is_started() to avoid open-coded
checks whether PHY has been started. To make the check easier move
PHY_HALTED before PHY_UP in enum phy_state. Further improvements:

phy_start_aneg():
Return -EBUSY and print warning if function is called from a non-started
state (DOWN, READY, HALTED). Better check because function is exported
and drivers may use it incorrectly.

phy_interrupt():
Return IRQ_NONE also if state is DOWN or READY. We should never receive
an interrupt in one of these states, but better play safe.

phy_stop():
Just return and print a warning if PHY is in a non-started state.
This warning should help to identify drivers with unbalanced calls to
phy_start() / phy_stop().

phy_state_machine():
Schedule state machine run only if PHY is in a started state.
E.g. if state is READY we don't need the state machine, it will be
started by phy_start().

v2:
- don't use __func__ within phy_warn_state
v3:
- use WARN() instead of printing error message to facilitate debugging
Signed-off-by: NHeiner Kallweit <hkallweit1@gmail.com>
Reviewed-by: NFlorian Fainelli <f.fainelli@gmail.com>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2b3e88ea
  31. 12 11月, 2018 7 次提交
  33. 10 11月, 2018 1 次提交
  35. 09 11月, 2018 1 次提交
  37. 08 11月, 2018 1 次提交
  39. 02 10月, 2018 5 次提交
  41. 13 9月, 2018 6 次提交