[PATCH 4/9] Doc/DT: Add DT binding documentation for HDMI Connector (original) (raw)

Russell King - ARM Linux linux at arm.linux.org.uk
Fri Feb 28 08:06:12 PST 2014

On Fri, Feb 28, 2014 at 02:20:11PM +0200, Tomi Valkeinen wrote:

Add DT binding documentation for HDMI Connector.

Signed-off-by: Tomi Valkeinen <tomi.valkeinen at ti.com> Reviewed-by: Archit Taneja <archit at ti.com> --- .../devicetree/bindings/video/hdmi-connector.txt | 23 ++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 Documentation/devicetree/bindings/video/hdmi-connector.txt diff --git a/Documentation/devicetree/bindings/video/hdmi-connector.txt b/Documentation/devicetree/bindings/video/hdmi-connector.txt new file mode 100644 index 000000000000..5d25f6a432bb --- /dev/null +++ b/Documentation/devicetree/bindings/video/hdmi-connector.txt @@ -0,0 +1,23 @@ +HDMI Connector +============== + +Required properties: +- compatible: "hdmi-connector" + +Optional properties: +- label: a symbolic name for the connector + +Required nodes: +- Video port for HDMI input + +Example +------- + +hdmi0: connector at 1 { + compatible = "hdmi-connector"; + label = "hdmi"; + + hdmiconnectorin: endpoint { + remote-endpoint = <&tpd12s015out>; + }; +};

It seems rather weird to have DVI connectors having an optional I2C property, but HDMI (which augments DVI) not having that as at least an optional property.

I can quite well see the iMX HDMI support needing an i2c bus here.

Also, HDMI has two connector standards - type A and type B, much like the single vs dual link of DVI. Again, DRM exposes this to userspace.

-- FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly improving, and getting towards what was expected from it.

More information about the dri-devel mailing list