| imx.rst (32e2eae23f8fd1b90d86f4d04ca9790952d9d928) | imx.rst (cdb82f826eca487cda530909e543b6cfee61d89b) |
|---|---|
| 1.. SPDX-License-Identifier: GPL-2.0 2 3i.MX Video Capture Driver 4========================= 5 6Introduction 7------------ 8 --- 88 unchanged lines hidden (view full) --- 97 defined that allow sending frames to the VDIC subdev directly from the 98 CSI. There is also support in the future for sending frames to the 99 VDIC from memory buffers via a output/mem2mem devices. 100 101- Includes a Frame Interval Monitor (FIM) that can correct vertical sync 102 problems with the ADV718x video decoders. 103 104 | 1.. SPDX-License-Identifier: GPL-2.0 2 3i.MX Video Capture Driver 4========================= 5 6Introduction 7------------ 8 --- 88 unchanged lines hidden (view full) --- 97 defined that allow sending frames to the VDIC subdev directly from the 98 CSI. There is also support in the future for sending frames to the 99 VDIC from memory buffers via a output/mem2mem devices. 100 101- Includes a Frame Interval Monitor (FIM) that can correct vertical sync 102 problems with the ADV718x video decoders. 103 104 |
| 105Topology 106-------- 107 108The following shows the media topologies for the i.MX6Q SabreSD and 109i.MX6Q SabreAuto. Refer to these diagrams in the entity descriptions 110in the next section. 111 112The i.MX5/6 topologies can differ upstream from the IPUv3 CSI video 113multiplexers, but the internal IPUv3 topology downstream from there 114is common to all i.MX5/6 platforms. For example, the SabreSD, with the 115MIPI CSI-2 OV5640 sensor, requires the i.MX6 MIPI CSI-2 receiver. But 116the SabreAuto has only the ADV7180 decoder on a parallel bt.656 bus, and 117therefore does not require the MIPI CSI-2 receiver, so it is missing in 118its graph. 119 120.. _imx6q_topology_graph: 121 122.. kernel-figure:: imx6q-sabresd.dot 123 :alt: Diagram of the i.MX6Q SabreSD media pipeline topology 124 :align: center 125 126 Media pipeline graph on i.MX6Q SabreSD 127 128.. kernel-figure:: imx6q-sabreauto.dot 129 :alt: Diagram of the i.MX6Q SabreAuto media pipeline topology 130 :align: center 131 132 Media pipeline graph on i.MX6Q SabreAuto 133 |
|
| 105Entities 106-------- 107 108imx6-mipi-csi2 109-------------- 110 111This is the MIPI CSI-2 receiver entity. It has one sink pad to receive 112the MIPI CSI-2 stream (usually from a MIPI CSI-2 camera sensor). It has --- 259 unchanged lines hidden (view full) --- 372from the subdev or from the active capture device interface. For 373example, the FIM controls are available either from the ipuX_csiY 374subdevs or from the active capture device. 375 376The following are specific usage notes for the Sabre* reference 377boards: 378 379 | 134Entities 135-------- 136 137imx6-mipi-csi2 138-------------- 139 140This is the MIPI CSI-2 receiver entity. It has one sink pad to receive 141the MIPI CSI-2 stream (usually from a MIPI CSI-2 camera sensor). It has --- 259 unchanged lines hidden (view full) --- 401from the subdev or from the active capture device interface. For 402example, the FIM controls are available either from the ipuX_csiY 403subdevs or from the active capture device. 404 405The following are specific usage notes for the Sabre* reference 406boards: 407 408 |
| 380SabreLite with OV5642 and OV5640 381-------------------------------- | 409i.MX6Q SabreLite with OV5642 and OV5640 410--------------------------------------- |
| 382 383This platform requires the OmniVision OV5642 module with a parallel 384camera interface, and the OV5640 module with a MIPI CSI-2 385interface. Both modules are available from Boundary Devices: 386 387- https://boundarydevices.com/product/nit6x_5mp 388- https://boundarydevices.com/product/nit6x_5mp_mipi 389 --- 152 unchanged lines hidden (view full) --- 542 v4l2-ctl -d2 --set-fmt-video=field=none 543 544Streaming can then begin on /dev/video2. The v4l2-ctl tool can also be 545used to select any supported YUV pixelformat on /dev/video2. 546 547This platform accepts Composite Video analog inputs to the ADV7180 on 548Ain1 (connector J42). 549 | 411 412This platform requires the OmniVision OV5642 module with a parallel 413camera interface, and the OV5640 module with a MIPI CSI-2 414interface. Both modules are available from Boundary Devices: 415 416- https://boundarydevices.com/product/nit6x_5mp 417- https://boundarydevices.com/product/nit6x_5mp_mipi 418 --- 152 unchanged lines hidden (view full) --- 571 v4l2-ctl -d2 --set-fmt-video=field=none 572 573Streaming can then begin on /dev/video2. The v4l2-ctl tool can also be 574used to select any supported YUV pixelformat on /dev/video2. 575 576This platform accepts Composite Video analog inputs to the ADV7180 on 577Ain1 (connector J42). 578 |
| 550SabreSD with MIPI CSI-2 OV5640 551------------------------------ | 579i.MX6Q SabreSD with MIPI CSI-2 OV5640 580------------------------------------- |
| 552 | 581 |
| 553Similarly to SabreLite, the SabreSD supports a parallel interface 554OV5642 module on IPU1 CSI0, and a MIPI CSI-2 OV5640 module. The OV5642 555connects to i2c bus 1 and the OV5640 to i2c bus 2. | 582Similarly to i.MX6Q SabreLite, the i.MX6Q SabreSD supports a parallel 583interface OV5642 module on IPU1 CSI0, and a MIPI CSI-2 OV5640 584module. The OV5642 connects to i2c bus 1 and the OV5640 to i2c bus 2. |
| 556 557The device tree for SabreSD includes OF graphs for both the parallel 558OV5642 and the MIPI CSI-2 OV5640, but as of this writing only the MIPI 559CSI-2 OV5640 has been tested, so the OV5642 node is currently disabled. 560The OV5640 module connects to MIPI connector J5 (sorry I don't have the 561compatible module part number or URL). 562 563The following example configures a direct conversion pipeline to capture --- 58 unchanged lines hidden --- | 585 586The device tree for SabreSD includes OF graphs for both the parallel 587OV5642 and the MIPI CSI-2 OV5640, but as of this writing only the MIPI 588CSI-2 OV5640 has been tested, so the OV5642 node is currently disabled. 589The OV5640 module connects to MIPI connector J5 (sorry I don't have the 590compatible module part number or URL). 591 592The following example configures a direct conversion pipeline to capture --- 58 unchanged lines hidden --- |