From: Steve Longerbeam <steve_longerbeam@mentor.com>
To: "Sergei Shtylyov" <sergei.shtylyov@cogentembedded.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
slongerbeam@gmail.com
Cc: <lars@metafoo.de>, <mchehab@kernel.org>, <hans.verkuil@cisco.com>
Subject: Re: [PATCH 6/6] media: adv7180: fix field type
Date: Fri, 29 Jul 2016 12:32:30 -0700 [thread overview]
Message-ID: <df2a330f-30a3-e296-006e-204fa1771bb5@mentor.com> (raw)
In-Reply-To: <cc084571-3063-a883-b731-0ffe01c4fefa@cogentembedded.com>
On 07/29/2016 12:10 PM, Sergei Shtylyov wrote:
> On 07/29/2016 08:40 PM, Niklas Söderlund wrote:
>
>> From: Steve Longerbeam <slongerbeam@gmail.com>
>>
>> The ADV7180 and ADV7182 transmit whole fields, bottom field followed
>> by top (or vice-versa, depending on detected video standard). So
>> for chips that do not have support for explicitly setting the field
>> mode, set the field mode to V4L2_FIELD_ALTERNATE.
>>
>> Signed-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>
>> [Niklas: changed filed type from V4L2_FIELD_SEQ_{TB,BT} to
>> V4L2_FIELD_ALTERNATE]
>> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>
> Tested-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> IIUC, it's a 4th version of this patch; you should have kept the
> original change log (below --- tearline) and indicated that in the
> subject.
>
> MBR, Sergei
This version is fine with me. The i.mx6 h/w motion-compensation
deinterlacer (VDIC)
needs to know the field order, and it can't get that info from
V4L2_FIELD_ALTERNATE,
but it can still determine the order via querystd().
But I agree the change log should be preserved, and the
V4L2_FIELD_ALTERNATE change
added to the change log.
Acked-by: Steve Longerbeam <slongerbeam@gmail.com>
Steve
next prev parent reply other threads:[~2016-07-29 19:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 17:40 [PATCH 0/6] Fix adv7180 and rcar-vin field handling Niklas Söderlund
2016-07-29 17:40 ` [PATCH 1/6] media: rcar-vin: allow field to be changed Niklas Söderlund
2016-07-29 21:04 ` Sergei Shtylyov
2016-08-01 16:52 ` Niklas Söderlund
2016-08-01 17:55 ` Hans Verkuil
2016-07-29 17:40 ` [PATCH 2/6] media: rcar-vin: fix bug in scaling Niklas Söderlund
2016-07-29 17:40 ` [PATCH 3/6] media: rcar-vin: fix height for TOP and BOTTOM fields Niklas Söderlund
2016-07-29 17:40 ` [PATCH 4/6] media: rcar-vin: add support for V4L2_FIELD_ALTERNATE Niklas Söderlund
2016-07-30 21:55 ` Sergei Shtylyov
2016-08-01 16:53 ` Niklas Söderlund
2016-08-02 9:41 ` Hans Verkuil
2016-08-02 10:32 ` Niklas Söderlund
2016-08-02 10:39 ` Hans Verkuil
2016-08-02 11:02 ` Niklas Söderlund
2016-08-02 11:21 ` Hans Verkuil
2016-07-29 17:40 ` [PATCH 5/6] media: adv7180: fill in mbus format in set_fmt Niklas Söderlund
2016-07-29 17:40 ` [PATCH 6/6] media: adv7180: fix field type Niklas Söderlund
2016-07-29 19:10 ` Sergei Shtylyov
2016-07-29 19:32 ` Steve Longerbeam [this message]
2016-07-29 20:16 ` Niklas Söderlund
2016-08-02 9:43 ` [PATCH 0/6] Fix adv7180 and rcar-vin field handling Hans Verkuil
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=df2a330f-30a3-e296-006e-204fa1771bb5@mentor.com \
--to=steve_longerbeam@mentor.com \
--cc=hans.verkuil@cisco.com \
--cc=lars@metafoo.de \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=sergei.shtylyov@cogentembedded.com \
--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