From: Philipp Zabel <p.zabel@pengutronix.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Steve Longerbeam <slongerbeam@gmail.com>,
Ezequiel Garcia <ezequiel@collabora.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
kernel@collabora.com, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-media <linux-media@vger.kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>
Subject: Re: [PATCH] media: imx: mipi csi-2: Don't fail if initial state times-out
Date: Thu, 27 Jun 2019 14:56:12 +0200 [thread overview]
Message-ID: <1561640172.4216.16.camel@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5D1Lq7MuK55hydP3JNGki71iNeubzfUgAvVhEDuzDcZFA@mail.gmail.com>
Hi Fabio,
On Thu, 2019-06-27 at 09:38 -0300, Fabio Estevam wrote:
> Hi Philipp,
>
> On Thu, Jun 27, 2019 at 5:43 AM Philipp Zabel <p.zabel@pengutronix.de> wrote:
>
> > Are there any visual artifacts in the first frame(s) in this case?
>
> I do not observe visual artifacts when running gst-launch-1.0 v4l2src ! kmssink
>
> > > So in my opinion the next version of this patch should make LP-11
> > > timeout a warning only, but keep the error return on clock lane timeouts.
> >
> > I agree.
>
> Here is a reworked version of Ezequiel's patch as per the suggestions:
> http://code.bulix.org/g5qap5-780475
>
> Does this one look good?
Limiting the change to wait_stopstate is fine, the actual message
makes assumptions that could be misleading. How about:
"Timeout waiting for LP-11 state on all active lanes.
This is most likely caused by a bug in the sensor driver.
Capture might fail or contain visual artifacts."
I'd like to keep the phy_state register output though, if only as
dev_dbg(). It contains useful output for debugging, for example if only
some of the lanes are in stop state, which could indicate an issue with
connections or lane configuration.
regards
Philipp
next prev parent reply other threads:[~2019-06-27 12:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 20:39 [PATCH] media: imx: mipi csi-2: Don't fail if initial state times-out Ezequiel Garcia
2019-06-26 0:45 ` Steve Longerbeam
2019-06-26 7:45 ` Philipp Zabel
2019-06-26 19:53 ` Fabio Estevam
2019-06-26 21:19 ` Steve Longerbeam
2019-06-26 23:22 ` Fabio Estevam
2019-06-26 23:29 ` Steve Longerbeam
2019-06-27 8:43 ` Philipp Zabel
2019-06-27 12:38 ` Fabio Estevam
2019-06-27 12:56 ` Philipp Zabel [this message]
2019-06-27 18:45 ` Ezequiel Garcia
2019-06-27 22:16 ` Fabio Estevam
2019-06-27 22:12 ` Steve Longerbeam
2019-07-01 6:48 ` Philipp Zabel
2019-06-27 12:42 ` Ezequiel Garcia
2019-06-26 8:00 ` Laurent Pinchart
2019-06-26 18:05 ` Ezequiel Garcia
2019-06-26 18:16 ` Steve Longerbeam
2019-06-27 7:39 ` 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=1561640172.4216.16.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=ezequiel@collabora.com \
--cc=festevam@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=kernel@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=slongerbeam@gmail.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