mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>
To: Sakari Ailus <sakari.ailus@iki.fi>,
	Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>
Cc: <mchehab@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-media@vger.kernel.org>, <robh+dt@kernel.org>,
	<devicetree@vger.kernel.org>, <davem@davemloft.net>,
	<gregkh@linuxfoundation.org>, <geert+renesas@glider.be>,
	<akpm@linux-foundation.org>, <linux@roeck-us.net>,
	<hverkuil@xs4all.nl>, <dheitmueller@kernellabs.com>,
	<slongerbeam@gmail.com>, <lars@metafoo.de>,
	<robert.jarzmik@free.fr>, <pavel@ucw.cz>, <pali.rohar@gmail.com>,
	<sakari.ailus@linux.intel.com>, <mark.rutland@arm.com>,
	<CARLOS.PALMINHA@synopsys.com>
Subject: Re: [PATCH v5 1/2] Add OV5647 device tree documentation
Date: Mon, 12 Dec 2016 11:39:31 +0000	[thread overview]
Message-ID: <cc5229b9-0705-4189-39d5-7c3e0a96c008@synopsys.com> (raw)
In-Reply-To: <20161207223319.GZ16630@valkosipuli.retiisi.org.uk>

Hi Sakari,

Thank you for the feedback.

On 12/7/2016 10:33 PM, Sakari Ailus wrote:
> 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@synopsys.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?

In the setup I'm using, I'm not aware of any reset GPIO or regulator. I do use a
external clock but it's fixed and not controlled by SW. Should I add a property
for this?

> 
> An example DT snippet wouldn't hurt.

Sure, I can add a example snippet.

> 

  reply	other threads:[~2016-12-12 11:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 17:36 [PATCH v5 0/2] Add support for Omnivision OV5647 Ramiro Oliveira
2016-12-05 17:36 ` [PATCH v5 1/2] Add OV5647 device tree documentation Ramiro Oliveira
2016-12-07 22:33   ` Sakari Ailus
2016-12-12 11:39     ` Ramiro Oliveira [this message]
2016-12-12 11:49       ` Sakari Ailus
2016-12-12 12:15         ` Ramiro Oliveira
2016-12-12 12:19           ` Sakari Ailus
2016-12-12 13:07             ` Ramiro Oliveira
2016-12-12 15:12               ` Sakari Ailus
2016-12-05 17:36 ` [PATCH v5 2/2] Add support for OV5647 sensor Ramiro Oliveira
2016-12-07 23:01   ` Sakari Ailus
2016-12-12 11:39     ` Ramiro Oliveira
2016-12-12 11:54       ` Sakari Ailus

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=cc5229b9-0705-4189-39d5-7c3e0a96c008@synopsys.com \
    --to=ramiro.oliveira@synopsys.com \
    --cc=CARLOS.PALMINHA@synopsys.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dheitmueller@kernellabs.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=hverkuil@xs4all.nl \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=robert.jarzmik@free.fr \
    --cc=robh+dt@kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=sakari.ailus@linux.intel.com \
    --cc=slongerbeam@gmail.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

all inboxes | Powered by JetHome®