4.4-stable review patch.  If anyone has any objections, please let me know.

------------------

This reverts commit 11bf4a8e1d5a300b38ca4bbe1156716b0174f2da which is
commit 2e644be30fcc08c736f66b60f4898d274d4873ab upstream.

Ben pointed out that there is no driver or device trees referencing this
device in 4.4-stable, so the patch should not be present there.

Reported-by: Ben Hutchings <[email protected]>
Cc: Bartosz Golaszewski <[email protected]>
Cc: Laurent Pinchart <[email protected]>
Cc: Rob Herring <[email protected]>
Cc: Archit Taneja <[email protected]>
Cc: Sasha Levin <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
 Documentation/devicetree/bindings/display/bridge/ti,ths8135.txt |   46 
----------
 1 file changed, 46 deletions(-)
 delete mode 100644 
Documentation/devicetree/bindings/display/bridge/ti,ths8135.txt

--- a/Documentation/devicetree/bindings/display/bridge/ti,ths8135.txt
+++ /dev/null
@@ -1,46 +0,0 @@
-THS8135 Video DAC
------------------
-
-This is the binding for Texas Instruments THS8135 Video DAC bridge.
-
-Required properties:
-
-- compatible: Must be "ti,ths8135"
-
-Required nodes:
-
-This device has two video ports. Their connections are modelled using the OF
-graph bindings specified in Documentation/devicetree/bindings/graph.txt.
-
-- Video port 0 for RGB input
-- Video port 1 for VGA output
-
-Example
--------
-
-vga-bridge {
-       compatible = "ti,ths8135";
-       #address-cells = <1>;
-       #size-cells = <0>;
-
-       ports {
-               #address-cells = <1>;
-               #size-cells = <0>;
-
-               port@0 {
-                       reg = <0>;
-
-                       vga_bridge_in: endpoint {
-                               remote-endpoint = <&lcdc_out_vga>;
-                       };
-               };
-
-               port@1 {
-                       reg = <1>;
-
-                       vga_bridge_out: endpoint {
-                               remote-endpoint = <&vga_con_in>;
-                       };
-               };
-       };
-};


Reply via email to