diff mbox series

[v5,2/2] dt-bindings: media: add ovti,ovm6211 bindings

Message ID 20220309102215.891001-3-petko.manolov@konsulko.com (mailing list archive)
State New
Headers
Series media: ovm6211: Adds support for OVM6211 |

Commit Message

Petko Manolov March 9, 2022, 10:22 a.m. UTC 
  Omnivision OVM6211 MIPI CSI-2 sensor bindings.

Signed-off-by: Petko Manolov <petko.manolov@konsulko.com>
---
 .../devicetree/bindings/media/i2c/ovm6211.txt | 49 +++++++++++++++++++
 1 file changed, 49 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/media/i2c/ovm6211.txt

Comments

Rob Herring (Arm) March 9, 2022, 1:59 p.m. UTC | #1 
On Wed, Mar 09, 2022 at 12:22:15PM +0200, Petko Manolov wrote:
> Omnivision OVM6211 MIPI CSI-2 sensor bindings.
> 
> Signed-off-by: Petko Manolov <petko.manolov@konsulko.com>
> ---
>  .../devicetree/bindings/media/i2c/ovm6211.txt | 49 +++++++++++++++++++

Not sure how you got to v5 already, but bindings must be in DT schema 
format now.

Rob
Petko Manolov March 9, 2022, 4:20 p.m. UTC | #2 
On 22-03-09 06:59:04, Rob Herring wrote:
> On Wed, Mar 09, 2022 at 12:22:15PM +0200, Petko Manolov wrote:
> > Omnivision OVM6211 MIPI CSI-2 sensor bindings.
> > 
> > Signed-off-by: Petko Manolov <petko.manolov@konsulko.com>
> > ---
> >  .../devicetree/bindings/media/i2c/ovm6211.txt | 49 +++++++++++++++++++
> 
> Not sure how you got to v5 already, but bindings must be in DT schema format
> now.

Easy, the bindings got included to the patch in v5.  Looks like it's going to be
yaml all the way... :)


		Petko
diff mbox series

Patch

diff --git a/Documentation/devicetree/bindings/media/i2c/ovm6211.txt b/Documentation/devicetree/bindings/media/i2c/ovm6211.txt
new file mode 100644
index 000000000000..6883c34106be
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/i2c/ovm6211.txt
@@ -0,0 +1,49 @@ 
+* Omnivision OVM6211 MIPI CSI-2 sensor
+
+The OVM6211 has an image array capable of operating at up to 120 frames per
+second in 400x400 resolution. All required image processing functions including
+exposure control are programmable through the SCCB interface.
+
+
+Required Properties:
+- compatible: shall be "ovti,ovm6211"
+- clocks: reference to the xvclk input clock
+- clock-names: shall be "xvclk"
+- avdd-supply: Analog voltage supply, 2.9 volts
+- dovdd-supply: Digital I/O voltage supply, 1.8 volts
+- dvdd-supply: Digital core voltage supply, 1.8 volts
+- reset-gpios: Low active reset gpio
+- enable-gpios: High active chip enable gpio
+
+The device node shall contain one 'port' child node with an
+'endpoint' subnode for its digital output video port,
+in accordance with the video interface bindings defined in
+Documentation/devicetree/bindings/media/video-interfaces.txt.
+The endpoint optional property 'data-lanes' shall be "<1>".
+
+
+Example:
+
+	&i2c1 {
+		...
+        
+		camera@60 {
+			compatible = "ovti,ovm6211";
+			reg = <0x60>;
+			clocks = <&clk_cam>;
+			clock-names = "xvclk";
+			dovdd-supply = <&v1v8>;
+			avdd-supply = <&vdda>;
+			reset-gpios = <&gpiof 14 GPIO_ACTIVE_LOW>;
+			enable-gpios = <&gpiof 15 GPIO_ACTIVE_HIGH>;
+
+			status = "okay";
+
+			port {
+				ovm6211_0: endpoint {
+					data-lanes = <1>;
+					clock-lanes = <0>;
+					pclk-max-frequency = <72000000>;
+			};
+		};
+	};