1. 17 10月, 2016 1 次提交
  2. 22 9月, 2016 1 次提交
  3. 11 5月, 2016 1 次提交
  4. 19 4月, 2016 1 次提交
  5. 14 3月, 2016 1 次提交
  6. 08 1月, 2016 11 次提交
  7. 31 12月, 2015 1 次提交
  8. 23 10月, 2015 1 次提交
  9. 03 10月, 2015 1 次提交
    • S
      phylib: Add phy_set_max_speed helper · f3a6bd39
      Simon Horman 提交于
      Add a helper to allow ethernet drivers to limit the speed of a phy
      (that they are attached to).
      
      This mainly involves factoring out the business-end of
      of_set_phy_supported() and exporting a new symbol.
      
      This code seems to be open coded in several places, in several different
      variants.
      
      It is is envisaged that this will be used in situations where setting the
      "max-speed" property in DT is not appropriate, e.g. because the maximum
      speed is not a property of the phy hardware.
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f3a6bd39
  10. 25 9月, 2015 2 次提交
    • R
      phy: add phy_device_remove() · 38737e49
      Russell King 提交于
      Add a phy_device_remove() function to complement phy_device_register(),
      which undoes the effects of phy_device_register() by removing the phy
      device from visibility, but not freeing it.
      
      This allows these details to be moved out of the mdio bus code into
      the phy code where this action belongs.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      38737e49
    • R
      phy: fix mdiobus module safety · 3e3aaf64
      Russell King 提交于
      Re-implement the mdiobus module refcounting to ensure that we actually
      ensure that the mdiobus module code does not go away while we might call
      into it.
      
      The old scheme using bus->dev.driver was buggy, because bus->dev is a
      class device which never has a struct device_driver associated with it,
      and hence the associated code trying to obtain a refcount did nothing
      useful.
      
      Instead, take the approach that other subsystems do: pass the module
      when calling mdiobus_register(), and record that in the mii_bus struct.
      When we need to increment the module use count in the phy code, use
      this stored pointer.  When the phy is deteched, drop the module
      refcount, remembering that the phy device might go away at that point.
      
      This doesn't stop the mii_bus going away while there are in-use phys -
      it merely stops the underlying code vanishing.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3e3aaf64
  11. 01 9月, 2015 1 次提交
    • F
      net: phy: Allow PHY devices to identify themselves as Ethernet switches, etc. · 5a11dd7d
      Florian Fainelli 提交于
      Some Ethernet MAC drivers using the PHY library require the hardcoding
      of link parameters when interfaced to a switch device, SFP module,
      switch to switch port, etc. This has typically lead to various ad-hoc
      implementations looking like this:
      
      - using a "fixed PHY" emulated device, which will provide link
        indication towards the Ethernet MAC driver and hardware
      
      - pretend there is no PHY and hardcode link parameters, ala mv643x_eth
      
      Based on that, it is desireable to have the PHY drivers advertise the
      correct link parameters, just like regular Ethernet PHYs towards their
      CPU Ethernet MAC drivers, however, Ethernet MAC drivers should be able
      to tell whether this link should be monitored or not. In the context
      of an Ethernet switch, SFP module, switch to switch link, we do not
      need to monitor this link since it should be always up.
      Signed-off-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: NAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5a11dd7d
  12. 11 7月, 2015 1 次提交
  13. 27 5月, 2015 1 次提交
  14. 15 5月, 2015 1 次提交
  15. 27 1月, 2015 2 次提交
  16. 07 1月, 2015 1 次提交
  17. 22 11月, 2014 1 次提交
  18. 13 11月, 2014 1 次提交
  19. 24 8月, 2014 1 次提交
  20. 31 7月, 2014 1 次提交
    • V
      net: libphy: Add phy specific function to access mmd phy registers · 0c1d77df
      Vince Bridgers 提交于
      libphy was originally written assuming all phy devices support clause 45
      access extensions to the mmd registers through the indirection registers
      located within the first 16 phy registers. This assumption is not true
      in all cases, and one specific example is the Micrel ksz9021 10/100/1000
      Mbps phy. Using the stmmac driver, accessing the mmd registers to query
      and configure energy efficient Ethernet (EEE) features yielded unexpected
      behavior.
      
      This patch adds mmd access functions to the phy driver that can be
      overriden by the phy specific driver if the phy does not support this
      mechanism or uses it's own non-standard access mechanism. By default,
      the IEEE Compatible clause 45 access mechanism described in clause 22
      is used. With this patch, EEE query/configure functions as expected
      using the stmmac and the Micrel ksz9021 phy.
      Signed-off-by: NVince Bridgers <vbridgers2013@gmail.com>
      Reviewed-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      0c1d77df
  21. 22 6月, 2014 1 次提交
  22. 03 5月, 2014 1 次提交
  23. 21 4月, 2014 1 次提交
  24. 17 4月, 2014 1 次提交
  25. 18 2月, 2014 2 次提交
  26. 14 2月, 2014 1 次提交
  27. 13 2月, 2014 1 次提交