@@ -0,0 +1,26 @@+DVI Connector+=======++Required properties:+- compatible: "dvi-connector"++Optional properties:+- label: a symbolic name for the connector+- i2c-bus: phandle to the i2c bus that is connected to DVI DDC++Required nodes:+- Video port for DVI input++Example+-------++dvi0: connector@0 {+ compatible = "dvi-connector";+ label = "dvi";++ i2c-bus = <&i2c3>;++ dvi_connector_in: endpoint {+ remote-endpoint = <&tfp410_out>;+ };+};
@@ -0,0 +1,26 @@+DVI Connector+=======++Required properties:+- compatible: "dvi-connector"++Optional properties:+- label: a symbolic name for the connector+- i2c-bus: phandle to the i2c bus that is connected to DVI DDC
For the i.MX bindings I had called this property 'ddc', but
Documentation/devicetree/bindings/panel/simple-panel.txt already
uses 'ddc-i2c-bus'. We should definitely standardize this.
quoted hunk
+Required nodes:+- Video port for DVI input++Example+-------++dvi0: connector@0 {+ compatible = "dvi-connector";+ label = "dvi";++ i2c-bus = <&i2c3>;++ dvi_connector_in: endpoint {+ remote-endpoint = <&tfp410_out>;+ };+};
@@ -0,0 +1,26 @@+DVI Connector+==============++Required properties:+- compatible: "dvi-connector"++Optional properties:+- label: a symbolic name for the connector+- i2c-bus: phandle to the i2c bus that is connected to DVI DDC
For the i.MX bindings I had called this property 'ddc', but
Documentation/devicetree/bindings/panel/simple-panel.txt already
uses 'ddc-i2c-bus'. We should definitely standardize this.