66 lines · plain
1What: /sys/class/mdio_bus/<bus>/<device>/attached_dev2Date: May 20173KernelVersion: 4.134Contact: netdev@vger.kernel.org5Description:6 Symbolic link to the network device this PHY device is7 attached to.8 9What: /sys/class/mdio_bus/<bus>/<device>/phy_has_fixups10Date: February 201411KernelVersion: 3.1512Contact: netdev@vger.kernel.org13Description:14 This attribute contains the boolean value whether a given PHY15 device has had any "fixup" workaround running on it, encoded as16 a boolean. This information is provided to help troubleshooting17 PHY configurations.18 19What: /sys/class/mdio_bus/<bus>/<device>/phy_id20Date: November 201221KernelVersion: 3.822Contact: netdev@vger.kernel.org23Description:24 This attribute contains the 32-bit PHY Identifier as reported25 by the device during bus enumeration, encoded in hexadecimal.26 This ID is used to match the device with the appropriate27 driver.28 29What: /sys/class/mdio_bus/<bus>/<device>/phy_interface30Date: February 201431KernelVersion: 3.1532Contact: netdev@vger.kernel.org33Description:34 This attribute contains the PHY interface as configured by the35 Ethernet driver during bus enumeration, encoded in string.36 This interface mode is used to configure the Ethernet MAC with the37 appropriate mode for its data lines to the PHY hardware.38 39 Possible values are:40 41 <empty> (not available), mii, gmii, sgmii, tbi, rev-mii,42 rmii, rgmii, rgmii-id, rgmii-rxid, rgmii-txid, rtbi, smii43 xgmii, moca, qsgmii, trgmii, 1000base-x, 2500base-x, rxaui,44 xaui, 10gbase-kr, unknown45 46What: /sys/class/mdio_bus/<bus>/<device>/phy_standalone47Date: May 201948KernelVersion: 5.349Contact: netdev@vger.kernel.org50Description:51 Boolean value indicating whether the PHY device is used in52 standalone mode, without a net_device associated, by PHYLINK.53 Attribute created only when this is the case.54 55What: /sys/class/mdio_bus/<bus>/<device>/phy_dev_flags56Date: March 202157KernelVersion: 5.1358Contact: netdev@vger.kernel.org59Description:60 32-bit hexadecimal number representing a bit mask of the61 configuration bits passed from the consumer of the PHY62 (Ethernet MAC, switch, etc.) to the PHY driver. The flags are63 only used internally by the kernel and their placement are64 not meant to be stable across kernel versions. This is intended65 for facilitating the debugging of PHY drivers.66