tsec.txt 2.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576
  1. * MDIO IO device
  2. The MDIO is a bus to which the PHY devices are connected. For each
  3. device that exists on this bus, a child node should be created. See
  4. the definition of the PHY node in booting-without-of.txt for an example
  5. of how to define a PHY.
  6. Required properties:
  7. - reg : Offset and length of the register set for the device
  8. - compatible : Should define the compatible device type for the
  9. mdio. Currently, this is most likely to be "fsl,gianfar-mdio"
  10. Example:
  11. mdio@24520 {
  12. reg = <24520 20>;
  13. compatible = "fsl,gianfar-mdio";
  14. ethernet-phy@0 {
  15. ......
  16. };
  17. };
  18. * TBI Internal MDIO bus
  19. As of this writing, every tsec is associated with an internal TBI PHY.
  20. This PHY is accessed through the local MDIO bus. These buses are defined
  21. similarly to the mdio buses, except they are compatible with "fsl,gianfar-tbi".
  22. The TBI PHYs underneath them are similar to normal PHYs, but the reg property
  23. is considered instructive, rather than descriptive. The reg property should
  24. be chosen so it doesn't interfere with other PHYs on the bus.
  25. * Gianfar-compatible ethernet nodes
  26. Properties:
  27. - device_type : Should be "network"
  28. - model : Model of the device. Can be "TSEC", "eTSEC", or "FEC"
  29. - compatible : Should be "gianfar"
  30. - reg : Offset and length of the register set for the device
  31. - local-mac-address : List of bytes representing the ethernet address of
  32. this controller
  33. - interrupts : For FEC devices, the first interrupt is the device's
  34. interrupt. For TSEC and eTSEC devices, the first interrupt is
  35. transmit, the second is receive, and the third is error.
  36. - phy-handle : The phandle for the PHY connected to this ethernet
  37. controller.
  38. - fixed-link : <a b c d e> where a is emulated phy id - choose any,
  39. but unique to the all specified fixed-links, b is duplex - 0 half,
  40. 1 full, c is link speed - d#10/d#100/d#1000, d is pause - 0 no
  41. pause, 1 pause, e is asym_pause - 0 no asym_pause, 1 asym_pause.
  42. - phy-connection-type : a string naming the controller/PHY interface type,
  43. i.e., "mii" (default), "rmii", "gmii", "rgmii", "rgmii-id", "sgmii",
  44. "tbi", or "rtbi". This property is only really needed if the connection
  45. is of type "rgmii-id", as all other connection types are detected by
  46. hardware.
  47. - fsl,magic-packet : If present, indicates that the hardware supports
  48. waking up via magic packet.
  49. - bd-stash : If present, indicates that the hardware supports stashing
  50. buffer descriptors in the L2.
  51. - rx-stash-len : Denotes the number of bytes of a received buffer to stash
  52. in the L2.
  53. - rx-stash-idx : Denotes the index of the first byte from the received
  54. buffer to stash in the L2.
  55. Example:
  56. ethernet@24000 {
  57. device_type = "network";
  58. model = "TSEC";
  59. compatible = "gianfar";
  60. reg = <0x24000 0x1000>;
  61. local-mac-address = [ 00 E0 0C 00 73 00 ];
  62. interrupts = <29 2 30 2 34 2>;
  63. interrupt-parent = <&mpic>;
  64. phy-handle = <&phy0>
  65. };