From: khalasa@piap.pl (Krzysztof Hałasa)
To: <linux-media@vger.kernel.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Steve Longerbeam <slongerbeam@gmail.com>,
Tim Harvey <tharvey@gateworks.com>
Subject: i.MX6 IPU CSI analog video input on Ventana
Date: Thu, 10 May 2018 10:19:11 +0200 [thread overview]
Message-ID: <m37eobudmo.fsf@t19.piap.pl> (raw)
Hi,
I'm using analog PAL video in on GW53xx/54xx boards (through ADV7180
chip and 8-bit parallel CSI input, with (presumably) BT.656).
I'm trying to upgrade from e.g. Linux 4.2 + Steve's older MX6 camera
driver (which works fine) to v.4.16 with the recently merged driver.
media-ctl -r -l '"adv7180 2-0020":0->"ipu2_csi1_mux":1[1],
"ipu2_csi1_mux":2->"ipu2_csi1":0[1],
"ipu2_csi1":2->"ipu2_csi1 capture":0[1]'
media-ctl -V '"adv7180 2-0020":0[fmt:UYVY2X8 720x576 field:interlaced]'
media-ctl -V '"ipu2_csi1_mux":1[fmt:UYVY2X8 720x576 field:interlaced]'
media-ctl -V '"ipu2_csi1_mux":2[fmt:UYVY2X8 720x576 field:interlaced]'
It seems there are issues, though:
First, I can't find a way to change to PAL standard. *s_std() doesn't
propagate from "ipu2_csi1 capture" through "ipu2_csi1_mux" to adv7180.
For now I have just changed the default:
--- a/drivers/media/i2c/adv7180.c
+++ b/drivers/media/i2c/adv7180.c
@@ -1320,7 +1321,7 @@ static int adv7180_probe(struct i2c_client *client,
state->irq = client->irq;
mutex_init(&state->mutex);
- state->curr_norm = V4L2_STD_NTSC;
+ state->curr_norm = V4L2_STD_PAL;
if (state->chip_info->flags & ADV7180_FLAG_RESET_POWERED)
state->powered = true;
else
Second, the image format information I'm getting out of "ipu2_csi1
capture" device is:
open("/dev/video6")
ioctl(VIDIOC_S_FMT, {V4L2_BUF_TYPE_VIDEO_CAPTURE,
fmt.pix={704x576, pixelformat=NV12, V4L2_FIELD_INTERLACED} =>
fmt.pix={720x576, pixelformat=NV12, V4L2_FIELD_INTERLACED,
bytesperline=720, sizeimage=622080,
colorspace=V4L2_COLORSPACE_SMPTE170M}})
Now, the resulting image obtained via QBUF/DQBUF doesn't seem to be
a single interlaced frame (like it was with older drivers). Actually,
I'm getting the two fields, encoded with NV12 and concatenated
together (I think it's V4L2_FIELD_SEQ_TB or V4L2_FIELD_SEQ_BT).
What's wrong?
Is it possible to get a real V4L2_FIELD_INTERLACED frame, so it can be
passed straight to the CODA H.264 encoder?
--
Krzysztof Halasa
Industrial Research Institute for Automation and Measurements PIAP
Al. Jerozolimskie 202, 02-486 Warsaw, Poland
next reply other threads:[~2018-05-10 8:27 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 8:19 Krzysztof Hałasa [this message]
2018-05-10 16:32 ` i.MX6 IPU CSI analog video input on Ventana 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
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=m37eobudmo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox