From: Dominic Curran <dcurran@ti.com>
To: linux-omap <linux-omap@vger.kernel.org>
Subject: [OMAPZOOM][PATCH 0/3] ISP: Component order
Date: Thu, 26 Feb 2009 16:39:38 -0600 [thread overview]
Message-ID: <200902261639.38890.dcurran@ti.com> (raw)
From: Dominic Curran <dcurran@ti.com>
Subject:[OMAPZOOM][PATCH 0/3] ISP: Component order
The RAW10 component order for all three sensors I test with (MT9P012, OV3640 &
IMX046) is different. This patch set uses different horz/vert offsets in CCDC
so that the output RAW component order is the same for all sensors.
Currently sph and slv in the board file (for MT & OV) are used to fix component
order in Previewer. However this approach doesn't work for the Sony IMX046
sensor.
This patch causes the component order output of CCDC to be the same for all
sensors. Since the order is the same going into Previewer this means that there
is not need for sph and slv to change per sensor.
woffset hoffset RAW10 test YUV test
MT9P012 GR..BG 1 0 OK OK
IMX046 RG..GB 0 0 OK OK
OV3640 BG..GR 1 1 OK OK
Patch:
1/3 Removes original bug introduced with IMX046 patch.
2/3 Changes in CCDC to all easy setup of component order in board file.
3/3 Remove no longer needed prev_sph & prev_slv from boad file.
Testing:
The following tests have been run using this patch set [x = working]:
(Test apps below are internal TI tools which test basic V4L2 functions)
IMX046 streaming 3 YUYV QVGA 1 500 x
streaming 3 YUYV VGA 1 500 x
streaming 3 YUYV 208 154 1 500 x
streaming 3 YUYV 854 480 1 500 x
fps 3 YUYV 640 480 200 30fps
fps 3 YUYV 3280 2464 100 7.5fps
burst_mode 3 YUYV 816 616 1 file.yuv x
burst_mode 3 YUYV 3280 2464 1 file.yuv x
burst_mode 3 RAW10 3280 616 1 file.raw x (h)
MT9P012 ./streaming_frame 1 15 YUYV QVGA 1 200 x
./streaming_frame 1 30 YUYV QVGA 1 200 x
./streaming_frame 1 15 YUYV VGA 1 200 x
./streaming_frame 1 30 YUYV VGA 1 200 x
burst_mode 1 YUYV 5MP 1 file.yuv x
burst_mode 1 RAW10 5MP 1 file.raw x (h)
streaming_zoom 1 YUYV VGA x
OV3640 streaming 2 YUYV 256 192 1 300 x
streaming 2 YUYV QVGA 1 300 x
streaming 2 YUYV VGA 1 300 x
burst_mode 2 YUYV XGA 1 file.yuv x
burst_mode 2 YUYV QXGA 1 file.yuv x
burst_mode 2 RAW10 QXGA 1 file.raw x (h)
fps 2 YUYV VGA 200 30fps
fps 2 YUYV QXGA 100 15 15fps
reply other threads:[~2009-02-26 22:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200902261639.38890.dcurran@ti.com \
--to=dcurran@ti.com \
--cc=linux-omap@vger.kernel.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