From: Florian Boor <florian.boor@kernelconcepts.de>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: MT9M131 on I.MX6DL CSI color issue
Date: Fri, 12 Jan 2018 01:16:03 +0100 [thread overview]
Message-ID: <b704a2fb-efa1-a2f8-7af0-43d869c688eb@kernelconcepts.de> (raw)
Hello all,
I have a Phytec VM-009 camera based on MT9M131 connected to CSI0 of a I.MX6DL
based board running mainline 4.13.0 + custom devicetree. Its using the parallel
interface, 8 bit bus width on pins 12 to 19.
Basically it works pretty well apart from the really strange colors. I guess its
some YUV vs. RGB issue or similar. Here [1] is an example generated with the
following command.
gst-launch v4l2src device=/dev/video4 num-buffers=1 ! jpegenc ! filesink
location=capture1.jpeg
Apart from the colors everything is fine.
I'm pretty sure I have not seen such an effect before - what might be wrong here?
The current setup looks like this:
IF=UYVY2X8
GEOM="1280x1024"
media-ctl -l "'mt9m111 2-0048':0 -> 'ipu1_csi0_mux':4[1]"
media-ctl -l "'ipu1_csi0_mux':5 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':2 -> 'ipu1_csi0 capture':0[1]"
media-ctl -d /dev/media0 -v -V "'ipu1_csi0':2 [fmt:${IF}/${GEOM} field:none]"
media-ctl -d /dev/media0 -v -V "'ipu1_csi0 capture':0 [fmt:${IF}/${GEOM}
field:none]"
media-ctl -d /dev/media0 -v -V "'ipu1_csi0_mux':4 [fmt:${IF}/${GEOM} field: none]"
media-ctl -d /dev/media0 -v -V "'ipu1_csi0_mux':5 [fmt:${IF}/${GEOM} field: none]"
media-ctl -d /dev/media0 -v -V "'mt9m111 2-0048':0 [fmt:${IF}/${GEOM} field: none]"
Greetings
Florian
[1] http://www.kernelconcepts.de/~florian/capture1.jpeg
--
The dream of yesterday Florian Boor
is the hope of today Tel: +49 271-771091-15
and the reality of tomorrow. Fax: +49 271-338857-29
[Robert Hutchings Goddard, 1904] florian.boor@kernelconcepts.de
http://www.kernelconcepts.de/en
kernel concepts GmbH
Hauptstraße 16
D-57074 Siegen
Geschäftsführer: Ole Reinhardt
HR Siegen, HR B 9613
next reply other threads:[~2018-01-12 0:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 0:16 Florian Boor [this message]
2018-01-12 9:58 ` MT9M131 on I.MX6DL CSI color issue Anatolij Gustschin
2018-01-12 10:06 ` Anatolij Gustschin
2018-01-15 10:40 ` Florian Boor
2018-01-17 10:31 ` Daniel Glöckner
2018-01-17 12:58 ` Florian Boor
2018-01-18 4:03 ` Daniel Glöckner
2018-01-18 16:31 ` Florian Boor
2018-01-20 15:02 ` Daniel Glöckner
2018-01-22 14:52 ` Florian Boor
2018-01-30 17:13 ` Florian Boor
2018-01-12 14:59 ` Nicolas Dufresne
2018-01-15 12:49 ` Philipp Zabel
2018-01-15 14:41 ` Florian Boor
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=b704a2fb-efa1-a2f8-7af0-43d869c688eb@kernelconcepts.de \
--to=florian.boor@kernelconcepts.de \
--cc=linux-media@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