From: Steve Longerbeam <slongerbeam@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
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: Wed, 26 Jun 2019 16:29:54 -0700 [thread overview]
Message-ID: <ba0f4a0f-cb61-6c5b-1db9-21536ae38c6f@gmail.com> (raw)
In-Reply-To: <CAOMZO5AGZcsrzogzxRo9UNauYgWZLdiVE8vJ3-FxU2X4K8Jwxg@mail.gmail.com>
Hi Fabio,
On 6/26/19 4:22 PM, Fabio Estevam wrote:
> Hi Steve,
>
> On Wed, Jun 26, 2019 at 6:19 PM Steve Longerbeam <slongerbeam@gmail.com> wrote:
>
>> Did you only get the LP-11 timeout warning message with this patch on
>> the OV5645, or both the LP-11 timeout and clock lane timeout warnings?
> With this patch applied I get only the LP-11 timeout warnings, not
> clock lane timeouts.
Ok thanks for the confirmation that the imx6 CSI-2 receiver is able to
successfully move to stream on without seeing the LP-11 state in this
case. 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.
Steve
next prev parent reply other threads:[~2019-06-26 23:30 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 [this message]
2019-06-27 8:43 ` Philipp Zabel
2019-06-27 12:38 ` Fabio Estevam
2019-06-27 12:56 ` Philipp Zabel
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=ba0f4a0f-cb61-6c5b-1db9-21536ae38c6f@gmail.com \
--to=slongerbeam@gmail.com \
--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=p.zabel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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