From: Rob Herring <robh@kernel.org>
To: roliveir <Ramiro.Oliveira@synopsys.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
mchehab@osg.samsung.com, CARLOS.PALMINHA@synopsys.com
Subject: Re: [RFC 1/2] Add OV5647 device tree documentation
Date: Wed, 25 May 2016 13:59:08 -0500 [thread overview]
Message-ID: <20160525185908.GA12900@rob-hp-laptop> (raw)
In-Reply-To: <c98fab2075cefbe155c99b99f7b09cdad67514a8.1464112779.git.roliveir@synopsys.com>
On Tue, May 24, 2016 at 07:16:47PM +0100, roliveir wrote:
> Signed-off-by: roliveir <roliveir@synopsys.com>
> ---
> .../devicetree/bindings/media/i2c/ov5647.txt | 29 ++++++++++++++++++++++
> 1 file changed, 29 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..fa6b09c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/ov5647.txt
> @@ -0,0 +1,29 @@
> +Omnivision OV5657 raw image sensor
5657?
> +---------------------------------
> +
> +OV5657 is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces
> +and CCI (I2C compatible) control bus.
> +
> +Required properties:
> +
> +- compatible : "ov5647";
> +- reg : I2C slave address of the sensor;
> +- clocks : should contain list of phandle and clock specifier pairs
> + according to common clock bindings for the clocks described
> + in the clock-names property;
Need to state how many clocks and the order.
> +- clock-names : should contain "extclk" entry for the sensor's EXTCLK clock;
> +
> +Optional properties:
> +
> +- clock-frequency : the frequency at which the "extclk" clock should be
> + configured to operate, in Hz; if this property is not
> + specified default 27 MHz value will be used.
> +
> +The common video interfaces bindings (see video-interfaces.txt) should be
> +used to specify link to the image data receiver. The OV5657 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.
> --
> 2.8.1
>
>
next prev parent reply other threads:[~2016-05-25 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 18:16 [RFC 0/2] Add support for OV5647 sensor roliveir
2016-05-24 18:16 ` [RFC 1/2] Add OV5647 device tree documentation roliveir
2016-05-25 18:59 ` Rob Herring [this message]
2016-05-24 18:16 ` [RFC 2/2] Add support for Omnivision OV5647 roliveir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160525185908.GA12900@rob-hp-laptop \
--to=robh@kernel.org \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=Ramiro.Oliveira@synopsys.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).