public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Todor Tomov <todor.tomov@linaro.org>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	mchehab@osg.samsung.com, hverkuil@xs4all.nl,
	geert@linux-m68k.org, matrandg@cisco.com, sakari.ailus@iki.fi,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v6 1/2] media: i2c/ov5645: add the device tree binding document
Date: Wed, 19 Oct 2016 11:49:18 +0300	[thread overview]
Message-ID: <5771512.gQUqkxEut4@avalon> (raw)
In-Reply-To: <5800C904.8080002@linaro.org>

Hi Todor,

On Friday 14 Oct 2016 15:01:08 Todor Tomov wrote:
> On 09/08/2016 03:22 PM, Laurent Pinchart wrote:
> > On Thursday 08 Sep 2016 12:13:54 Todor Tomov wrote:
> >> Add the document for ov5645 device tree binding.
> >> 
> >> Signed-off-by: Todor Tomov <todor.tomov@linaro.org>
> >> ---
> >> 
> >>  .../devicetree/bindings/media/i2c/ov5645.txt       | 52 ++++++++++++++++
> >>  1 file changed, 52 insertions(+)
> >>  create mode 100644
> >>  Documentation/devicetree/bindings/media/i2c/ov5645.txt
> >> 
> >> diff --git a/Documentation/devicetree/bindings/media/i2c/ov5645.txt
> >> b/Documentation/devicetree/bindings/media/i2c/ov5645.txt new file mode
> >> 100644
> >> index 0000000..bcf6dba
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/media/i2c/ov5645.txt
> >> @@ -0,0 +1,52 @@
> >> +* Omnivision 1/4-Inch 5Mp CMOS Digital Image Sensor
> >> +
> >> +The Omnivision OV5645 is a 1/4-Inch CMOS active pixel digital image
> >> sensor with
> >> +an active array size of 2592H x 1944V. It is programmable through a
> >> serial I2C
> >> +interface.
> >> +
> >> +Required Properties:
> >> +- compatible: Value should be "ovti,ov5645".
> >> +- clocks: Reference to the xclk clock.
> >> +- clock-names: Should be "xclk".
> >> +- clock-frequency: Frequency of the xclk clock.
> >> +- enable-gpios: Chip enable GPIO. Polarity is GPIO_ACTIVE_HIGH.

By the way, isn't the pin called pwdnb and isn't it active low ?

> >> +- reset-gpios: Chip reset GPIO. Polarity is GPIO_ACTIVE_LOW.
> > 
> > Shouldn't the enable and reset GPIOs be optional ?
> 
> I don't think so. The operations on the GPIOs are part of the power up
> sequence of the sensor so we must have control over them to execute the
> exact sequence.

Right, let's keep them mandatory. If we later have to make them optional for a 
board that pulls one of those signals up (assuming this can work at all) we'll 
revisit the bindings.

> >> +- vdddo-supply: Chip digital IO regulator.
> >> +- vdda-supply: Chip analog regulator.
> >> +- vddd-supply: Chip digital core regulator.
> >> +
> >> +The device node must contain one 'port' child node for its digital
> >> output
> >> +video port, in accordance with the video interface bindings defined in
> >> +Documentation/devicetree/bindings/media/video-interfaces.txt.
> >> +
> >> +Example:
> >> +
> >> +	&i2c1 {
> >> +		...
> >> +
> >> +		ov5645: ov5645@78 {
> >> +			compatible = "ovti,ov5645";
> >> +			reg = <0x78>;
> >> +
> >> +			enable-gpios = <&gpio1 6 GPIO_ACTIVE_HIGH>;
> >> +			reset-gpios = <&gpio5 20 GPIO_ACTIVE_LOW>;
> >> +			pinctrl-names = "default";
> >> +			pinctrl-0 = <&camera_rear_default>;
> >> +
> >> +			clocks = <&clks 200>;
> >> +			clock-names = "xclk";
> >> +			clock-frequency = <23880000>;
> >> +
> >> +			vdddo-supply = <&camera_dovdd_1v8>;
> >> +			vdda-supply = <&camera_avdd_2v8>;
> >> +			vddd-supply = <&camera_dvdd_1v2>;
> >> +
> >> +			port {
> >> +				ov5645_ep: endpoint {
> >> +					clock-lanes = <1>;
> >> +					data-lanes = <0 2>;
> >> +					remote-endpoint = <&csi0_ep>;
> >> +				};
> >> +			};
> >> +		};
> >> +	};

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2016-10-19 14:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08  9:13 [PATCH v6 0/2] OV5645 camera sensor driver Todor Tomov
2016-09-08  9:13 ` [PATCH v6 1/2] media: i2c/ov5645: add the device tree binding document Todor Tomov
2016-09-08 12:22   ` Laurent Pinchart
2016-10-14 12:01     ` Todor Tomov
2016-10-19  8:49       ` Laurent Pinchart [this message]
2016-10-19  9:14         ` Todor Tomov
2016-10-19  9:21           ` Laurent Pinchart
2016-10-26 18:53             ` Rob Herring
2016-11-01  8:24               ` Todor Tomov
2016-11-03  0:06                 ` Laurent Pinchart
2016-09-08  9:13 ` [PATCH v6 2/2] media: Add a driver for the ov5645 camera sensor Todor Tomov
2016-09-08 12:22   ` Laurent Pinchart
2016-10-14 11:57     ` Todor Tomov
2016-10-19  8:44       ` Laurent Pinchart
2016-10-26 11:15         ` Todor Tomov
2016-10-26 11:27           ` Todor Tomov
2016-10-26 11:51             ` Mark Brown
2016-11-14 12:18               ` Laurent Pinchart
2016-11-14 13:46                 ` Mark Brown
2016-10-26 12:48             ` Ian Arkver
2016-10-26 14:07               ` Todor Tomov
2016-10-26 16:48                 ` Ian Arkver
2016-10-27  7:50                   ` Todor Tomov

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=5771512.gQUqkxEut4@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=galak@codeaurora.org \
    --cc=geert@linux-m68k.org \
    --cc=hverkuil@xs4all.nl \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-media@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=matrandg@cisco.com \
    --cc=mchehab@osg.samsung.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=todor.tomov@linaro.org \
    /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