On Thu, Jan 09, 2014 at 12:03:24PM +0100, Jean-Francois Moine wrote:
> diff --git a/Documentation/devicetree/bindings/drm/i2c/tda998x.txt b/Documentation/devicetree/bindings/drm/i2c/tda998x.txt
> new file mode 100644
> index 0000000..f07339e1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/drm/i2c/tda998x.txt
> @@ -0,0 +1,16 @@
> +Device-Tree bindings for the NXP TDA998x HDMI transmitter
> +
> +Required properties;
> + - compatible: must be "nxp,tda998x"
> +
> +Optional properties:
> + - video-ports: 24 bits value - default: <0x230145>
> +
> +Example:
> +
> + tda998x: hdmi-encoder {
> + compatible = "nxp,tda998x";
> + reg = <0x70>;
> + pinctrl-0 = <&pmx_camera>;
> + pinctrl-names = "default";
This example seems to be meaningless. What SoC pinctrl settings are there
on this device? What has a HDMI encoder got to do with a camera?
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
