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