1The following properties are common to the Ethernet controllers:
2
3NOTE: All 'phy*' properties documented below are Ethernet specific. For the
4generic PHY 'phys' property, see
5Documentation/devicetree/bindings/phy/phy-bindings.txt.
6
7- mac-address: array of 6 bytes, specifies the MAC address that was last used by
8  the boot program; should be used in cases where the MAC address assigned to
9  the device by the boot program is different from the "local-mac-address"
10  property;
11- local-mac-address: array of 6 bytes, specifies the MAC address that was
12  assigned to the network device;
13- nvmem-cells: phandle, reference to an nvmem node for the MAC address
14- nvmem-cell-names: string, should be "mac-address" if nvmem is to be used
15- max-speed: number, specifies maximum speed in Mbit/s supported by the device;
16- max-frame-size: number, maximum transfer unit (IEEE defined MTU), rather than
17  the maximum frame size (there's contradiction in the Devicetree
18  Specification).
19- phy-mode: string, operation mode of the PHY interface. This is now a de-facto
20  standard property; supported values are:
21  * "internal" (Internal means there is not a standard bus between the MAC and
22     the PHY, something proprietary is being used to embed the PHY in the MAC.)
23  * "mii"
24  * "gmii"
25  * "sgmii"
26  * "qsgmii"
27  * "tbi"
28  * "rev-mii"
29  * "rmii"
30  * "rgmii" (RX and TX delays are added by the MAC when required)
31  * "rgmii-id" (RGMII with internal RX and TX delays provided by the PHY, the
32     MAC should not add the RX or TX delays in this case)
33  * "rgmii-rxid" (RGMII with internal RX delay provided by the PHY, the MAC
34     should not add an RX delay in this case)
35  * "rgmii-txid" (RGMII with internal TX delay provided by the PHY, the MAC
36     should not add an TX delay in this case)
37  * "rtbi"
38  * "smii"
39  * "xgmii"
40  * "trgmii"
41  * "1000base-x",
42  * "2500base-x",
43  * "rxaui"
44  * "xaui"
45  * "10gbase-kr" (10GBASE-KR, XFI, SFI)
46  * "usxgmii"
47- phy-connection-type: the same as "phy-mode" property but described in the
48  Devicetree Specification;
49- phy-handle: phandle, specifies a reference to a node representing a PHY
50  device; this property is described in the Devicetree Specification and so
51  preferred;
52- phy: the same as "phy-handle" property, not recommended for new bindings.
53- phy-device: the same as "phy-handle" property, not recommended for new
54  bindings.
55- rx-fifo-depth: the size of the controller's receive fifo in bytes. This
56  is used for components that can have configurable receive fifo sizes,
57  and is useful for determining certain configuration settings such as
58  flow control thresholds.
59- tx-fifo-depth: the size of the controller's transmit fifo in bytes. This
60  is used for components that can have configurable fifo sizes.
61- managed: string, specifies the PHY management type. Supported values are:
62  "auto", "in-band-status". "auto" is the default, it usess MDIO for
63  management if fixed-link is not specified.
64
65Child nodes of the Ethernet controller are typically the individual PHY devices
66connected via the MDIO bus (sometimes the MDIO bus controller is separate).
67They are described in the phy.txt file in this same directory.
68For non-MDIO PHY management see fixed-link.txt.
69