1What:		/sys/class/mdio_bus/<bus>/<device>/attached_dev
2Date:		May 2017
3KernelVersion:	4.13
4Contact:	netdev@vger.kernel.org
5Description:
6		Symbolic link to the network device this PHY device is
7		attached to.
8
9What:		/sys/class/mdio_bus/<bus>/<device>/phy_has_fixups
10Date:		February 2014
11KernelVersion:	3.15
12Contact:	netdev@vger.kernel.org
13Description:
14		Boolean value indicating whether the PHY device has
15		any fixups registered against it (phy_register_fixup)
16
17What:		/sys/class/mdio_bus/<bus>/<device>/phy_id
18Date:		November 2012
19KernelVersion:	3.8
20Contact:	netdev@vger.kernel.org
21Description:
22		32-bit hexadecimal value corresponding to the PHY device's OUI,
23		model and revision number.
24
25What:		/sys/class/mdio_bus/<bus>/<device>/phy_interface
26Date:		February 2014
27KernelVersion:	3.15
28Contact:	netdev@vger.kernel.org
29Description:
30		String value indicating the PHY interface, possible
31		values are:.
32		<empty> (not available), mii, gmii, sgmii, tbi, rev-mii,
33		rmii, rgmii, rgmii-id, rgmii-rxid, rgmii-txid, rtbi, smii
34		xgmii, moca, qsgmii, trgmii, 1000base-x, 2500base-x, rxaui,
35		xaui, 10gbase-kr, unknown
36
37