ethernet.txt 3.0 KB

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