On Monday 09 March 2009 23:29:27 ext Menon, Nishanth wrote:
Further, we have multiple sensors following CCI[1] - why not have a driver
for the same, it will simplify the entire process - ov3640, mt9p012 both
follow the spec at least.. dependency would be sensor - cci dev-i2c
framework.
-D/Helsinki); DongSoo(Nathaniel) Kim; MiaoStanley; Nagalla,
Hari; Hiremath, Vaibhav; Lakhani, Amish
Subject: Re: [PATCH 3/5] OV3640: Add driver
On Monday 09 March 2009 23:29:27 ext Menon, Nishanth wrote:
Further, we have multiple sensors following CCI[1] - why not have a
driver
Hi Alexey,
-Original Message-
From: Alexey Klimov [mailto:klimov.li...@gmail.com]
snip
--- /dev/null
+++ b/drivers/media/video/ov3640.c
@@ -0,0 +1,2202 @@
+/*
+ * drivers/media/video/ov3640.c
+ *
+ * ov3640 sensor driver
+ *
+ *
+ * Copyright (C) 2008 Texas
; MiaoStanley;
Nagalla, Hari; Hiremath, Vaibhav; Lakhani, Amish; Menon, Nishanth
Subject: Re: [PATCH 3/5] OV3640: Add driver
On Tue, 3 Mar 2009, Aguirre Rodriguez, Sergio Alberto wrote:
+ {
+ /* Note: V4L2 defines RGB565 as:
+*
+* Byte
, Vaibhav; Lakhani, Amish; Menon, Nishanth
Subject: RE: [PATCH 3/5] OV3640: Add driver
+ /* FIXME: QXGA framerate setting forced to 15 FPS */
+ if (isize == QXGA) {
lots of i2c reg writes snip
4));
+ err = ov3640_write_reg(client, OV3640_ISP_YOUT_L
On Tue, 3 Mar 2009, Aguirre Rodriguez, Sergio Alberto wrote:
+ {
+ /* Note: V4L2 defines RGB565 as:
+*
+* Byte 0Byte 1
+* g2 g1 g0 r4 r3 r2 r1 r0 b4 b3 b2 b1 b0 g5 g4 g3
+*
+