Sergei Shtylyov | e8f08ee | 2014-02-18 02:41:59 +0300 | [diff] [blame] | 1 | The following properties are common to the Ethernet controllers: |
| 2 | |
| 3 | - local-mac-address: array of 6 bytes, specifies the MAC address that was |
| 4 | assigned to the network device; |
| 5 | - mac-address: array of 6 bytes, specifies the MAC address that was last used by |
| 6 | the boot program; should be used in cases where the MAC address assigned to |
| 7 | the device by the boot program is different from the "local-mac-address" |
| 8 | property; |
| 9 | - max-speed: number, specifies maximum speed in Mbit/s supported by the device; |
| 10 | - max-frame-size: number, maximum transfer unit (IEEE defined MTU), rather than |
| 11 | the maximum frame size (there's contradiction in ePAPR). |
Martin Blumenstingl | e5f3a4a | 2016-11-25 14:12:00 +0100 | [diff] [blame] | 12 | - phy-mode: string, operation mode of the PHY interface. This is now a de-facto |
| 13 | standard property; supported values are: |
| 14 | * "mii" |
| 15 | * "gmii" |
| 16 | * "sgmii" |
| 17 | * "qsgmii" |
| 18 | * "tbi" |
| 19 | * "rev-mii" |
| 20 | * "rmii" |
| 21 | * "rgmii" (RX and TX delays are added by the MAC when required) |
| 22 | * "rgmii-id" (RGMII with internal RX and TX delays provided by the PHY, the |
| 23 | MAC should not add the RX or TX delays in this case) |
| 24 | * "rgmii-rxid" (RGMII with internal RX delay provided by the PHY, the MAC |
| 25 | should not add an RX delay in this case) |
| 26 | * "rgmii-txid" (RGMII with internal TX delay provided by the PHY, the MAC |
| 27 | should not add an TX delay in this case) |
| 28 | * "rtbi" |
| 29 | * "smii" |
| 30 | * "xgmii" |
| 31 | * "trgmii" |
Sergei Shtylyov | e8f08ee | 2014-02-18 02:41:59 +0300 | [diff] [blame] | 32 | - phy-connection-type: the same as "phy-mode" property but described in ePAPR; |
| 33 | - phy-handle: phandle, specifies a reference to a node representing a PHY |
| 34 | device; this property is described in ePAPR and so preferred; |
| 35 | - phy: the same as "phy-handle" property, not recommended for new bindings. |
| 36 | - phy-device: the same as "phy-handle" property, not recommended for new |
| 37 | bindings. |
Vince Bridgers | 13967f0 | 2015-04-15 11:17:38 -0500 | [diff] [blame] | 38 | - rx-fifo-depth: the size of the controller's receive fifo in bytes. This |
| 39 | is used for components that can have configurable receive fifo sizes, |
| 40 | and is useful for determining certain configuration settings such as |
| 41 | flow control thresholds. |
| 42 | - tx-fifo-depth: the size of the controller's transmit fifo in bytes. This |
| 43 | is used for components that can have configurable fifo sizes. |
Stas Sergeev | 4cba5c2 | 2015-07-20 17:49:57 -0700 | [diff] [blame] | 44 | - managed: string, specifies the PHY management type. Supported values are: |
| 45 | "auto", "in-band-status". "auto" is the default, it usess MDIO for |
| 46 | management if fixed-link is not specified. |
Sergei Shtylyov | e8f08ee | 2014-02-18 02:41:59 +0300 | [diff] [blame] | 47 | |
| 48 | Child nodes of the Ethernet controller are typically the individual PHY devices |
| 49 | connected via the MDIO bus (sometimes the MDIO bus controller is separate). |
| 50 | They are described in the phy.txt file in this same directory. |
Stas Sergeev | 4cba5c2 | 2015-07-20 17:49:57 -0700 | [diff] [blame] | 51 | For non-MDIO PHY management see fixed-link.txt. |