1. 07 6月, 2017 6 次提交
  2. 06 6月, 2017 1 次提交
  3. 05 6月, 2017 3 次提交
  4. 03 6月, 2017 1 次提交
  5. 01 6月, 2017 1 次提交
  6. 31 5月, 2017 1 次提交
  7. 28 5月, 2017 1 次提交
  8. 27 5月, 2017 5 次提交
  9. 26 5月, 2017 1 次提交
  10. 25 5月, 2017 2 次提交
  11. 18 5月, 2017 6 次提交
  12. 17 5月, 2017 1 次提交
  13. 16 5月, 2017 2 次提交
  14. 12 5月, 2017 2 次提交
    • F
      net: phy: Call bus->reset() after releasing PHYs from reset · df0c8d91
      Florian Fainelli 提交于
      The API convention makes it that a given MDIO bus reset should be able
      to access PHY devices in its reset() callback and perform additional
      MDIO accesses in order to bring the bus and PHYs in a working state.
      
      Commit 69226896 ("mdio_bus: Issue GPIO RESET to PHYs.") broke that
      contract by first calling bus->reset() and then release all PHYs from
      reset using their shared GPIO line, so restore the expected
      functionality here.
      
      Fixes: 69226896 ("mdio_bus: Issue GPIO RESET to PHYs.")
      Signed-off-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      df0c8d91
    • J
      mdio: mux: Correct mdio_mux_init error path issues · b6016166
      Jon Mason 提交于
      There is a potential unnecessary refcount decrement on error path of
      put_device(&pb->mii_bus->dev), as it is possible to avoid the
      of_mdio_find_bus() call if mux_bus is specified by the calling function.
      
      The same put_device() is not called in the error path if the
      devm_kzalloc of pb fails.  This caused the variable used in the
      put_device() to be changed, as the pb pointer was obviously not set up.
      
      There is an unnecessary of_node_get() on child_bus_node if the
      of_mdiobus_register() is successful, as the
      for_each_available_child_of_node() automatically increments this.
      Thus the refcount on this node will always be +1 more than it should be.
      
      There is no of_node_put() on child_bus_node if the of_mdiobus_register()
      call fails.
      
      Finally, it is lacking devm_kfree() of pb in the error path.  While this
      might not be technically necessary, it was present in other parts of the
      function.  So, I am adding it where necessary to make it uniform.
      Signed-off-by: NJon Mason <jon.mason@broadcom.com>
      Fixes: f20e6657 ("mdio: mux: Enhanced MDIO mux framework for integrated multiplexers")
      Fixes: 0ca2997d ("netdev/of/phy: Add MDIO bus multiplexer support.")
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b6016166
  15. 09 5月, 2017 1 次提交
  16. 01 5月, 2017 1 次提交
  17. 27 4月, 2017 2 次提交
  18. 25 4月, 2017 1 次提交
    • R
      mdio_bus: Issue GPIO RESET to PHYs. · 69226896
      Roger Quadros 提交于
      Some boards [1] leave the PHYs at an invalid state
      during system power-up or reset thus causing unreliability
      issues with the PHY which manifests as PHY not being detected
      or link not functional. To fix this, these PHYs need to be RESET
      via a GPIO connected to the PHY's RESET pin.
      
      Some boards have a single GPIO controlling the PHY RESET pin of all
      PHYs on the bus whereas some others have separate GPIOs controlling
      individual PHY RESETs.
      
      In both cases, the RESET de-assertion cannot be done in the PHY driver
      as the PHY will not probe till its reset is de-asserted.
      So do the RESET de-assertion in the MDIO bus driver.
      
      [1] - am572x-idk, am571x-idk, a437x-idk
      Signed-off-by: NRoger Quadros <rogerq@ti.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      69226896
  19. 21 4月, 2017 1 次提交
  20. 18 4月, 2017 1 次提交