From: Rui Miguel Silva <rui.silva@linaro.org>
To: jacopo mondi <jacopo@jmondi.org>
Cc: Rui Miguel Silva <rui.silva@linaro.org>,
mchehab@kernel.org, sakari.ailus@linux.intel.com,
hverkuil@xs4all.nl, linux-media@vger.kernel.org,
Fabio Estevam <fabio.estevam@nxp.com>,
Ryan Harkin <ryan.harkin@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v7 1/2] media: ov2680: dt: Add bindings for OV2680
Date: Wed, 04 Jul 2018 16:51:59 +0100 [thread overview]
Message-ID: <m3a7r7robk.fsf@linaro.org> (raw)
In-Reply-To: <20180704085801.GB4463@w540>
Hi Jacopo,
Hope your fine.
Thanks for the review.
On Wed 04 Jul 2018 at 09:58, jacopo mondi wrote:
> Hi Rui,
> sorry, I'm a bit late, you're already at v7 and I don't want
> to
> slow down inclusion with a few minor comments.
>
> Please bear with me and see below...
>
> On Tue, Jul 03, 2018 at 03:08:02PM +0100, Rui Miguel Silva
> wrote:
>> Add device tree binding documentation for the OV2680 camera
>> sensor.
>>
>> CC: devicetree@vger.kernel.org
>> Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
>> ---
>> .../devicetree/bindings/media/i2c/ov2680.txt | 46
>> +++++++++++++++++++
>> 1 file changed, 46 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..11e925ed9dad
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/media/i2c/ov2680.txt
>> @@ -0,0 +1,46 @@
>> +* 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".
>
> Having a single clock source I think you can omit 'clock-names'
> (or at
> least not marking it as required)
yeah, I see you point, but really all other OV sensors share this
and
the bellow clock/data-lanes properties as required, I will let Rob
or
Sakari take a call in this one.
---
Cheers,
Rui
>
>> +- DOVDD-supply: Digital I/O voltage supply.
>> +- DVDD-supply: Digital core voltage supply.
>> +- AVDD-supply: Analog voltage supply.
>> +
>> +Optional Properties:
>> +- reset-gpios: reference to the GPIO connected to the
>> powerdown/reset pin,
>> + if any. This is an active low signal to the
>> OV2680.
>> +
>> +The device node must contain one 'port' child node for its
>> digital output
>> +video port, and this port must have a single endpoint in
>> accordance with
>> + the video interface bindings defined in
>> +Documentation/devicetree/bindings/media/video-interfaces.txt.
>> +
>> +Endpoint node required properties for CSI-2 connection are:
>> +- remote-endpoint: a phandle to the bus receiver's endpoint
>> node.
>> +- clock-lanes: should be set to <0> (clock lane on hardware
>> lane 0).
>> +- data-lanes: should be set to <1> (one CSI-2 lane supported).
>
> What is the value of marking as required two properties which
> can only have
> default values (the sensor does not support clock on different
> lanes,
> nor it supports more than 1 data lane) ?
>
> Thanks
> j
>
>> +
>> +Example:
>> +
>> +&i2c2 {
>> + ov2680: camera-sensor@36 {
>> + compatible = "ovti,ov2680";
>> + reg = <0x36>;
>> + clocks = <&osc>;
>> + clock-names = "xvclk";
>> + reset-gpios = <&gpio1 3 GPIO_ACTIVE_LOW>;
>> + DOVDD-supply = <&sw2_reg>;
>> + DVDD-supply = <&sw2_reg>;
>> + AVDD-supply = <®_peri_3p15v>;
>> +
>> + port {
>> + ov2680_to_mipi: endpoint {
>> + remote-endpoint =
>> <&mipi_from_sensor>;
>> + clock-lanes = <0>;
>> + data-lanes = <1>;
>> + };
>> + };
>> + };
>> +};
>> --
>> 2.18.0
>>
next prev parent reply other threads:[~2018-07-04 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180703140803.19580-1-rui.silva@linaro.org>
2018-07-03 14:08 ` [PATCH v7 1/2] media: ov2680: dt: Add bindings for OV2680 Rui Miguel Silva
2018-07-03 16:27 ` Rob Herring
2018-07-04 8:58 ` jacopo mondi
2018-07-04 15:51 ` Rui Miguel Silva [this message]
2018-07-05 20:11 ` Rob Herring
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=m3a7r7robk.fsf@linaro.org \
--to=rui.silva@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=hverkuil@xs4all.nl \
--cc=jacopo@jmondi.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).