From: Tim Harvey <tharvey@gateworks.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Steve Longerbeam <slongerbeam@gmail.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] media: imx.rst: Update the imx6-sabreauto ADV7180 instructions
Date: Tue, 15 Oct 2019 09:33:25 -0700 [thread overview]
Message-ID: <CAJ+vNU1+oS1wFav4W2g0f6XGCP3oqEwzxyvrN3fkggNSBau0Tg@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5Dcv9fz=A8nTsvVsvu7+LNag2Sj03tJyFQKgpt_1B6Dwg@mail.gmail.com>
On Tue, Oct 15, 2019 at 9:16 AM Fabio Estevam <festevam@gmail.com> wrote:
>
> Hi Tim,
>
> On Tue, Oct 15, 2019 at 1:07 PM Tim Harvey <tharvey@gateworks.com> wrote:
> >
> > Right, I understand there is something else going on with the i.MX53
> > but what about the i.MX6 testing related to these patches?
>
> I tested it on a imx6 sabreauto board with 5.3.x kernel plus Steve's
> patch that discard the 10 initial corrupted frames and I do not get
> rolling video.
>
> I do get rolling video if I remove/insert the cable though.
Right, because this re-creates the initial issue. Upon any signal lock
you would need to throw away the first few frames. I wish I knew the
proper way to deal with this.
Tim
>
> > Regarding the i.MX53 as you have a kernel that does work you could
> > start looking for i2c register differences and csi config differences
> > between the two kernels. I discovered an issue with the adv7280 by
> > comparing i2c register dumps.
>
> Yes, I am in the process of comparing the two kernels.
>
> Thanks
next prev parent reply other threads:[~2019-10-15 16:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 15:44 [PATCH] media: imx.rst: Update the imx6-sabreauto ADV7180 instructions Fabio Estevam
2019-10-12 20:14 ` Steve Longerbeam
2019-10-12 20:24 ` Steve Longerbeam
2019-10-12 21:19 ` Fabio Estevam
2019-10-15 15:49 ` Tim Harvey
2019-10-15 15:53 ` Fabio Estevam
2019-10-15 16:07 ` Tim Harvey
2019-10-15 16:16 ` Fabio Estevam
2019-10-15 16:33 ` Tim Harvey [this message]
2019-10-15 16:42 ` Fabio Estevam
2019-10-15 18:19 ` Steve Longerbeam
2019-10-15 19:11 ` Fabio Estevam
2019-10-16 1:17 ` Steve Longerbeam
2019-10-16 1:32 ` Fabio Estevam
2019-10-16 13:04 ` Fabio Estevam
2019-10-16 17:31 ` Steve Longerbeam
2019-10-16 18:54 ` Fabio Estevam
2019-10-16 19:11 ` Steve Longerbeam
2019-10-16 19:51 ` Fabio Estevam
2020-06-25 10:53 ` Hans Verkuil
2020-06-25 11:38 ` Fabio Estevam
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=CAJ+vNU1+oS1wFav4W2g0f6XGCP3oqEwzxyvrN3fkggNSBau0Tg@mail.gmail.com \
--to=tharvey@gateworks.com \
--cc=festevam@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).