[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161207223319.GZ16630@valkosipuli.retiisi.org.uk>
Date: Thu, 8 Dec 2016 00:33:19 +0200
From: Sakari Ailus <sakari.ailus@....fi>
To: Ramiro Oliveira <Ramiro.Oliveira@...opsys.com>
Cc: mchehab@...nel.org, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, robh+dt@...nel.org,
devicetree@...r.kernel.org, davem@...emloft.net,
gregkh@...uxfoundation.org, geert+renesas@...der.be,
akpm@...ux-foundation.org, linux@...ck-us.net, hverkuil@...all.nl,
dheitmueller@...nellabs.com, slongerbeam@...il.com,
lars@...afoo.de, robert.jarzmik@...e.fr, pavel@....cz,
pali.rohar@...il.com, sakari.ailus@...ux.intel.com,
mark.rutland@....com, CARLOS.PALMINHA@...opsys.com
Subject: Re: [PATCH v5 1/2] Add OV5647 device tree documentation
Hi Ramiro,
Thank you for the patch.
On Mon, Dec 05, 2016 at 05:36:33PM +0000, Ramiro Oliveira wrote:
> Add device tree documentation.
>
> Signed-off-by: Ramiro Oliveira <roliveir@...opsys.com>
> ---
> .../devicetree/bindings/media/i2c/ov5647.txt | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txt
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/ov5647.txt b/Documentation/devicetree/bindings/media/i2c/ov5647.txt
> new file mode 100644
> index 0000000..4c91b3b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/ov5647.txt
> @@ -0,0 +1,19 @@
> +Omnivision OV5647 raw image sensor
> +---------------------------------
> +
> +OV5647 is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces
> +and CCI (I2C compatible) control bus.
> +
> +Required properties:
> +
> +- compatible : "ovti,ov5647";
> +- reg : I2C slave address of the sensor;
> +
> +The common video interfaces bindings (see video-interfaces.txt) should be
> +used to specify link to the image data receiver. The OV5647 device
> +node should contain one 'port' child node with an 'endpoint' subnode.
> +
> +Following properties are valid for the endpoint node:
> +
> +- data-lanes : (optional) specifies MIPI CSI-2 data lanes as covered in
> + video-interfaces.txt. The sensor supports only two data lanes.
Doesn't this sensor require a external clock, a reset GPIO and / or a
regulator or a few? Do you need data-lanes, unless you can change the order
or the number?
An example DT snippet wouldn't hurt.
--
Kind regards,
Sakari Ailus
e-mail: sakari.ailus@....fi XMPP: sailus@...iisi.org.uk
Powered by blists - more mailing lists