1 * TSEC-compatible ethernet nodes 2 3 Properties: 4 5 - compatible : Should be "fsl,tsec" 6 - reg : Offset and length of the register set for the device 7 - phy-handle : See ethernet.txt file in the same directory. 8 - phy-connection-type : See ethernet.txt file in the same directory. This 9 property is only really needed if the connection is of type "rgmii-id", 10 "rgmii-rxid" and "rgmii-txid" as all other connection types are detected 11 by hardware. 12 13 Example: 14 ethernet@24000 { 15 compatible = "fsl,tsec"; 16 reg = <0x24000 0x1000>; 17 phy-handle = <&phy0>; 18 phy-connection-type = "sgmii"; 19 }; 20 21 Child nodes of the TSEC controller are typically the individual PHY devices 22 connected via the MDIO bus (sometimes the MDIO bus controller is separate). 23 24 * MDIO IO device 25 26 The MDIO is a bus to which the PHY devices are connected. For each 27 device that exists on this bus, a PHY node should be created. 28 29 Required properties: 30 - compatible : Should define the compatible device type for the 31 mdio. Currently supported string/device is "fsl,tsec-mdio". 32 - reg : Offset and length of the register set for the device 33 34 Example: 35 36 mdio@24520 { 37 compatible = "fsl,tsec-mdio"; 38 reg = <0x24520 0x20>; 39 40 ethernet-phy@0 { 41 reg = <0>; 42 }; 43 }; 44 45 * TBI Internal MDIO bus 46 47 As of this writing, every tsec is associated with an internal TBI PHY. 48 This PHY is accessed through the local MDIO bus. These buses are defined 49 similarly to the mdio buses. The TBI PHYs underneath them are similar to 50 normal PHYs, but the reg property is considered instructive, rather than 51 descriptive. The reg property should be chosen so it doesn't interfere 52 with other PHYs on the bus. The TBI PHYs are referred to by a "tbi-handle" 53 property under the tsec node, which has a similar meaning of "phy-handle". 54 55 Example: 56 ethernet@24000 { 57 phy-handle = <&tbi1>; 58 }; 59 60 mdio@24520 { 61 tbi1: tbi-phy@1f { 62 reg = <0x1f>; 63 }; 64 }; 65
