GitHub PushEvent at 2014-10-23 23:22:50
Repository: mediatree
Actor: slongerbeam
Payload: {"shas":[["88fb4dcd1cc77a372e6afe522fa56c05681ae2d3","8c188e05ba274fa98ae533cac185ab207938eb34@mentor.com","ARM: dts: imx6-sabreauto: add video capture ports and endpoints\n\nDefines the host v4l2-capture device node and the ADV7180 decoder\nsensor. The host capture device is a child of ipu1. The ADV7180 is\nconnected to the host parallel-bus endpoint on CSI0.\n\nOn the sabreauto, two analog video inputs are routed to the ADV7180,\ncomposite on Ain1, and composite on Ain3. Those inputs are defined\nvia inputs and input-names under the host endpoint node on CSI0.\n\nRegulators and port expanders are defined which are required for the\nADV7180 (power pin is via port expander gpio on i2c3). The reset pin\nto the port expander chip (MAX7310) is controlled by a gpio, so define\nthe reset-gpios property to control it.\n\nThe sabreauto uses a steering pin to select between the SDA signal on\ni2c3 bus, and a data-in pin for an SPI NOR chip. Use i2cmux to control\nthis steering pin. Idle state of the i2cmux selects SPI NOR. This is not\na classic way to use i2cmux, since one side of the mux selects something\nother than an i2c bus, but it works and is probably the cleanest\nsolution. Note that if one thread is attempting to access SPI NOR while\nanother thread is accessing i2c3, the SPI NOR access will fail since the\ni2cmux has selected the SDA pin rather than SPI NOR data-in. This couldn't\nbe avoided in any case, the board is not designed to allow concurrent\ni2c3 and SPI NOR functions (and the default device-tree does not enable\nSPI NOR anyway).\n\nSigned-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>","Steve Longerbeam",true],["54769d852ae07c7459e3ffa32f748fa7418e8aba","8c188e05ba274fa98ae533cac185ab207938eb34@mentor.com","ARM: imx6dl: Add iomux field defines for imx6dl\n\nStart adding iomux field defines for imx6dl. Adds GPR13 fields for\nMIPI-CSI2/Parallel video mux selection.\n\nSigned-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>","Steve Longerbeam",true],["2197c3880e9add870448023c8301785ec25f2bf4","8c188e05ba274fa98ae533cac185ab207938eb34@mentor.com","ARM: imx: Add imx6 video capture platform_data\n\nAdds platform_data for imx6 v4l2 video capture device. Implements\nset_video_mux(), which sets the video capture mux in IOMUXC, which\nselects between MIPI CSI-2 gasket and Parallel camera sensor\ninterface.\n\nSigned-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>","Steve Longerbeam",true],["a2e6958d570758412e542aa1b645deab657e78d7","8c188e05ba274fa98ae533cac185ab207938eb34@mentor.com","gpio: pca953x: Add reset-gpios property\n\nAdd optional reset-gpios property. If present, de-assert the\nspecified reset gpio pin to bring the chip out of reset.\n\nSigned-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>","Steve Longerbeam",true],["44f243d2ac42e298a2f471b2219edb9cc7b78810","8c188e05ba274fa98ae533cac185ab207938eb34@mentor.com","media: imx6: Add device tree binding documentation\n\nAdd device tree binding documentation for i.MX6 media devices.\n\nSigned-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>","Steve Longerbeam",true],["bc8e906faf9c37eef5e309adbf1b0d4935e777a7","8c188e05ba274fa98ae533cac185ab207938eb34@mentor.com","media: Add new camera interface driver for i.MX6\n\nThis is a V4L2 camera interface driver for i.MX6. See\nDocumentation/video4linux/mx6_camera.txt.\n\nSigned-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>\nSigned-off-by: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com>\nSigned-off-by: Jiada Wang <jiada_wang@mentor.com>\nSigned-off-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>","Steve Longerbeam",true],["20800433b5d3a9269a4e69e41f1253aff37957f7","8c188e05ba274fa98ae533cac185ab207938eb34@mentor.com","media: imx6: Add support for MIPI CSI-2 OV5640\n\nThis driver is based on ov5640_mipi.c from Freescale imx_3.10.17_1.0.0_beta\nbranch, modified heavily for code cleanup and converted from int-device\nto subdev.\n\nSigned-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>","Steve Longerbeam",true],["d31f449b0f9fca9539de60d79120f40de1a446fa","8c188e05ba274fa98ae533cac185ab207938eb34@mentor.com","media: imx6: Add support for Parallel OV5642\n\nThis driver is based on ov5642.c from Freescale imx_3.10.17_1.0.0_beta\nbranch, modified heavily for code cleanup and converted from int-device\nto subdev.\n\nSigned-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>","Steve Longerbeam",true],["53902d865730c0be86e3dbe27308f7729af468a5","8c188e05ba274fa98ae533cac185ab207938eb34@mentor.com","media: imx6: Add support for ADV7180 Video Decoder\n\nThis driver is based on adv7180.c from Freescale imx_3.10.17_1.0.0_beta\nbranch, modified heavily for code cleanup and converted from int-device\nto subdev.\n\nSigned-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>","Steve Longerbeam",true],["c09f5af631b8f4c8f342ff96f081356a76e45bac","8c188e05ba274fa98ae533cac185ab207938eb34@mentor.com","media: imx6 camera: Add deinterlace motion control\n\nAdd a custom control to set a motion compensation setting for\ndeinterlacing using the VDIC.\n\nUse of the VDIC is not compatible with preview because both\nrequire the IC viewfinder task.\n\nSigned-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>","Steve Longerbeam",true],["045281f69c7c1cbdd4b34dc5279c76db9567566b","8c188e05ba274fa98ae533cac185ab207938eb34@mentor.com","media: imx6 camera: Add VDIC deinterlacing subdev\n\nThis subdev implements two different video pipelines:\n\nCSI -> VDIC -> IC-VF -> CH21 -> MEM\n\nIn this pipeline, the CSI sends a single interlaced field F(n-1)\ndirectly to the VDIC (and optionally the following field F(n)\ncan be sent to memory via IDMAC channel 13). This pipeline only works\nin VDIC's high motion mode, which only requires a single field for\nprocessing. The other motion modes (low and medium) require three fields,\nso this pipeline does not work in those modes. Also, it is not clear how\nthis pipeline can deal with the various field orders (sequential BT/TB,\ninterlaced BT/TB) and there are reported image quality issues output\nfrom the VDIC in this pipeline.\n\nCSI -> CH[0-3] -> MEM -> CH8,9,10 -> VDIC -> IC-VF -> CH21 -> MEM\n\nIn this pipeline, the CSI sends raw and full frames to memory buffers\nvia the IDMAC SMFC channels 0-3. Fields from these frames are then\ntransferred to the VDIC via IDMAC channels 8,9,10. The VDIC requires\nthree fields: previous field F(n-1), current field F(n), and next\nfield F(n+1), so we need three raw frames in memory: two completed frames\nto send F(n-1), F(n), F(n+1) to the VDIC, and a third frame for active\nCSI capture while the completed fields are sent through the VDIC->IC for\nprocessing.\n\nWhile the \"direct\" CSI->VDIC pipeline requires less memory bus bandwidth\n(just 1 channel vs. 5 channels for indirect pipeline), it can't be used\nfor all motion modes, it only processes a single field (so half the\noriginal image resolution is lost), and it has the image quality issues\nmentioned above. With the indirect pipeline we have full control over\nfield order. So by default the direct pipeline is disabled via a module\nparameter, if enabled it will be used by high motion mode.\n\nSigned-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>","Steve Longerbeam",true],["472ac81d53b8b967792e2666d6808c1038bff10b","8c188e05ba274fa98ae533cac185ab207938eb34@mentor.com","ARM: imx_v6_v7_defconfig: Enable staging video4linux drivers\n\nEnable imx6 v4l2 staging drivers as modules. For video capture on\nthe SabreAuto, the ADV7180 video decoder also requires the\ni2c-mux-gpio and the max7310 port expander.\n\nSigned-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>","Steve Longerbeam",true]],"size":12,"ref":"refs/heads/mx6-camera-staging-v2","head":"472ac81d53b8b967792e2666d6808c1038bff10b"}