dsi.txt 6.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217
  1. Qualcomm Technologies Inc. adreno/snapdragon DSI output
  2. DSI Controller:
  3. Required properties:
  4. - compatible:
  5. * "qcom,mdss-dsi-ctrl"
  6. - reg: Physical base address and length of the registers of controller
  7. - reg-names: The names of register regions. The following regions are required:
  8. * "dsi_ctrl"
  9. - qcom,dsi-host-index: The ID of DSI controller hardware instance. This should
  10. be 0 or 1, since we have 2 DSI controllers at most for now.
  11. - interrupts: The interrupt signal from the DSI block.
  12. - power-domains: Should be <&mmcc MDSS_GDSC>.
  13. - clocks: Phandles to device clocks.
  14. - clock-names: the following clocks are required:
  15. * "mdp_core_clk"
  16. * "iface_clk"
  17. * "bus_clk"
  18. * "core_mmss_clk"
  19. * "byte_clk"
  20. * "pixel_clk"
  21. * "core_clk"
  22. For DSIv2, we need an additional clock:
  23. * "src_clk"
  24. - assigned-clocks: Parents of "byte_clk" and "pixel_clk" for the given platform.
  25. - assigned-clock-parents: The Byte clock and Pixel clock PLL outputs provided
  26. by a DSI PHY block. See [1] for details on clock bindings.
  27. - vdd-supply: phandle to vdd regulator device node
  28. - vddio-supply: phandle to vdd-io regulator device node
  29. - vdda-supply: phandle to vdda regulator device node
  30. - phys: phandle to DSI PHY device node
  31. - phy-names: the name of the corresponding PHY device
  32. - syscon-sfpb: A phandle to mmss_sfpb syscon node (only for DSIv2)
  33. - ports: Contains 2 DSI controller ports as child nodes. Each port contains
  34. an endpoint subnode as defined in [2] and [3].
  35. Optional properties:
  36. - panel@0: Node of panel connected to this DSI controller.
  37. See files in [4] for each supported panel.
  38. - qcom,dual-dsi-mode: Boolean value indicating if the DSI controller is
  39. driving a panel which needs 2 DSI links.
  40. - qcom,master-dsi: Boolean value indicating if the DSI controller is driving
  41. the master link of the 2-DSI panel.
  42. - qcom,sync-dual-dsi: Boolean value indicating if the DSI controller is
  43. driving a 2-DSI panel whose 2 links need receive command simultaneously.
  44. - interrupt-parent: phandle to the MDP block if the interrupt signal is routed
  45. through MDP block
  46. - pinctrl-names: the pin control state names; should contain "default"
  47. - pinctrl-0: the default pinctrl state (active)
  48. - pinctrl-n: the "sleep" pinctrl state
  49. - ports: contains DSI controller input and output ports as children, each
  50. containing one endpoint subnode.
  51. DSI Endpoint properties:
  52. - remote-endpoint: For port@0, set to phandle of the connected panel/bridge's
  53. input endpoint. For port@1, set to the MDP interface output. See [2] for
  54. device graph info.
  55. - data-lanes: this describes how the physical DSI data lanes are mapped
  56. to the logical lanes on the given platform. The value contained in
  57. index n describes what physical lane is mapped to the logical lane n
  58. (DATAn, where n lies between 0 and 3). The clock lane position is fixed
  59. and can't be changed. Hence, they aren't a part of the DT bindings. See
  60. [3] for more info on the data-lanes property.
  61. For example:
  62. data-lanes = <3 0 1 2>;
  63. The above mapping describes that the logical data lane DATA0 is mapped to
  64. the physical data lane DATA3, logical DATA1 to physical DATA0, logic DATA2
  65. to phys DATA1 and logic DATA3 to phys DATA2.
  66. There are only a limited number of physical to logical mappings possible:
  67. <0 1 2 3>
  68. <1 2 3 0>
  69. <2 3 0 1>
  70. <3 0 1 2>
  71. <0 3 2 1>
  72. <1 0 3 2>
  73. <2 1 0 3>
  74. <3 2 1 0>
  75. DSI PHY:
  76. Required properties:
  77. - compatible: Could be the following
  78. * "qcom,dsi-phy-28nm-hpm"
  79. * "qcom,dsi-phy-28nm-lp"
  80. * "qcom,dsi-phy-20nm"
  81. * "qcom,dsi-phy-28nm-8960"
  82. - reg: Physical base address and length of the registers of PLL, PHY and PHY
  83. regulator
  84. - reg-names: The names of register regions. The following regions are required:
  85. * "dsi_pll"
  86. * "dsi_phy"
  87. * "dsi_phy_regulator"
  88. - clock-cells: Must be 1. The DSI PHY block acts as a clock provider, creating
  89. 2 clocks: A byte clock (index 0), and a pixel clock (index 1).
  90. - qcom,dsi-phy-index: The ID of DSI PHY hardware instance. This should
  91. be 0 or 1, since we have 2 DSI PHYs at most for now.
  92. - power-domains: Should be <&mmcc MDSS_GDSC>.
  93. - clocks: Phandles to device clocks. See [1] for details on clock bindings.
  94. - clock-names: the following clocks are required:
  95. * "iface_clk"
  96. - vddio-supply: phandle to vdd-io regulator device node
  97. Optional properties:
  98. - qcom,dsi-phy-regulator-ldo-mode: Boolean value indicating if the LDO mode PHY
  99. regulator is wanted.
  100. [1] Documentation/devicetree/bindings/clocks/clock-bindings.txt
  101. [2] Documentation/devicetree/bindings/graph.txt
  102. [3] Documentation/devicetree/bindings/media/video-interfaces.txt
  103. [4] Documentation/devicetree/bindings/display/panel/
  104. Example:
  105. dsi0: dsi@fd922800 {
  106. compatible = "qcom,mdss-dsi-ctrl";
  107. qcom,dsi-host-index = <0>;
  108. interrupt-parent = <&mdp>;
  109. interrupts = <4 0>;
  110. reg-names = "dsi_ctrl";
  111. reg = <0xfd922800 0x200>;
  112. power-domains = <&mmcc MDSS_GDSC>;
  113. clock-names =
  114. "bus_clk",
  115. "byte_clk",
  116. "core_clk",
  117. "core_mmss_clk",
  118. "iface_clk",
  119. "mdp_core_clk",
  120. "pixel_clk";
  121. clocks =
  122. <&mmcc MDSS_AXI_CLK>,
  123. <&mmcc MDSS_BYTE0_CLK>,
  124. <&mmcc MDSS_ESC0_CLK>,
  125. <&mmcc MMSS_MISC_AHB_CLK>,
  126. <&mmcc MDSS_AHB_CLK>,
  127. <&mmcc MDSS_MDP_CLK>,
  128. <&mmcc MDSS_PCLK0_CLK>;
  129. assigned-clocks =
  130. <&mmcc BYTE0_CLK_SRC>,
  131. <&mmcc PCLK0_CLK_SRC>;
  132. assigned-clock-parents =
  133. <&dsi_phy0 0>,
  134. <&dsi_phy0 1>;
  135. vdda-supply = <&pma8084_l2>;
  136. vdd-supply = <&pma8084_l22>;
  137. vddio-supply = <&pma8084_l12>;
  138. phys = <&dsi_phy0>;
  139. phy-names ="dsi-phy";
  140. qcom,dual-dsi-mode;
  141. qcom,master-dsi;
  142. qcom,sync-dual-dsi;
  143. pinctrl-names = "default", "sleep";
  144. pinctrl-0 = <&dsi_active>;
  145. pinctrl-1 = <&dsi_suspend>;
  146. ports {
  147. #address-cells = <1>;
  148. #size-cells = <0>;
  149. port@0 {
  150. reg = <0>;
  151. dsi0_in: endpoint {
  152. remote-endpoint = <&mdp_intf1_out>;
  153. };
  154. };
  155. port@1 {
  156. reg = <1>;
  157. dsi0_out: endpoint {
  158. remote-endpoint = <&panel_in>;
  159. data-lanes = <0 1 2 3>;
  160. };
  161. };
  162. };
  163. panel: panel@0 {
  164. compatible = "sharp,lq101r1sx01";
  165. reg = <0>;
  166. link2 = <&secondary>;
  167. power-supply = <...>;
  168. backlight = <...>;
  169. port {
  170. panel_in: endpoint {
  171. remote-endpoint = <&dsi0_out>;
  172. };
  173. };
  174. };
  175. };
  176. dsi_phy0: dsi-phy@fd922a00 {
  177. compatible = "qcom,dsi-phy-28nm-hpm";
  178. qcom,dsi-phy-index = <0>;
  179. reg-names =
  180. "dsi_pll",
  181. "dsi_phy",
  182. "dsi_phy_regulator";
  183. reg = <0xfd922a00 0xd4>,
  184. <0xfd922b00 0x2b0>,
  185. <0xfd922d80 0x7b>;
  186. clock-names = "iface_clk";
  187. clocks = <&mmcc MDSS_AHB_CLK>;
  188. #clock-cells = <1>;
  189. vddio-supply = <&pma8084_l12>;
  190. qcom,dsi-phy-regulator-ldo-mode;
  191. };