media: Add new camera interface driver for i.MX6

This is a V4L2 camera interface driver for i.MX6. See
Documentation/video4linux/mx6_camera.txt.

Signed-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>
Signed-off-by: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com>
Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
Signed-off-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
media: imx6: Add support for MIPI CSI-2 OV5640

This driver is based on ov5640_mipi.c from Freescale imx_3.10.17_1.0.0_beta
branch, modified heavily for code cleanup and converted from int-device
to subdev.

Signed-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>
media: imx6: Add support for Parallel OV5642

This driver is based on ov5642.c from Freescale imx_3.10.17_1.0.0_beta
branch, modified heavily for code cleanup and converted from int-device
to subdev.

Signed-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>
media: imx6: Add support for ADV7180 Video Decoder

This driver is based on adv7180.c from Freescale imx_3.10.17_1.0.0_beta
branch, modified heavily for code cleanup and converted from int-device
to subdev.

Signed-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>
media: imx6 camera: Add deinterlace motion control

Add a custom control to set a motion compensation setting for
deinterlacing using the VDIC.

Use of the VDIC is not compatible with preview because both
require the IC viewfinder task.

Signed-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>
media: imx6 camera: Add VDIC deinterlacing subdev

This subdev implements two different video pipelines:

CSI -> VDIC -> IC-VF -> CH21 -> MEM

In this pipeline, the CSI sends a single interlaced field F(n-1)
directly to the VDIC (and optionally the following field F(n)
can be sent to memory via IDMAC channel 13). This pipeline only works
in VDIC's high motion mode, which only requires a single field for
processing. The other motion modes (low and medium) require three fields,
so this pipeline does not work in those modes. Also, it is not clear how
this pipeline can deal with the various field orders (sequential BT/TB,
interlaced BT/TB) and there are reported image quality issues output
from the VDIC in this pipeline.

CSI -> CH[0-3] -> MEM -> CH8,9,10 -> VDIC -> IC-VF -> CH21 -> MEM

In this pipeline, the CSI sends raw and full frames to memory buffers
via the IDMAC SMFC channels 0-3. Fields from these frames are then
transferred to the VDIC via IDMAC channels 8,9,10. The VDIC requires
three fields: previous field F(n-1), current field F(n), and next
field F(n+1), so we need three raw frames in memory: two completed frames
to send F(n-1), F(n), F(n+1) to the VDIC, and a third frame for active
CSI capture while the completed fields are sent through the VDIC->IC for
processing.

While the "direct" CSI->VDIC pipeline requires less memory bus bandwidth
(just 1 channel vs. 5 channels for indirect pipeline), it can't be used
for all motion modes, it only processes a single field (so half the
original image resolution is lost), and it has the image quality issues
mentioned above. With the indirect pipeline we have full control over
field order. So by default the direct pipeline is disabled via a module
parameter, if enabled it will be used by high motion mode.

Signed-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>
ARM: imx_v6_v7_defconfig: Enable staging video4linux drivers

Enable imx6 v4l2 staging drivers as modules. For video capture on
the SabreAuto, the ADV7180 video decoder also requires the
i2c-mux-gpio and the max7310 port expander.

Signed-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>