From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: mchehab@kernel.org, linux-media@vger.kernel.org, g.liakhovetski@gmx.de
Cc: linux-renesas-soc@vger.kernel.org, niklas.soderlund@ragnatech.se
Subject: [PATCH] rcar_vin: add support for V4L2_FIELD_ALTERNATE
Date: Sun, 31 Jul 2016 16:07:45 +0300 [thread overview]
Message-ID: <4854742.fOvMrCAxeI@wasted.cogentembedded.com> (raw)
The hardware can capture both odd and even fields in the separate buffers,
so it's possible to support this field mode. However, if the subdevice
presents data in this mode, we prefer to use the hardware deinterlacing...
Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
---
This patch is against the 'media_tree.git' repo's 'master' branch.
This patch needs to be merged before the following ADV7180 driver patch is
merged: http://www.mail-archive.com/linux-media@vger.kernel.org/msg100410.html
drivers/media/platform/soc_camera/rcar_vin.c | 2 ++
1 file changed, 2 insertions(+)
Index: media_tree/drivers/media/platform/soc_camera/rcar_vin.c
===================================================================
--- media_tree.orig/drivers/media/platform/soc_camera/rcar_vin.c
+++ media_tree/drivers/media/platform/soc_camera/rcar_vin.c
@@ -585,6 +585,7 @@ static int rcar_vin_setup(struct rcar_vi
vnmc = VNMC_IM_FULL | VNMC_FOC;
break;
case V4L2_FIELD_NONE:
+ case V4L2_FIELD_ALTERNATE:
if (is_continuous_transfer(priv)) {
vnmc = VNMC_IM_ODD_EVEN;
progressive = true;
@@ -1595,6 +1596,7 @@ static int rcar_vin_set_fmt(struct soc_c
case V4L2_FIELD_INTERLACED_BT:
field = pix->field;
break;
+ case V4L2_FIELD_ALTERNATE:
case V4L2_FIELD_INTERLACED:
/* Query for standard if not explicitly mentioned _TB/_BT */
ret = v4l2_subdev_call(sd, video, querystd, &std);
reply other threads:[~2016-07-31 13:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4854742.fOvMrCAxeI@wasted.cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund@ragnatech.se \
/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.