All of lore.kernel.org
 help / color / mirror / Atom feed
From: khalasa@piap.pl (Krzysztof Hałasa)
To: Steve Longerbeam <slongerbeam@gmail.com>
Cc: Javier Martinez Canillas <javierm@redhat.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	linux-media@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] gpu: ipu-v3: Allow negative offsets for interlaced scanning
Date: Fri, 15 Jun 2018 10:33:54 +0200	[thread overview]
Message-ID: <m336xoxxcd.fsf@t19.piap.pl> (raw)
In-Reply-To: <798b8ad7-2fce-8408-b1c4-c2954f524d23@gmail.com> (Steve Longerbeam's message of "Thu, 14 Jun 2018 09:26:16 -0700")

Steve Longerbeam <slongerbeam@gmail.com> writes:

> Right, the selection of interweave is moved to the capture devices,
> so the following will enable interweave:
>
> v4l2-ctl -dN --set-fmt-video=field=interlaced_tb

and

> So the patch to adv7180 needs to be modified to report # field lines.
>
> Try the following:
>
> --- a/drivers/media/i2c/adv7180.c
> +++ b/drivers/media/i2c/adv7180.c

With this patch, fix-csi-interlaced.3 seems to work for me.
"ipu2_csi1":2 reports [fmt:AYUV32/720x576 field:seq-tb], but the
/dev/videoX shows (when requested) 720 x 576 NV12 interlaced, top field
first, and I'm getting valid output.

Thanks for your work.
-- 
Krzysztof Halasa

Industrial Research Institute for Automation and Measurements PIAP
Al. Jerozolimskie 202, 02-486 Warsaw, Poland

  reply	other threads:[~2018-06-15  8:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 13:13 [PATCH] gpu: ipu-v3: Allow negative offsets for interlaced scanning Philipp Zabel
2018-06-11  0:08 ` Steve Longerbeam
2018-06-11  9:19   ` Philipp Zabel
2018-06-11 21:06     ` Steve Longerbeam
2018-06-12 16:43       ` Philipp Zabel
2018-06-12 17:27       ` Javier Martinez Canillas
2018-06-12 17:31         ` Steve Longerbeam
2018-06-14  9:39           ` Krzysztof Hałasa
2018-06-14 16:26             ` Steve Longerbeam
2018-06-15  8:33               ` Krzysztof Hałasa [this message]
2018-06-20  1:30                 ` Steve Longerbeam
2018-06-20  8:54                   ` Philipp Zabel
2018-06-21  4:30                     ` Steve Longerbeam

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=m336xoxxcd.fsf@t19.piap.pl \
    --to=khalasa@piap.pl \
    --cc=javierm@redhat.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-media@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.