qman.txt 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176
  1. QorIQ DPAA Queue Manager Device Tree Binding
  2. Copyright (C) 2008 - 2014 Freescale Semiconductor Inc.
  3. CONTENTS
  4. - QMan Node
  5. - QMan Private Memory Nodes
  6. - Example
  7. QMan Node
  8. The Queue Manager is part of the Data-Path Acceleration Architecture (DPAA). QMan
  9. supports queuing and QoS scheduling of frames to CPUs, network interfaces and
  10. DPAA logic modules, maintains packet ordering within flows. Besides providing
  11. flow-level queuing, is also responsible for congestion management functions such
  12. as RED/WRED, congestion notifications and tail discards. This binding covers the
  13. CCSR space programming model
  14. PROPERTIES
  15. - compatible
  16. Usage: Required
  17. Value type: <stringlist>
  18. Definition: Must include "fsl,qman"
  19. May include "fsl,<SoC>-qman"
  20. - reg
  21. Usage: Required
  22. Value type: <prop-encoded-array>
  23. Definition: Registers region within the CCSR address space
  24. The QMan revision information is located in the QMAN_IP_REV_1/2 registers which
  25. are located at offsets 0xbf8 and 0xbfc
  26. - interrupts
  27. Usage: Required
  28. Value type: <prop-encoded-array>
  29. Definition: Standard property. The error interrupt
  30. - fsl,qman-portals
  31. Usage: Required
  32. Value type: <phandle>
  33. Definition: Phandle to this QMan instance's portals
  34. - fsl,liodn
  35. Usage: See pamu.txt
  36. Value type: <prop-encoded-array>
  37. Definition: PAMU property used for static LIODN assignment
  38. - fsl,iommu-parent
  39. Usage: See pamu.txt
  40. Value type: <phandle>
  41. Definition: PAMU property used for dynamic LIODN assignment
  42. For additional details about the PAMU/LIODN binding(s) see pamu.txt
  43. - clocks
  44. Usage: See clock-bindings.txt and qoriq-clock.txt
  45. Value type: <prop-encoded-array>
  46. Definition: Reference input clock. Its frequency is half of the
  47. platform clock
  48. Devices connected to a QMan instance via Direct Connect Portals (DCP) must link
  49. to the respective QMan instance
  50. - fsl,qman
  51. Usage: Required
  52. Value type: <prop-encoded-array>
  53. Description: List of phandle and DCP index pairs, to the QMan instance
  54. to which this device is connected via the DCP
  55. QMan Private Memory Nodes
  56. QMan requires two contiguous range of physical memory used for the backing store
  57. for QMan Frame Queue Descriptor (FQD) and Packed Frame Descriptor Record (PFDR).
  58. This memory is reserved/allocated as a nodes under the /reserved-memory node
  59. The QMan FQD memory node must be named "qman-fqd"
  60. PROPERTIES
  61. - compatible
  62. Usage: required
  63. Value type: <stringlist>
  64. Definition: Must inclide "fsl,qman-fqd"
  65. The QMan PFDR memory node must be named "qman-pfdr"
  66. PROPERTIES
  67. - compatible
  68. Usage: required
  69. Value type: <stringlist>
  70. Definition: Must inclide "fsl,qman-pfdr"
  71. The following constraints are relevant to the FQD and PFDR private memory:
  72. - The size must be 2^(size + 1), with size = 11..29. That is 4 KiB to
  73. 1 GiB
  74. - The alignment must be a muliptle of the memory size
  75. The size of the FQD and PFDP must be chosen by observing the hardware features
  76. configured via the Reset Configuration Word (RCW) and that are relevant to a
  77. specific board (e.g. number of MAC(s) pinned-out, number of offline/host command
  78. FMan ports, etc.). The size configured in the DT must reflect the hardware
  79. capabilities and not the specific needs of an application
  80. For additional details about reserved memory regions see reserved-memory.txt
  81. EXAMPLE
  82. The example below shows a QMan FQD and a PFDR dynamic allocation memory nodes
  83. reserved-memory {
  84. #address-cells = <2>;
  85. #size-cells = <2>;
  86. ranges;
  87. qman_fqd: qman-fqd {
  88. compatible = "fsl,qman-fqd";
  89. alloc-ranges = <0 0 0x10 0>;
  90. size = <0 0x400000>;
  91. alignment = <0 0x400000>;
  92. };
  93. qman_pfdr: qman-pfdr {
  94. compatible = "fsl,qman-pfdr";
  95. alloc-ranges = <0 0 0x10 0>;
  96. size = <0 0x2000000>;
  97. alignment = <0 0x2000000>;
  98. };
  99. };
  100. The example below shows a (P4080) QMan CCSR-space node
  101. qportals: qman-portals@ff4200000 {
  102. ...
  103. };
  104. clockgen: global-utilities@e1000 {
  105. ...
  106. sysclk: sysclk {
  107. ...
  108. };
  109. ...
  110. platform_pll: platform-pll@c00 {
  111. #clock-cells = <1>;
  112. reg = <0xc00 0x4>;
  113. compatible = "fsl,qoriq-platform-pll-1.0";
  114. clocks = <&sysclk>;
  115. clock-output-names = "platform-pll", "platform-pll-div2";
  116. };
  117. ...
  118. };
  119. crypto@300000 {
  120. ...
  121. fsl,qman = <&qman, 2>;
  122. ...
  123. };
  124. qman: qman@318000 {
  125. compatible = "fsl,qman";
  126. reg = <0x318000 0x1000>;
  127. interrupts = <16 2 1 3>
  128. fsl,liodn = <0x16>;
  129. fsl,qman-portals = <&qportals>;
  130. memory-region = <&qman_fqd &qman_pfdr>;
  131. clocks = <&platform_pll 1>;
  132. };
  133. fman@400000 {
  134. ...
  135. fsl,qman = <&qman, 0>;
  136. ...
  137. };