* Using OV5642 sensor driver for CM8206-A500SA-E
@ 2012-11-06 9:14 Anatolij Gustschin
2012-11-06 9:44 ` Bastian Hecht
[not found] ` <CABYn4sxjZjiEt+=JC0vxXHFkCbHbuMRqTrAzgP_y-XKNsnSDHA@mail.gmail.com>
0 siblings, 2 replies; 3+ messages in thread
From: Anatolij Gustschin @ 2012-11-06 9:14 UTC (permalink / raw)
To: linux-media; +Cc: Bastian Hecht
Hi,
I'm trying to use mainline ov5642 driver for ov5642 based camera
module CM8206-A500SA-E from TRULY. The driver loads and initializes
the sensor, but the initialization seems to be incomplete, the sensor
doesn't generate pixel clock and sync signals.
For a quick test I've replaced the default initialisation sequences
from ov5642_default_regs_init[] and ov5642_default_regs_finalise[]
with an init sequence in ov5642_setting_30fps_720P_1280_720[] taken
from Freescale ov5642 driver [1] and commented out ov5642_set_resolution()
in ov5642_s_power(). With these changes to the mainline driver the
sensor starts clocking out pixels and I receive 1280x720 image.
Is anyone using the mainline ov5642 driver for mentioned TRULY camera
module? Just wanted to ask before digging further to find out what
changes to the mainline driver are really needed to make it working
with TRULY camera module.
Thanks,
Anatolij
[1] http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/plain/drivers/media/video/mxc/capture/ov5642.c?h=imx_3.0.15
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Using OV5642 sensor driver for CM8206-A500SA-E
2012-11-06 9:14 Using OV5642 sensor driver for CM8206-A500SA-E Anatolij Gustschin
@ 2012-11-06 9:44 ` Bastian Hecht
[not found] ` <CABYn4sxjZjiEt+=JC0vxXHFkCbHbuMRqTrAzgP_y-XKNsnSDHA@mail.gmail.com>
1 sibling, 0 replies; 3+ messages in thread
From: Bastian Hecht @ 2012-11-06 9:44 UTC (permalink / raw)
To: Anatolij Gustschin; +Cc: Linux Media Mailing List, Bastian Hecht
Hi Anatolij,
if I remember correctly I had the same issue inverted. For me the
initialization sequence of the freescale driver didn't work. Generally
it was quite difficult to deduce anything from the docs to split the
initialization into sensible parts. Too many parts were undocumented
or didn't work as expected. Maybe there are different hardware
revisions out there that need a different register setup.
Unfortunately I can only give you some general notes here as I no
longer possess an OV5642.
Good luck,
Bastian
2012/11/6 Anatolij Gustschin <agust@denx.de>
>
> Hi,
>
> I'm trying to use mainline ov5642 driver for ov5642 based camera
> module CM8206-A500SA-E from TRULY. The driver loads and initializes
> the sensor, but the initialization seems to be incomplete, the sensor
> doesn't generate pixel clock and sync signals.
>
> For a quick test I've replaced the default initialisation sequences
> from ov5642_default_regs_init[] and ov5642_default_regs_finalise[]
> with an init sequence in ov5642_setting_30fps_720P_1280_720[] taken
> from Freescale ov5642 driver [1] and commented out ov5642_set_resolution()
> in ov5642_s_power(). With these changes to the mainline driver the
> sensor starts clocking out pixels and I receive 1280x720 image.
>
> Is anyone using the mainline ov5642 driver for mentioned TRULY camera
> module? Just wanted to ask before digging further to find out what
> changes to the mainline driver are really needed to make it working
> with TRULY camera module.
>
> Thanks,
> Anatolij
>
> [1] http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/plain/drivers/media/video/mxc/capture/ov5642.c?h=imx_3.0.15
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Using OV5642 sensor driver for CM8206-A500SA-E
[not found] ` <CABYn4sxjZjiEt+=JC0vxXHFkCbHbuMRqTrAzgP_y-XKNsnSDHA@mail.gmail.com>
@ 2012-11-06 13:33 ` Anatolij Gustschin
0 siblings, 0 replies; 3+ messages in thread
From: Anatolij Gustschin @ 2012-11-06 13:33 UTC (permalink / raw)
To: Bastian Hecht; +Cc: Linux Media Mailing List
Hi Bastian,
On Tue, 6 Nov 2012 10:38:40 +0100
Bastian Hecht <hechtb@googlemail.com> wrote:
> Hi Anatolij,
>
> if I remember correctly I had the same issue inverted. For me the
> initialization sequence of the freescale driver didn't work. Generally it
> was quite difficult to deduce anything from the docs to split the
> initialization into sensible parts. Too many parts were undocumented or
> didn't work as expected. Maybe there are different hardware revisions out
> there that need a different register setup.
> Unfortunately I can only give you some general notes here as I no longer
> possess an OV5642.
Okay, thanks for the info anyway!
Anatolij
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-11-06 13:33 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-06 9:14 Using OV5642 sensor driver for CM8206-A500SA-E Anatolij Gustschin
2012-11-06 9:44 ` Bastian Hecht
[not found] ` <CABYn4sxjZjiEt+=JC0vxXHFkCbHbuMRqTrAzgP_y-XKNsnSDHA@mail.gmail.com>
2012-11-06 13:33 ` Anatolij Gustschin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox