This patch allows drivers to modify cam_mclk rate which is
used for generating external cam_xclka and cam_xclkb for cameras.
Signed-off-by: Tuukka Toivonen
---
arch/arm/mach-omap2/clock34xx.c | 18 ++
arch/arm/mach-omap2/clock34xx.h |2 ++
2 files changed, 20 insertions(+),
On Wednesday 01 July 2009 14:27:28 Tuukka.O Toivonen wrote:
> This patch allows drivers to modify cam_mclk rate which is
> used for generating external cam_xclka and cam_xclkb for cameras.
I'm terribly sorry, this patch was misapplied to the
kernel tree. I send the patch again.
- T
This patch allows drivers to modify cam_mclk rate which is
used for generating external cam_xclka and cam_xclkb for cameras.
Signed-off-by: Tuukka Toivonen
---
arch/arm/mach-omap2/clock34xx.c | 18 ++
arch/arm/mach-omap2/clock34xx.h |2 ++
2 files changed, 20 insertions(+),
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.
On Wednesday 04 March 2009 09:39:48 ext Hans Verkuil wrote:
> BTW, do I understand correctly that e.g. lens drivers also get their
> own /dev/videoX node? Please tell me I'm mistaken! Since that would be so
> very wrong.
You're mistaken :)
With the v4l2-int-interface/omap34xxcam camera driver o
Signed-off-by: Tuukka Toivonen
---
include/linux/i2c/twl4030.h | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/include/linux/i2c/twl4030.h b/include/linux/i2c/twl4030.h
index c89d33b..c4fe1b6 100644
--- a/include/linux/i2c/twl4030.h
+++ b/include/linux/i2c/twl4
Signed-off-by: Tuukka Toivonen
---
include/linux/i2c/twl4030.h | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/include/linux/i2c/twl4030.h b/include/linux/i2c/twl4030.h
index c89d33b..c4fe1b6 100644
--- a/include/linux/i2c/twl4030.h
+++ b/include/linux/i2c/twl40
On Monday 23 February 2009 10:08:54 ext DongSoo(Nathaniel) Kim wrote:
> So, logically it does not make sense with making device nodes of every
> single slave attached with OMAP3camera interface. Because they can't
> be opened at the same time,even if it is possible it should not work
> properly.
>
On Tuesday 13 January 2009 09:34:16 ext Hans Verkuil wrote:
> second entry rather than the third. There are more devices that can
> choose between color and B&W, but this is the first device I know of
> that can do sepia. Having B&W as the second entry makes it easier for
Actually OMAP3 ISP can
