linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jacopo mondi <jacopo@jmondi.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
	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 <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: Tue, 3 Jul 2018 20:41:17 +0200	[thread overview]
Message-ID: <20180703184117.GC5611@w540> (raw)
In-Reply-To: <CAOMZO5AOpOSAx=L4tOU1Na6hm8Tex3PHNxCYDB81C0+NPHzTZQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2507 bytes --]

Hi Fabio,
  thanks for pointing Jagan to my series, but..

On Fri, Jun 29, 2018 at 06:46:39PM -0300, Fabio Estevam wrote:
> Hi Jagan,
>
> On Fri, Jun 1, 2018 at 2:19 AM, Jagan Teki <jagan@amarulasolutions.com> wrote:
>
> > 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
>
> Could you please test this series from Jacopo?
> https://www.mail-archive.com/linux-media@vger.kernel.org/msg133191.html
>
> It seems that it would fix this problem.

... unfortunately it does not :(

I've been able to test on the same platform where Jagan has reported
this issue, and the CSI-2 bus still fails to startup properly...

I do not have CSI-2 receiver driver documentation for the other platform
I am testing on and where my patches improved stability, but the i.MX6 error
reported by Jagan could be useful to help debugging what's wrong with the
serial bus initialization on that platform.

The error comes from register MIPI_CSI_PHY_STATE of the i.MX6 MIPI_CSI-2
interface and reads as:

0x2b0 : BIT(9) -> clock in ULPS state
	BIT(7) -> lane3 in stop state
	BIT(5) -> lane1 in stop state
	BIT(4) -> lane0 in stop state

The i.MX6 driver wants instead that register to be:

0x430 : BIT(10) -> clock in stop state
	BIT(5) -> lane1 in stop state
	BIT(4) -> lane0 in stop state

So indeed it represents a useful debugging tool to have an idea of what's going
on there.

I'm a bit puzzled by the BIT(7) as lane3 is not connected, as ov5640 is a 2
lanes sensor, and I would have a question for Jagan here: has the sensor been
validated with BSP/vendor kernels on that platform? There's a flat cable
connecting the camera module to the main board, and for high speed
differential signals that's maybe not the best possible solution...

Also, anyone interested in my mumbling on the ov5640 MIPI bus
initialization, I've collected some thoughts here:
https://paste.debian.net/1031942/

Any comment is of course welcome, and if I have a confirmation that
the Engicam platform works with that flat cable, I'll keep working on
it..

Thanks
   j


> Thanks

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2018-07-03 18: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
2018-06-29 21:46     ` Fabio Estevam
2018-07-03 18:41       ` jacopo mondi [this message]
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=20180703184117.GC5611@w540 \
    --to=jacopo@jmondi.org \
    --cc=fabio.estevam@nxp.com \
    --cc=festevam@gmail.com \
    --cc=gstreamer-devel@lists.freedesktop.org \
    --cc=jagan@amarulasolutions.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=pza@pengutronix.de \
    --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).