Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 6d2ca852 authored by Laurent Pinchart's avatar Laurent Pinchart
Browse files

dt-bindings: display: renesas: Deprecate LVDS support in the DU bindings 



The internal LVDS encoders now have their own DT bindings, representing
them as part of the DU is deprecated.

Signed-off-by: default avatarLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Reviewed-by: default avatarRob Herring <robh@kernel.org>
Reviewed-by: default avatarNiklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
parent 871b4560

Documentation/devicetree/bindings/display/renesas,du.txt

+11 −20
Original line number Diff line number Diff line
@@ -14,12 +14,7 @@ Required Properties: 
    - "renesas,du-r8a7795" for R8A7795 (R-Car H3) compatible DU

    - "renesas,du-r8a7796" for R8A7796 (R-Car M3-W) compatible DU



  - reg: A list of base address and length of each memory resource, one for

    each entry in the reg-names property.

  - reg-names: Name of the memory resources. The DU requires one memory

    resource for the DU core (named "du") and one memory resource for each

    LVDS encoder (named "lvds.x" with "x" being the LVDS controller numerical

    index).

  - reg: the memory-mapped I/O registers base address and length



  - interrupt-parent: phandle of the parent interrupt controller.

  - interrupts: Interrupt specifiers for the DU interrupts.
@@ -29,14 +24,13 @@ Required Properties: 
  - clock-names: Name of the clocks. This property is model-dependent.

    - R8A7779 uses a single functional clock. The clock doesn't need to be

      named.

    - All other DU instances use one functional clock per channel and one

      clock per LVDS encoder (if available). The functional clocks must be

      named "du.x" with "x" being the channel numerical index. The LVDS clocks

      must be named "lvds.x" with "x" being the LVDS encoder numerical index.

    - In addition to the functional and encoder clocks, all DU versions also

      support externally supplied pixel clocks. Those clocks are optional.

      When supplied they must be named "dclkin.x" with "x" being the input

      clock numerical index.

    - All other DU instances use one functional clock per channel The

      functional clocks must be named "du.x" with "x" being the channel

      numerical index.

    - In addition to the functional clocks, all DU versions also support

      externally supplied pixel clocks. Those clocks are optional. When

      supplied they must be named "dclkin.x" with "x" being the input clock

      numerical index.



  - vsps: A list of phandle and channel index tuples to the VSPs that handle

    the memory interfaces for the DU channels. The phandle identifies the VSP
@@ -69,9 +63,7 @@ Example: R8A7795 (R-Car H3) ES2.0 DU 


	du: display@feb00000 {

		compatible = "renesas,du-r8a7795";

		reg = <0 0xfeb00000 0 0x80000>,

		      <0 0xfeb90000 0 0x14>;

		reg-names = "du", "lvds.0";

		reg = <0 0xfeb00000 0 0x80000>;

		interrupts = <GIC_SPI 256 IRQ_TYPE_LEVEL_HIGH>,

			     <GIC_SPI 268 IRQ_TYPE_LEVEL_HIGH>,

			     <GIC_SPI 269 IRQ_TYPE_LEVEL_HIGH>,
@@ -79,9 +71,8 @@ Example: R8A7795 (R-Car H3) ES2.0 DU 
		clocks = <&cpg CPG_MOD 724>,

			 <&cpg CPG_MOD 723>,

			 <&cpg CPG_MOD 722>,

			 <&cpg CPG_MOD 721>,

			 <&cpg CPG_MOD 727>;

		clock-names = "du.0", "du.1", "du.2", "du.3", "lvds.0";

			 <&cpg CPG_MOD 721>;

		clock-names = "du.0", "du.1", "du.2", "du.3";

		vsps = <&vspd0 0>, <&vspd1 0>, <&vspd2 0>, <&vspd0 1>;



		ports {