1PHY nodes 2 3Required properties: 4 5 - interrupts : <a b> where a is the interrupt number and b is a 6 field that represents an encoding of the sense and level 7 information for the interrupt. This should be encoded based on 8 the information in section 2) depending on the type of interrupt 9 controller you have. 10 - interrupt-parent : the phandle for the interrupt controller that 11 services interrupts for this device. 12 - reg : The ID number for the phy, usually a small integer 13 14Optional Properties: 15 16- compatible: Compatible list, may contain 17 "ethernet-phy-ieee802.3-c22" or "ethernet-phy-ieee802.3-c45" for 18 PHYs that implement IEEE802.3 clause 22 or IEEE802.3 clause 45 19 specifications. If neither of these are specified, the default is to 20 assume clause 22. The compatible list may also contain other 21 elements. 22 23 If the phy's identifier is known then the list may contain an entry 24 of the form: "ethernet-phy-idAAAA.BBBB" where 25 AAAA - The value of the 16 bit Phy Identifier 1 register as 26 4 hex digits. This is the chip vendor OUI bits 3:18 27 BBBB - The value of the 16 bit Phy Identifier 2 register as 28 4 hex digits. This is the chip vendor OUI bits 19:24, 29 followed by 10 bits of a vendor specific ID. 30 31- max-speed: Maximum PHY supported speed (10, 100, 1000...) 32 33- broken-turn-around: If set, indicates the PHY device does not correctly 34 release the turn around line low at the end of a MDIO transaction. 35 36Example: 37 38ethernet-phy@0 { 39 compatible = "ethernet-phy-id0141.0e90", "ethernet-phy-ieee802.3-c22"; 40 interrupt-parent = <40000>; 41 interrupts = <35 1>; 42 reg = <0>; 43}; 44