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 08:49:21 -0700 [thread overview]
Message-ID: <CAJ+vNU2fJ_eGMwQH7-HmO_==5p3Uuscv6S2fG_NY67J2o8OG+g@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5BgnbfFSmu7HEWtaT9Gexb-u13ZxzWEN-+Hw9eMfuC+LQ@mail.gmail.com>
On Sat, Oct 12, 2019 at 2:19 PM Fabio Estevam <festevam@gmail.com> wrote:
>
> Hi Steve,
>
> On Sat, Oct 12, 2019 at 5:24 PM Steve Longerbeam <slongerbeam@gmail.com> wrote:
>
> > Ah, now I remember. You are using the imx6dl sabreauto, it's IPU-CSI
>
> Yes, correct. I am using the imx6dl-sabreauto.
>
> > video muxes have five input pads for each of the four MIPI CSI-2 virtual
> > channels (pads 0 - 3) and one parallel input (pad 4). The output mux pad
> > is pad 5.
> >
> > But the doc should clarify which SabreAuto corresponds to the given
> > example pipeline config. Can you send a v2 of this patch that clarifies
> > the config corresponds to the imx6 quad SabreAuto. If you like you could
> > also include the analogous config for the imx6dl.
>
> Good idea. Will send a v2 that clarifies the example pipeline for each
> sabreauto variant.
>
> Thanks
Fabio,
I assume your seeing the same rolling video issue on capture unless
you discard the first few 'corrupt' frames? I'm still wondering how we
can address this properly upstream.
Tim
next prev parent reply other threads:[~2019-10-15 15:49 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 [this message]
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
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+vNU2fJ_eGMwQH7-HmO_==5p3Uuscv6S2fG_NY67J2o8OG+g@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).