From: khalasa@piap.pl (Krzysztof Hałasa)
To: Tim Harvey <tharvey@gateworks.com>
Cc: Steve Longerbeam <slongerbeam@gmail.com>,
linux-media <linux-media@vger.kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: i.MX6 IPU CSI analog video input on Ventana
Date: Mon, 21 May 2018 07:51:56 +0200 [thread overview]
Message-ID: <m3bmd9sghv.fsf@t19.piap.pl> (raw)
In-Reply-To: <CAJ+vNU3WxSPe9jHRnajU0CNurMS4vMVakh4W0vb197caQhKP7g@mail.gmail.com> (Tim Harvey's message of "Fri, 18 May 2018 10:56:33 -0700")
Tim,
Tim Harvey <tharvey@gateworks.com> writes:
> What version of kernel are you using and what specific board model do
> you have (full board model and/or serial number so I know if you've
> got an IMX6DL or an IMX6Q) and have you modified the device-tree? I
> tested the adv7180 a couple of months ago but I don't know if I hit
> your specific combination. I was using NTSC but if your not getting
> VSYNC then yes I would like to make sure the pinmux is correct for
> your situation.
At the moment I'm using 4.16.0 and this particular board IDs itself as
GW5304-D2, the CPU is i.MX6Q. I mostly use GW5300s and GW5400s (and
others in smaller numbers) and they work fine with Steve's older driver
(the one with a special ADV7180 module).
I'm using the official device tree (v4.16 in this case) with just the
LDB (LVDS display) portion removed.
I guess I can test it with a NTSC camera.
--
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 5:51 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 [this message]
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=m3bmd9sghv.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