From: Rui Miguel Silva <rui.silva@linaro.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: mchehab@kernel.org, hverkuil@xs4all.nl,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Ryan Harkin <ryan.harkin@linaro.org>,
Rui Miguel Silva <rui.silva@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] media: ov2680: dt: Add bindings for OV2680
Date: Fri, 23 Feb 2018 14:56:41 +0000 [thread overview]
Message-ID: <m3k1v3kb4m.fsf@linaro.org> (raw)
In-Reply-To: <20180222105932.t4j7ranj2qp4jhj6@paasikivi.fi.intel.com>
Hi Sakari,
Thanks for the review.
On Thu 22 Feb 2018 at 10:59, Sakari Ailus wrote:
> Hi Rui,
>
> Thanks for the patchset.
>
> Could you use "dt: bindings: " prefix in the subject?
Sure, no problem.
>
> On Thu, Feb 22, 2018 at 10:23:37AM +0000, Rui Miguel Silva
> wrote:
>> Add device tree binding documentation for the OV5640 camera
>> sensor.
>>
>> CC: devicetree@vger.kernel.org
>> Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
>> ---
>> .../devicetree/bindings/media/i2c/ov2680.txt | 34
>> ++++++++++++++++++++++
>> 1 file changed, 34 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/media/i2c/ov2680.txt
>>
>> diff --git
>> a/Documentation/devicetree/bindings/media/i2c/ov2680.txt
>> b/Documentation/devicetree/bindings/media/i2c/ov2680.txt
>> new file mode 100644
>> index 000000000000..f9dc63ce5044
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/media/i2c/ov2680.txt
>> @@ -0,0 +1,34 @@
>> +* Omnivision OV2680 MIPI CSI-2 sensor
>> +
>> +Required Properties:
>> +- compatible: should be "ovti,ov2680"
>> +- clocks: reference to the xvclk input clock.
>> +- clock-names: should be "xvclk".
>> +
>> +Optional Properties:
>> +- powerdown-gpios: reference to the GPIO connected to the
>> powerdown pin,
>> + if any. This is an active high signal to the
>> OV2680.
>> +
>> +The device node must contain one 'port' child node for its
>> digital output
>
> Please add that the port contains a single endpoint as well.
Ack.
>
>> +video port, in accordance with the video interface bindings
>> defined in
>> +Documentation/devicetree/bindings/media/video-interfaces.txt.
>
> Please list required and optional endpoint properties as well.
OK.
---
Cheers,
Rui
>
>> +
>> +Example:
>> +
>> +&i2c2 {
>> + ov2680: camera-sensor@36 {
>> + compatible = "ovti,ov2680";
>> + reg = <0x36>;
>> + clocks = <&osc>;
>> + clock-names = "xvclk";
>> + powerdown-gpios = <&gpio1 3 GPIO_ACTIVE_HIGH>;
>> +
>> + port {
>> + ov2680_mipi_ep: endpoint {
>> + remote-endpoint =
>> <&mipi_sensor_ep>;
>> + clock-lanes = <0>;
>> + data-lanes = <1>;
>> + };
>> + };
>> + };
>> +};
next prev parent reply other threads:[~2018-02-23 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180222102338.28896-1-rui.silva@linaro.org>
2018-02-22 10:23 ` [PATCH 1/2] media: ov2680: dt: Add bindings for OV2680 Rui Miguel Silva
2018-02-22 10:59 ` Sakari Ailus
2018-02-23 14:56 ` Rui Miguel Silva [this message]
2018-02-22 11:31 ` Fabio Estevam
2018-02-23 14:57 ` Rui Miguel Silva
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=m3k1v3kb4m.fsf@linaro.org \
--to=rui.silva@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ryan.harkin@linaro.org \
--cc=sakari.ailus@linux.intel.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).