From: Jagan Teki <jagan@amarulasolutions.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Philipp Zabel <pza@pengutronix.de>,
Steve Longerbeam <steve_longerbeam@mentor.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
Discussion of the development of and with GStreamer
<gstreamer-devel@lists.freedesktop.org>,
linux-media@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: i.MX6 MIPI-CSI2 OV5640 Camera testing on Mainline Linux
Date: Fri, 1 Jun 2018 17:11:16 +0530 [thread overview]
Message-ID: <CAMty3ZBCrrj=GJzGWR8tp5e2ZEAgADFT9OQ_THAALOW_Bay1LA@mail.gmail.com> (raw)
In-Reply-To: <20180601095322.hdxcpmj4tfonaq4g@valkosipuli.retiisi.org.uk>
On Fri, Jun 1, 2018 at 3:23 PM, Sakari Ailus <sakari.ailus@iki.fi> wrote:
> On Fri, Jun 01, 2018 at 10:49:56AM +0530, Jagan Teki wrote:
>> Hi Philipp,
>>
>> On Fri, Jun 1, 2018 at 12:36 AM, Philipp Zabel <pza@pengutronix.de> wrote:
>> > Hi Jagan,
>> >
>> > On Thu, May 31, 2018 at 08:39:20PM +0530, Jagan Teki wrote:
>> >> Hi All,
>> >>
>> >> I'm trying to verify MIPI-CSI2 OV5640 camera on i.MX6 platform with
>> >> Mainline Linux.
>> >>
>> >> I've followed these[1] instructions to configure MC links and pads
>> >> based on the probing details from dmesg and trying to capture
>> >> ipu1_ic_prpenc capture (/dev/video1) but it's not working.
>> >>
>> >> Can anyone help me to verify whether I configured all the details
>> >> properly if not please suggest.
>> >>
>> >> I'm pasting full log here, so-that anyone can comment in line and dt
>> >> changes are at [2]
>> >>
>> >> Log:
>> >> -----
>> > [...]
>> >> # media-ctl -l "'ov5640 2-003c':0 -> 'imx6-mipi-csi2':0[1]"
>> >> # media-ctl -l "'imx6-mipi-csi2':2 -> 'ipu1_csi1':0[1]"
>> >> # media-ctl -l "'ipu1_csi1':1 -> 'ipu1_ic_prp':0[1]"
>> >> # media-ctl -l "'ipu1_ic_prp':1 -> 'ipu1_ic_prpenc':0[1]"
>> >> # media-ctl -l "'ipu1_ic_prpenc':1 -> 'ipu1_ic_prpenc capture':0[1]"
>> >
>> > Here you configure a pipeline that ends at ipu1 prpenc capture ...
>> >
>> >> # med# media-ctl -p
>> > [...]
>> >> - entity 18: ipu1_ic_prpenc capture (1 pad, 1 link)
>> >> type Node subtype V4L flags 0
>> >> device node name /dev/video0
>> >
>> > ... which is /dev/video0 ...
>> >
>> > [...]
>> >> - entity 27: ipu1_ic_prpvf capture (1 pad, 1 link)
>> >> type Node subtype V4L flags 0
>> >> device node name /dev/video1
>> >
>> > ... not /dev/video1 ...
>>
>> True, thanks for pointing it.
>>
>> I actually tried even on video0 which I forgot to post the log [4].
>> Now I understand I'm trying for wrong device to capture look like
>> video0 which is ipu1 prepenc firing kernel oops. I'm trying to debug
>> this and let me know if have any suggestion to look into.
>>
>> [ 56.800074] imx6-mipi-csi2: LP-11 timeout, phy_state = 0x000002b0
>> [ 57.369660] ipu1_ic_prpenc: EOF timeout
>> [ 57.849692] ipu1_ic_prpenc: wait last EOF timeout
>> [ 57.855703] ipu1_ic_prpenc: pipeline start failed with -110
>
> I don't have the hardware but this looks like the host cannot detect the
> LP-11 state on the sensor (both wires high?). Some sensors cannot do this
> without starting streaming at the same time. I'd expect the same if there
> are problems in lane configuration etc.
You mean the lane configurations in hardware? but this sensor is
working with imx kernel. what do you mean by wires here? lanes.
Jagan.
--
Jagan Teki
Senior Linux Kernel Engineer | Amarula Solutions
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.
next prev parent reply other threads:[~2018-06-01 11:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 15:09 i.MX6 MIPI-CSI2 OV5640 Camera testing on Mainline Linux Jagan Teki
2018-05-31 16:10 ` Nicolas Dufresne
2018-05-31 16:25 ` Jagan Teki
2018-05-31 19:06 ` Philipp Zabel
2018-06-01 5:19 ` Jagan Teki
2018-06-01 9:53 ` Sakari Ailus
2018-06-01 11:41 ` Jagan Teki [this message]
2018-06-29 21:46 ` Fabio Estevam
2018-07-03 18:41 ` jacopo mondi
2018-07-04 0:18 ` Fabio Estevam
2018-07-04 5:18 ` Jagan Teki
2018-07-04 6:57 ` Jagan Teki
2018-07-04 14:26 ` Fabio Estevam
[not found] ` <588A2275-4D45-442D-8B38-7A17C27BED10@gmail.com>
2018-07-04 6:59 ` Jagan Teki
2018-07-04 7:11 ` chain256
2018-09-20 14:56 ` jacopo mondi
2018-10-16 19:46 ` Adam Ford
2018-10-17 0:13 ` Steve Longerbeam
2018-10-17 8:01 ` jacopo mondi
2018-10-19 13:45 ` Adam Ford
2018-10-19 19:42 ` Adam Ford
2018-10-22 11:33 ` jacopo mondi
2018-10-22 12:25 ` Adam Ford
2018-10-22 12:40 ` Fabio Estevam
2018-10-23 15:19 ` Adam Ford
2018-10-23 16:36 ` Steve Longerbeam
2018-10-23 17:34 ` Adam Ford
2018-10-23 17:39 ` Steve Longerbeam
2018-10-23 17:54 ` Adam Ford
2018-10-23 18:11 ` Steve Longerbeam
2018-10-23 23:03 ` jacopo mondi
2018-10-24 13:53 ` Adam Ford
2018-10-24 14:08 ` jacopo mondi
2018-10-24 14:17 ` Adam Ford
2018-10-28 18:57 ` Adam Ford
2018-10-29 13:49 ` Fabio Estevam
2018-11-05 22:32 ` Adam Ford
2018-11-06 8:27 ` jacopo mondi
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='CAMty3ZBCrrj=GJzGWR8tp5e2ZEAgADFT9OQ_THAALOW_Bay1LA@mail.gmail.com' \
--to=jagan@amarulasolutions.com \
--cc=fabio.estevam@nxp.com \
--cc=gstreamer-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=pza@pengutronix.de \
--cc=sakari.ailus@iki.fi \
--cc=steve_longerbeam@mentor.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;
as well as URLs for NNTP newsgroup(s).