blob: dbe91aa161bf8b17967f1d5a997d4988daa48ddd [file] [log] [blame]
Bin Meng69a00872016-01-11 22:41:23 -08001* TSEC-compatible ethernet nodes
2
3Properties:
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
13Example:
14 ethernet@24000 {
15 compatible = "fsl,tsec";
16 reg = <0x24000 0x1000>;
17 phy-handle = <&phy0>;
18 phy-connection-type = "sgmii";
19 };
20
21Child nodes of the TSEC controller are typically the individual PHY devices
22connected via the MDIO bus (sometimes the MDIO bus controller is separate).
23
24* MDIO IO device
25
26The MDIO is a bus to which the PHY devices are connected. For each
27device that exists on this bus, a PHY node should be created.
28
29Required 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
34Example:
35
36 mdio@24520 {
37 compatible = "fsl,tsec-mdio";
38 reg = <0x24520 0x20>;
39
40 ethernet-phy@0 {
41 reg = <0>;
42 };
43 };