From: khalasa@piap.pl (Krzysztof Hałasa)
To: Steve Longerbeam <slongerbeam@gmail.com>
Cc: linux-media@vger.kernel.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Tim Harvey <tharvey@gateworks.com>
Subject: Re: i.MX6 IPU CSI analog video input on Ventana
Date: Mon, 21 May 2018 10:09:27 +0200 [thread overview]
Message-ID: <m3603hsa4o.fsf@t19.piap.pl> (raw)
In-Reply-To: <m3fu2oswjh.fsf@t19.piap.pl> ("Krzysztof \=\?utf-8\?Q\?Ha\=C5\=82as\?\= \=\?utf-8\?Q\?a\=22's\?\= message of "Fri, 18 May 2018 19:28:34 +0200")
Tested with NTSC camera, it's the same as with PAL.
The only case when IPU2_CSI1_SENS_CONF register is set to interlaced
mode (PRCTL=3, CCIR interlaced mode (BT.656)) is when all parts of the
pipeline are set to interlaced:
"adv7180 2-0020":0 [fmt:UYVY2X8/720x576 field:interlaced]
"ipu2_csi1_mux":1 [fmt:UYVY2X8/720x576 field:interlaced]
"ipu2_csi1_mux":2 [fmt:UYVY2X8/720x576 field:interlaced]
"ipu2_csi1":0 [fmt:UYVY2X8/720x576 field:interlaced]
"ipu2_csi1":2 [fmt:AYUV32/720x576 field:interlaced]
The image is stable and in sync, the "only" problem is that I get two
concatenated field images (in one V4L2 frame) instead of a normal
interlaced frame (all lines in order - 0, 1, 2, 3, 4 etc).
IOW I get V4L2_FIELD_ALTERNATE, V4L2_FIELD_SEQ_TB or V4L2_FIELD_SEQ_BT
(the data format, I don't mean the pixel format.field) while I need to
get V4L2_FIELD_INTERLACED, V4L2_FIELD_INTERLACED_TB or _BT.
If I set "ipu2_csi1":2 to field:none, the IPU2_CSI1_SENS_CONF is set to
progressive mode (PRCTL=2). It's the last element of the pipeline I can
configure, it's connected straight to "ipu2_csi1 capture" aka
/dev/videoX. I think CSI can't work with interlaced camera (and ADV7180)
when set to progressive, can it?
I wonder... perhaps to get an interlaced frame I need to route the data
through VDIC (ipu2_vdic, the deinterlacer)?
--
Krzysztof Halasa
Industrial Research Institute for Automation and Measurements PIAP
Al. Jerozolimskie 202, 02-486 Warsaw, Poland
next prev parent reply other threads:[~2018-05-21 8:09 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 8:19 i.MX6 IPU CSI analog video input on Ventana Krzysztof Hałasa
2018-05-10 16:32 ` Steve Longerbeam
2018-05-11 5:37 ` Krzysztof Hałasa
2018-05-11 17:35 ` Steve Longerbeam
2018-05-18 17:28 ` Krzysztof Hałasa
2018-05-18 17:56 ` Tim Harvey
2018-05-21 5:51 ` Krzysztof Hałasa
2018-05-21 8:09 ` Krzysztof Hałasa [this message]
2018-05-21 15:55 ` Tim Harvey
2018-05-21 21:25 ` Steve Longerbeam
2018-05-22 10:48 ` Krzysztof Hałasa
2018-05-24 15:56 ` Krzysztof Hałasa
2018-05-24 18:12 ` Steve Longerbeam
2018-05-24 20:48 ` Steve Longerbeam
2018-05-24 21:33 ` Steve Longerbeam
2018-05-25 6:34 ` Philipp Zabel
2018-05-25 5:21 ` Krzysztof Hałasa
2018-05-25 6:32 ` Philipp Zabel
2018-05-25 7:18 ` Krzysztof Hałasa
2018-05-25 23:39 ` Steve Longerbeam
2018-05-29 7:26 ` Krzysztof Hałasa
2018-05-29 14:00 ` Steve Longerbeam
2018-05-30 8:53 ` Krzysztof Hałasa
2018-05-30 17:57 ` Steve Longerbeam
2018-05-30 18:46 ` Krzysztof Hałasa
2018-05-30 20:56 ` Steve Longerbeam
2018-05-31 6:29 ` Philipp Zabel
2018-06-01 5:23 ` Krzysztof Hałasa
2018-06-02 17:33 ` Steve Longerbeam
2018-06-04 8:38 ` Philipp Zabel
2018-06-01 10:02 ` Krzysztof Hałasa
2018-06-01 13:13 ` Philipp Zabel
2018-06-02 17:45 ` Steve Longerbeam
2018-06-04 7:33 ` Krzysztof Hałasa
2018-06-04 8:47 ` Philipp Zabel
2018-06-04 8:58 ` Krzysztof Hałasa
2018-10-17 20:38 ` Tim Harvey
[not found] ` <57dfdc0b-5f04-e10a-2ffd-c7ba561fe7ce@gmail.com>
2018-10-17 23:05 ` Tim Harvey
2018-10-17 23:37 ` Steve Longerbeam
2018-10-18 17:56 ` Tim Harvey
2018-10-19 20:06 ` Steve Longerbeam
2018-10-19 9:45 ` Philipp Zabel
2018-06-04 7:06 ` Krzysztof Hałasa
2018-05-25 23:21 ` Steve Longerbeam
2018-06-01 13:52 ` Philipp Zabel
2018-05-25 7:07 ` Krzysztof Hałasa
2018-05-22 9:41 ` Franz Melchior
2018-05-11 6:11 ` Franz Melchior
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=m3603hsa4o.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=slongerbeam@gmail.com \
--cc=tharvey@gateworks.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.