25 Oct, 2010

1 commit

  • The following functions are not used directly by any drivers:
    phy_attach_direct
    phy_device_create
    phy_prepare_link
    genphy_config_advert
    genphy_setup_forced
    phy_config_interrupt
    phy_clear_interrypt
    phy_sanitize_settings
    phy_enable_interrupts
    phy_disable_interrupts

    Signed-off-by: Stephen Hemminger
    Signed-off-by: David S. Miller

    stephen hemminger
     

20 Nov, 2008

1 commit

  • All MDIO bus drivers currently name bus with "%x" format.
    There is one exception where mv643xx_eth driver is using "%d".
    Phy address on the bus uses format "%02x".

    Fixing phy name example to match all real life MDIO drivers.

    Signed-off-by: Paulius Zaleckas
    Signed-off-by: David S. Miller

    Paulius Zaleckas
     

25 Apr, 2008

1 commit

  • Sometimes the specific interaction between the platform and the PHY
    requires special handling. For instance, to change where the PHY's
    clock input is, or to add a delay to account for latency issues in the
    data path. We add a mechanism for registering a callback with the PHY
    Lib to be called on matching PHYs when they are brought up, or reset.

    Signed-off-by: Andy Fleming
    Signed-off-by: Jeff Garzik

    Andy Fleming
     

02 Dec, 2006

1 commit

  • Most PHYs connect to an ethernet controller over a GMII or MII
    interface. However, a growing number are connected over
    different interfaces, such as RGMII or SGMII.

    The ethernet driver will tell the PHY what type of connection it
    is by setting it manually, or passing it in through phy_connect
    (or phy_attach).

    Changes include:
    * Updates to documentation
    * Updates to PHY Lib consumers
    * Changes to PHY Lib to add interface support
    * Some minor changes to whitespace in phy.h
    * gianfar driver now detects interface and passes appropriate
    value to PHY Lib
    Signed-off-by: Andrew Fleming
    Signed-off-by: Jeff Garzik

    Andy Fleming
     

31 Jul, 2005

1 commit