€•Å      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ)/translations/zh_CN/admin-guide/media/imx”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/zh_TW/admin-guide/media/imx”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/it_IT/admin-guide/media/imx”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/ja_JP/admin-guide/media/imx”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/ko_KR/admin-guide/media/imx”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/sp_SP/admin-guide/media/imx”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒC/var/lib/git/docbuild/linux/Documentation/admin-guide/media/imx.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒi.MX Video Capture Driver”h]”hŒi.MX Video Capture Driver”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒIntroduction”h]”hŒIntroduction”…””}”(hhÌhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hhÉhžhhŸh³h KubhŒ	paragraph”“”)”}”(hŒ–The Freescale i.MX5/6 contains an Image Processing Unit (IPU), which
handles the flow of image frames to and from capture devices and
display devices.”h]”hŒ–The Freescale i.MX5/6 contains an Image Processing Unit (IPU), which
handles the flow of image frames to and from capture devices and
display devices.”…””}”(hhÜhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K	hhÉhžhubhÛ)”}”(hŒDFor image capture, the IPU contains the following internal subunits:”h]”hŒDFor image capture, the IPU contains the following internal subunits:”…””}”(hhêhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KhhÉhžhubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒImage DMA Controller (IDMAC)”h]”hÛ)”}”(hj  h]”hŒImage DMA Controller (IDMAC)”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Khhÿubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhhúhžhhŸh³h Nubhþ)”}”(hŒCamera Serial Interface (CSI)”h]”hÛ)”}”(hj  h]”hŒCamera Serial Interface (CSI)”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhhúhžhhŸh³h Nubhþ)”}”(hŒImage Converter (IC)”h]”hÛ)”}”(hj/  h]”hŒImage Converter (IC)”…””}”(hj1  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Khj-  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhhúhžhhŸh³h Nubhþ)”}”(hŒ#Sensor Multi-FIFO Controller (SMFC)”h]”hÛ)”}”(hjF  h]”hŒ#Sensor Multi-FIFO Controller (SMFC)”…””}”(hjH  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KhjD  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhhúhžhhŸh³h Nubhþ)”}”(hŒImage Rotator (IRT)”h]”hÛ)”}”(hj]  h]”hŒImage Rotator (IRT)”…””}”(hj_  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Khj[  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhhúhžhhŸh³h Nubhþ)”}”(hŒ/Video De-Interlacing or Combining Block (VDIC)
”h]”hÛ)”}”(hŒ.Video De-Interlacing or Combining Block (VDIC)”h]”hŒ.Video De-Interlacing or Combining Block (VDIC)”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Khjr  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhhúhžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1høhŸh³h KhhÉhžhubhÛ)”}”(hX  The IDMAC is the DMA controller for transfer of image frames to and from
memory. Various dedicated DMA channels exist for both video capture and
display paths. During transfer, the IDMAC is also capable of vertical
image flip, 8x8 block transfer (see IRT description), pixel component
re-ordering (for example UYVY to YUYV) within the same colorspace, and
packed <--> planar conversion. The IDMAC can also perform a simple
de-interlacing by interweaving even and odd lines during transfer
(without motion compensation which requires the VDIC).”h]”hX  The IDMAC is the DMA controller for transfer of image frames to and from
memory. Various dedicated DMA channels exist for both video capture and
display paths. During transfer, the IDMAC is also capable of vertical
image flip, 8x8 block transfer (see IRT description), pixel component
re-ordering (for example UYVY to YUYV) within the same colorspace, and
packed <--> planar conversion. The IDMAC can also perform a simple
de-interlacing by interweaving even and odd lines during transfer
(without motion compensation which requires the VDIC).”…””}”(hj’  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KhhÉhžhubhÛ)”}”(hŒ‚The CSI is the backend capture unit that interfaces directly with
camera sensors over Parallel, BT.656/1120, and MIPI CSI-2 buses.”h]”hŒ‚The CSI is the backend capture unit that interfaces directly with
camera sensors over Parallel, BT.656/1120, and MIPI CSI-2 buses.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KhhÉhžhubhÛ)”}”(hŒ„The IC handles color-space conversion, resizing (downscaling and
upscaling), horizontal flip, and 90/270 degree rotation operations.”h]”hŒ„The IC handles color-space conversion, resizing (downscaling and
upscaling), horizontal flip, and 90/270 degree rotation operations.”…””}”(hj®  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K"hhÉhžhubhÛ)”}”(hX\  There are three independent "tasks" within the IC that can carry out
conversions concurrently: pre-process encoding, pre-process viewfinder,
and post-processing. Within each task, conversions are split into three
sections: downsizing section, main section (upsizing, flip, colorspace
conversion, and graphics plane combining), and rotation section.”h]”hX`  There are three independent â€œtasksâ€ within the IC that can carry out
conversions concurrently: pre-process encoding, pre-process viewfinder,
and post-processing. Within each task, conversions are split into three
sections: downsizing section, main section (upsizing, flip, colorspace
conversion, and graphics plane combining), and rotation section.”…””}”(hj¼  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K%hhÉhžhubhÛ)”}”(hŒÖThe IPU time-shares the IC task operations. The time-slice granularity
is one burst of eight pixels in the downsizing section, one image line
in the main processing section, one image frame in the rotation section.”h]”hŒÖThe IPU time-shares the IC task operations. The time-slice granularity
is one burst of eight pixels in the downsizing section, one image line
in the main processing section, one image frame in the rotation section.”…””}”(hjÊ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K+hhÉhžhubhÛ)”}”(hŒ›The SMFC is composed of four independent FIFOs that each can transfer
captured frames from sensors directly to memory concurrently via four
IDMAC channels.”h]”hŒ›The SMFC is composed of four independent FIFOs that each can transfer
captured frames from sensors directly to memory concurrently via four
IDMAC channels.”…””}”(hjØ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K/hhÉhžhubhÛ)”}”(hX  The IRT carries out 90 and 270 degree image rotation operations. The
rotation operation is carried out on 8x8 pixel blocks at a time. This
operation is supported by the IDMAC which handles the 8x8 block transfer
along with block reordering, in coordination with vertical flip.”h]”hX  The IRT carries out 90 and 270 degree image rotation operations. The
rotation operation is carried out on 8x8 pixel blocks at a time. This
operation is supported by the IDMAC which handles the 8x8 block transfer
along with block reordering, in coordination with vertical flip.”…””}”(hjæ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K3hhÉhžhubhÛ)”}”(hXx  The VDIC handles the conversion of interlaced video to progressive, with
support for different motion compensation modes (low, medium, and high
motion). The deinterlaced output frames from the VDIC can be sent to the
IC pre-process viewfinder task for further conversions. The VDIC also
contains a Combiner that combines two image planes, with alpha blending
and color keying.”h]”hXx  The VDIC handles the conversion of interlaced video to progressive, with
support for different motion compensation modes (low, medium, and high
motion). The deinterlaced output frames from the VDIC can be sent to the
IC pre-process viewfinder task for further conversions. The VDIC also
contains a Combiner that combines two image planes, with alpha blending
and color keying.”…””}”(hjô  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K8hhÉhžhubhÛ)”}”(hŒƒIn addition to the IPU internal subunits, there are also two units
outside the IPU that are also involved in video capture on i.MX:”h]”hŒƒIn addition to the IPU internal subunits, there are also two units
outside the IPU that are also involved in video capture on i.MX:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K?hhÉhžhubhù)”}”(hhh]”(hþ)”}”(hŒmMIPI CSI-2 Receiver for camera sensors with the MIPI CSI-2 bus
interface. This is a Synopsys DesignWare core.”h]”hÛ)”}”(hŒmMIPI CSI-2 Receiver for camera sensors with the MIPI CSI-2 bus
interface. This is a Synopsys DesignWare core.”h]”hŒmMIPI CSI-2 Receiver for camera sensors with the MIPI CSI-2 bus
interface. This is a Synopsys DesignWare core.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KBhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhj  hžhhŸh³h Nubhþ)”}”(hŒTTwo video multiplexers for selecting among multiple sensor inputs
to send to a CSI.
”h]”hÛ)”}”(hŒSTwo video multiplexers for selecting among multiple sensor inputs
to send to a CSI.”h]”hŒSTwo video multiplexers for selecting among multiple sensor inputs
to send to a CSI.”…””}”(hj/  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KDhj+  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhj  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”j  j‘  uh1høhŸh³h KBhhÉhžhubhÛ)”}”(hŒ_For more info, refer to the latest versions of the i.MX5/6 reference
manuals [#f1]_ and [#f2]_.”h]”(hŒMFor more info, refer to the latest versions of the i.MX5/6 reference
manuals ”…””}”(hjI  hžhhŸNh NubhŒfootnote_reference”“”)”}”(hŒ[#f1]_”h]”hŒ1”…””}”(hjS  hžhhŸNh Nubah}”(h]”Œid1”ah ]”h"]”h$]”h&]”Œauto”KŒrefid”Œf1”Œdocname”Œadmin-guide/media/imx”uh1jQ  hjI  Œresolved”KubhŒ and ”…””}”(hjI  hžhhŸNh NubjR  )”}”(hŒ[#f2]_”h]”hŒ2”…””}”(hjl  hžhhŸNh Nubah}”(h]”Œid2”ah ]”h"]”h$]”h&]”jb  Kjc  Œf2”je  jf  uh1jQ  hjI  jg  KubhŒ.”…””}”(hjI  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KGhhÉhžhubeh}”(h]”Œintroduction”ah ]”h"]”Œintroduction”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒFeatures”h]”hŒFeatures”…””}”(hj‘  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjŽ  hžhhŸh³h KLubhÛ)”}”(hŒ,Some of the features of this driver include:”h]”hŒ,Some of the features of this driver include:”…””}”(hjŸ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KNhjŽ  hžhubhù)”}”(hhh]”(hþ)”}”(hŒ”Many different pipelines can be configured via media controller API,
that correspond to the hardware video capture pipelines supported in
the i.MX.
”h]”hÛ)”}”(hŒ“Many different pipelines can be configured via media controller API,
that correspond to the hardware video capture pipelines supported in
the i.MX.”h]”hŒ“Many different pipelines can be configured via media controller API,
that correspond to the hardware video capture pipelines supported in
the i.MX.”…””}”(hj´  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KPhj°  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhj­  hžhhŸh³h Nubhþ)”}”(hŒ6Supports parallel, BT.565, and MIPI CSI-2 interfaces.
”h]”hÛ)”}”(hŒ5Supports parallel, BT.565, and MIPI CSI-2 interfaces.”h]”hŒ5Supports parallel, BT.565, and MIPI CSI-2 interfaces.”…””}”(hjÌ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KThjÈ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhj­  hžhhŸh³h Nubhþ)”}”(hŒzConcurrent independent streams, by configuring pipelines to multiple
video capture interfaces using independent entities.
”h]”hÛ)”}”(hŒyConcurrent independent streams, by configuring pipelines to multiple
video capture interfaces using independent entities.”h]”hŒyConcurrent independent streams, by configuring pipelines to multiple
video capture interfaces using independent entities.”…””}”(hjä  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KVhjà  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhj­  hžhhŸh³h Nubhþ)”}”(hŒgScaling, color-space conversion, horizontal and vertical flip, and
image rotation via IC task subdevs.
”h]”hÛ)”}”(hŒfScaling, color-space conversion, horizontal and vertical flip, and
image rotation via IC task subdevs.”h]”hŒfScaling, color-space conversion, horizontal and vertical flip, and
image rotation via IC task subdevs.”…””}”(hjü  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KYhjø  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhj­  hžhhŸh³h Nubhþ)”}”(hŒOMany pixel formats supported (RGB, packed and planar YUV, partial
planar YUV).
”h]”hÛ)”}”(hŒNMany pixel formats supported (RGB, packed and planar YUV, partial
planar YUV).”h]”hŒNMany pixel formats supported (RGB, packed and planar YUV, partial
planar YUV).”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K\hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhj­  hžhhŸh³h Nubhþ)”}”(hXO  The VDIC subdev supports motion compensated de-interlacing, with three
motion compensation modes: low, medium, and high motion. Pipelines are
defined that allow sending frames to the VDIC subdev directly from the
CSI. There is also support in the future for sending frames to the
VDIC from memory buffers via a output/mem2mem devices.
”h]”hÛ)”}”(hXN  The VDIC subdev supports motion compensated de-interlacing, with three
motion compensation modes: low, medium, and high motion. Pipelines are
defined that allow sending frames to the VDIC subdev directly from the
CSI. There is also support in the future for sending frames to the
VDIC from memory buffers via a output/mem2mem devices.”h]”hXN  The VDIC subdev supports motion compensated de-interlacing, with three
motion compensation modes: low, medium, and high motion. Pipelines are
defined that allow sending frames to the VDIC subdev directly from the
CSI. There is also support in the future for sending frames to the
VDIC from memory buffers via a output/mem2mem devices.”…””}”(hj,  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K_hj(  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhj­  hžhhŸh³h Nubhþ)”}”(hŒrIncludes a Frame Interval Monitor (FIM) that can correct vertical sync
problems with the ADV718x video decoders.

”h]”hÛ)”}”(hŒpIncludes a Frame Interval Monitor (FIM) that can correct vertical sync
problems with the ADV718x video decoders.”h]”hŒpIncludes a Frame Interval Monitor (FIM) that can correct vertical sync
problems with the ADV718x video decoders.”…””}”(hjD  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kehj@  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhj­  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”j  j‘  uh1høhŸh³h KPhjŽ  hžhubeh}”(h]”Œfeatures”ah ]”h"]”Œfeatures”ah$]”h&]”uh1h´hh¶hžhhŸh³h KLubhµ)”}”(hhh]”(hº)”}”(hŒTopology”h]”hŒTopology”…””}”(hji  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjf  hžhhŸh³h KjubhÛ)”}”(hŒThe following shows the media topologies for the i.MX6Q SabreSD and
i.MX6Q SabreAuto. Refer to these diagrams in the entity descriptions
in the next section.”h]”hŒThe following shows the media topologies for the i.MX6Q SabreSD and
i.MX6Q SabreAuto. Refer to these diagrams in the entity descriptions
in the next section.”…””}”(hjw  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Klhjf  hžhubhÛ)”}”(hX°  The i.MX5/6 topologies can differ upstream from the IPUv3 CSI video
multiplexers, but the internal IPUv3 topology downstream from there
is common to all i.MX5/6 platforms. For example, the SabreSD, with the
MIPI CSI-2 OV5640 sensor, requires the i.MX6 MIPI CSI-2 receiver. But
the SabreAuto has only the ADV7180 decoder on a parallel bt.656 bus, and
therefore does not require the MIPI CSI-2 receiver, so it is missing in
its graph.”h]”hX°  The i.MX5/6 topologies can differ upstream from the IPUv3 CSI video
multiplexers, but the internal IPUv3 topology downstream from there
is common to all i.MX5/6 platforms. For example, the SabreSD, with the
MIPI CSI-2 OV5640 sensor, requires the i.MX6 MIPI CSI-2 receiver. But
the SabreAuto has only the ADV7180 decoder on a parallel bt.656 bus, and
therefore does not require the MIPI CSI-2 receiver, so it is missing in
its graph.”…””}”(hj…  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kphjf  hžhubhŒtarget”“”)”}”(hŒ.. _imx6q_topology_graph:”h]”h}”(h]”h ]”h"]”h$]”h&]”jc  Œimx6q-topology-graph”uh1j“  h Kxhjf  hžhhŸh³ubŒkfigure”Œkernel_figure”“”)”}”(hhh]”hŒfigure”“”)”}”(hhh]”(hŒimage”“”)”}”(hŒ¦.. kernel-figure:: imx6q-sabresd.dot
    :alt:   Diagram of the i.MX6Q SabreSD media pipeline topology
    :align: center

    Media pipeline graph on i.MX6Q SabreSD
”h]”h}”(h]”h ]”h"]”h$]”h&]”Œalt”Œ5Diagram of the i.MX6Q SabreSD media pipeline topology”Œuri”Œ#admin-guide/media/imx6q-sabresd.dot”Œ
candidates”}”Œ*”jº  suh1j«  hj¨  hŸh³h K ubhŒcaption”“”)”}”(hŒ&Media pipeline graph on i.MX6Q SabreSD”h]”hŒ&Media pipeline graph on i.MX6Q SabreSD”…””}”(hjÀ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¾  hŸh³h K~hj¨  ubeh}”(h]”Œid3”ah ]”h"]”h$]”h&]”Œalign”Œcenter”uh1j¦  hj£  ubah}”(h]”jŸ  ah ]”h"]”Œimx6q_topology_graph”ah$]”h&]”uh1j¡  hjf  hžhhŸh³h NŒexpect_referenced_by_name”}”jÛ  j•  sŒexpect_referenced_by_id”}”jŸ  j•  subj¢  )”}”(hhh]”j§  )”}”(hhh]”(j¬  )”}”(hŒ¬.. kernel-figure:: imx6q-sabreauto.dot
    :alt:   Diagram of the i.MX6Q SabreAuto media pipeline topology
    :align: center

    Media pipeline graph on i.MX6Q SabreAuto
”h]”h}”(h]”h ]”h"]”h$]”h&]”Œalt”Œ7Diagram of the i.MX6Q SabreAuto media pipeline topology”Œuri”Œ%admin-guide/media/imx6q-sabreauto.dot”j»  }”j½  jõ  suh1j«  hjå  hŸh³h K ubj¿  )”}”(hŒ(Media pipeline graph on i.MX6Q SabreAuto”h]”hŒ(Media pipeline graph on i.MX6Q SabreAuto”…””}”(hj÷  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¾  hŸh³h K„hjå  ubeh}”(h]”Œid4”ah ]”h"]”h$]”h&]”jÕ  Œcenter”uh1j¦  hjâ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¡  hjf  hžhhŸh³h Nubeh}”(h]”Œtopology”ah ]”h"]”Œtopology”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kjubhµ)”}”(hhh]”hº)”}”(hŒEntities”h]”hŒEntities”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj  hžhhŸh³h K‡ubah}”(h]”Œentities”ah ]”h"]”Œentities”ah$]”h&]”uh1h´hh¶hžhhŸh³h K‡ubhµ)”}”(hhh]”(hº)”}”(hŒimx6-mipi-csi2”h]”hŒimx6-mipi-csi2”…””}”(hj7  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj4  hžhhŸh³h KŠubhÛ)”}”(hXB  This is the MIPI CSI-2 receiver entity. It has one sink pad to receive
the MIPI CSI-2 stream (usually from a MIPI CSI-2 camera sensor). It has
four source pads, corresponding to the four MIPI CSI-2 demuxed virtual
channel outputs. Multiple source pads can be enabled to independently
stream from multiple virtual channels.”h]”hXB  This is the MIPI CSI-2 receiver entity. It has one sink pad to receive
the MIPI CSI-2 stream (usually from a MIPI CSI-2 camera sensor). It has
four source pads, corresponding to the four MIPI CSI-2 demuxed virtual
channel outputs. Multiple source pads can be enabled to independently
stream from multiple virtual channels.”…””}”(hjE  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KŒhj4  hžhubhÛ)”}”(hX}  This entity actually consists of two sub-blocks. One is the MIPI CSI-2
core. This is a Synopsys Designware MIPI CSI-2 core. The other sub-block
is a "CSI-2 to IPU gasket". The gasket acts as a demultiplexer of the
four virtual channels streams, providing four separate parallel buses
containing each virtual channel that are routed to CSIs or video
multiplexers as described below.”h]”hX  This entity actually consists of two sub-blocks. One is the MIPI CSI-2
core. This is a Synopsys Designware MIPI CSI-2 core. The other sub-block
is a â€œCSI-2 to IPU gasketâ€. The gasket acts as a demultiplexer of the
four virtual channels streams, providing four separate parallel buses
containing each virtual channel that are routed to CSIs or video
multiplexers as described below.”…””}”(hjS  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K’hj4  hžhubhÛ)”}”(hŒ¸On i.MX6 solo/dual-lite, all four virtual channel buses are routed to
two video multiplexers. Both CSI0 and CSI1 can receive any virtual
channel, as selected by the video multiplexers.”h]”hŒ¸On i.MX6 solo/dual-lite, all four virtual channel buses are routed to
two video multiplexers. Both CSI0 and CSI1 can receive any virtual
channel, as selected by the video multiplexers.”…””}”(hja  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K™hj4  hžhubhÛ)”}”(hŒøOn i.MX6 Quad, virtual channel 0 is routed to IPU1-CSI0 (after selected
by a video mux), virtual channels 1 and 2 are hard-wired to IPU1-CSI1
and IPU2-CSI0, respectively, and virtual channel 3 is routed to
IPU2-CSI1 (again selected by a video mux).”h]”hŒøOn i.MX6 Quad, virtual channel 0 is routed to IPU1-CSI0 (after selected
by a video mux), virtual channels 1 and 2 are hard-wired to IPU1-CSI1
and IPU2-CSI0, respectively, and virtual channel 3 is routed to
IPU2-CSI1 (again selected by a video mux).”…””}”(hjo  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Khj4  hžhubeh}”(h]”Œimx6-mipi-csi2”ah ]”h"]”Œimx6-mipi-csi2”ah$]”h&]”uh1h´hh¶hžhhŸh³h KŠubhµ)”}”(hhh]”(hº)”}”(hŒipuX_csiY_mux”h]”hŒipuX_csiY_mux”…””}”(hjˆ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj…  hžhhŸh³h K£ubhÛ)”}”(hX
  These are the video multiplexers. They have two or more sink pads to
select from either camera sensors with a parallel interface, or from
MIPI CSI-2 virtual channels from imx6-mipi-csi2 entity. They have a
single source pad that routes to a CSI (ipuX_csiY entities).”h]”hX
  These are the video multiplexers. They have two or more sink pads to
select from either camera sensors with a parallel interface, or from
MIPI CSI-2 virtual channels from imx6-mipi-csi2 entity. They have a
single source pad that routes to a CSI (ipuX_csiY entities).”…””}”(hj–  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K¥hj…  hžhubhÛ)”}”(hXf  On i.MX6 solo/dual-lite, there are two video mux entities. One sits
in front of IPU1-CSI0 to select between a parallel sensor and any of
the four MIPI CSI-2 virtual channels (a total of five sink pads). The
other mux sits in front of IPU1-CSI1, and again has five sink pads to
select between a parallel sensor and any of the four MIPI CSI-2 virtual
channels.”h]”hXf  On i.MX6 solo/dual-lite, there are two video mux entities. One sits
in front of IPU1-CSI0 to select between a parallel sensor and any of
the four MIPI CSI-2 virtual channels (a total of five sink pads). The
other mux sits in front of IPU1-CSI1, and again has five sink pads to
select between a parallel sensor and any of the four MIPI CSI-2 virtual
channels.”…””}”(hj¤  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kªhj…  hžhubhÛ)”}”(hX$  On i.MX6 Quad, there are two video mux entities. One sits in front of
IPU1-CSI0 to select between a parallel sensor and MIPI CSI-2 virtual
channel 0 (two sink pads). The other mux sits in front of IPU2-CSI1 to
select between a parallel sensor and MIPI CSI-2 virtual channel 3 (two
sink pads).”h]”hX$  On i.MX6 Quad, there are two video mux entities. One sits in front of
IPU1-CSI0 to select between a parallel sensor and MIPI CSI-2 virtual
channel 0 (two sink pads). The other mux sits in front of IPU2-CSI1 to
select between a parallel sensor and MIPI CSI-2 virtual channel 3 (two
sink pads).”…””}”(hj²  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K±hj…  hžhubeh}”(h]”Œipux-csiy-mux”ah ]”h"]”Œipux_csiy_mux”ah$]”h&]”uh1h´hh¶hžhhŸh³h K£ubhµ)”}”(hhh]”(hº)”}”(hŒ	ipuX_csiY”h]”hŒ	ipuX_csiY”…””}”(hjË  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÈ  hžhhŸh³h K¸ubhÛ)”}”(hŒ’These are the CSI entities. They have a single sink pad receiving from
either a video mux or from a MIPI CSI-2 virtual channel as described
above.”h]”hŒ’These are the CSI entities. They have a single sink pad receiving from
either a video mux or from a MIPI CSI-2 virtual channel as described
above.”…””}”(hjÙ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KºhjÈ  hžhubhÛ)”}”(hŒ½This entity has two source pads. The first source pad can link directly
to the ipuX_vdic entity or the ipuX_ic_prp entity, using hardware links
that require no IDMAC memory buffer transfer.”h]”hŒ½This entity has two source pads. The first source pad can link directly
to the ipuX_vdic entity or the ipuX_ic_prp entity, using hardware links
that require no IDMAC memory buffer transfer.”…””}”(hjç  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K¾hjÈ  hžhubhÛ)”}”(hŒ“When the direct source pad is routed to the ipuX_ic_prp entity, frames
from the CSI can be processed by one or both of the IC pre-processing
tasks.”h]”hŒ“When the direct source pad is routed to the ipuX_ic_prp entity, frames
from the CSI can be processed by one or both of the IC pre-processing
tasks.”…””}”(hjõ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KÂhjÈ  hžhubhÛ)”}”(hŒµWhen the direct source pad is routed to the ipuX_vdic entity, the VDIC
will carry out motion-compensated de-interlace using "high motion" mode
(see description of ipuX_vdic entity).”h]”hŒ¹When the direct source pad is routed to the ipuX_vdic entity, the VDIC
will carry out motion-compensated de-interlace using â€œhigh motionâ€ mode
(see description of ipuX_vdic entity).”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KÆhjÈ  hžhubhÛ)”}”(hŒëThe second source pad sends video frames directly to memory buffers
via the SMFC and an IDMAC channel, bypassing IC pre-processing. This
source pad is routed to a capture device node, with a node name of the
format "ipuX_csiY capture".”h]”hŒïThe second source pad sends video frames directly to memory buffers
via the SMFC and an IDMAC channel, bypassing IC pre-processing. This
source pad is routed to a capture device node, with a node name of the
format â€œipuX_csiY captureâ€.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KÊhjÈ  hžhubhÛ)”}”(hX¡  Note that since the IDMAC source pad makes use of an IDMAC channel,
pixel reordering within the same colorspace can be carried out by the
IDMAC channel. For example, if the CSI sink pad is receiving in UYVY
order, the capture device linked to the IDMAC source pad can capture
in YUYV order. Also, if the CSI sink pad is receiving a packed YUV
format, the capture device can capture a planar YUV format such as
YUV420.”h]”hX¡  Note that since the IDMAC source pad makes use of an IDMAC channel,
pixel reordering within the same colorspace can be carried out by the
IDMAC channel. For example, if the CSI sink pad is receiving in UYVY
order, the capture device linked to the IDMAC source pad can capture
in YUYV order. Also, if the CSI sink pad is receiving a packed YUV
format, the capture device can capture a planar YUV format such as
YUV420.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KÏhjÈ  hžhubhÛ)”}”(hXÑ  The IDMAC channel at the IDMAC source pad also supports simple
interweave without motion compensation, which is activated if the source
pad's field type is sequential top-bottom or bottom-top, and the
requested capture interface field type is set to interlaced (t-b, b-t,
or unqualified interlaced). The capture interface will enforce the same
field order as the source pad field order (interlaced-bt if source pad
is seq-bt, interlaced-tb if source pad is seq-tb).”h]”hXÓ  The IDMAC channel at the IDMAC source pad also supports simple
interweave without motion compensation, which is activated if the source
padâ€™s field type is sequential top-bottom or bottom-top, and the
requested capture interface field type is set to interlaced (t-b, b-t,
or unqualified interlaced). The capture interface will enforce the same
field order as the source pad field order (interlaced-bt if source pad
is seq-bt, interlaced-tb if source pad is seq-tb).”…””}”(hj-  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K×hjÈ  hžhubhÛ)”}”(hŒ>For events produced by ipuX_csiY, see ref:`imx_api_ipuX_csiY`.”h]”(hŒ*For events produced by ipuX_csiY, see ref:”…””}”(hj;  hžhhŸNh NubhŒtitle_reference”“”)”}”(hŒ`imx_api_ipuX_csiY`”h]”hŒimx_api_ipuX_csiY”…””}”(hjE  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jC  hj;  ubhŒ.”…””}”(hj;  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KßhjÈ  hžhubeh}”(h]”Œ	ipux-csiy”ah ]”h"]”Œ	ipux_csiy”ah$]”h&]”uh1h´hh¶hžhhŸh³h K¸ubhµ)”}”(hhh]”(hº)”}”(hŒCropping in ipuX_csiY”h]”hŒCropping in ipuX_csiY”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hje  hžhhŸh³h KâubhÛ)”}”(hŒThe CSI supports cropping the incoming raw sensor frames. This is
implemented in the ipuX_csiY entities at the sink pad, using the
crop selection subdev API.”h]”hŒThe CSI supports cropping the incoming raw sensor frames. This is
implemented in the ipuX_csiY entities at the sink pad, using the
crop selection subdev API.”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kähje  hžhubhÛ)”}”(hŒ¿The CSI also supports fixed divide-by-two downscaling independently in
width and height. This is implemented in the ipuX_csiY entities at
the sink pad, using the compose selection subdev API.”h]”hŒ¿The CSI also supports fixed divide-by-two downscaling independently in
width and height. This is implemented in the ipuX_csiY entities at
the sink pad, using the compose selection subdev API.”…””}”(hj„  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kèhje  hžhubhÛ)”}”(hX0  The output rectangle at the ipuX_csiY source pad is the same as
the compose rectangle at the sink pad. So the source pad rectangle
cannot be negotiated, it must be set using the compose selection
API at sink pad (if /2 downscale is desired, otherwise source pad
rectangle is equal to incoming rectangle).”h]”hX0  The output rectangle at the ipuX_csiY source pad is the same as
the compose rectangle at the sink pad. So the source pad rectangle
cannot be negotiated, it must be set using the compose selection
API at sink pad (if /2 downscale is desired, otherwise source pad
rectangle is equal to incoming rectangle).”…””}”(hj’  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kìhje  hžhubhÛ)”}”(hŒÂTo give an example of crop and /2 downscale, this will crop a
1280x960 input frame to 640x480, and then /2 downscale in both
dimensions to 320x240 (assumes ipu1_csi0 is linked to ipu1_csi0_mux):”h]”hŒÂTo give an example of crop and /2 downscale, this will crop a
1280x960 input frame to 640x480, and then /2 downscale in both
dimensions to 320x240 (assumes ipu1_csi0 is linked to ipu1_csi0_mux):”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kòhje  hžhubhŒliteral_block”“”)”}”(hŒ›media-ctl -V "'ipu1_csi0_mux':2[fmt:UYVY2X8/1280x960]"
media-ctl -V "'ipu1_csi0':0[crop:(0,0)/640x480]"
media-ctl -V "'ipu1_csi0':0[compose:(0,0)/320x240]"”h]”hŒ›media-ctl -V "'ipu1_csi0_mux':2[fmt:UYVY2X8/1280x960]"
media-ctl -V "'ipu1_csi0':0[crop:(0,0)/640x480]"
media-ctl -V "'ipu1_csi0':0[compose:(0,0)/320x240]"”…””}”hj°  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²Œforce”‰Œlanguage”Œnone”Œhighlight_args”}”uh1j®  hŸh³h Köhje  hžhubeh}”(h]”Œcropping-in-ipux-csiy”ah ]”h"]”Œcropping in ipux_csiy”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kâubhµ)”}”(hhh]”(hº)”}”(hŒFrame Skipping in ipuX_csiY”h]”hŒFrame Skipping in ipuX_csiY”…””}”(hjÎ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjË  hžhhŸh³h KýubhÛ)”}”(hX  The CSI supports frame rate decimation, via frame skipping. Frame
rate decimation is specified by setting the frame intervals at
sink and source pads. The ipuX_csiY entity then applies the best
frame skip setting to the CSI to achieve the desired frame rate
at the source pad.”h]”hX  The CSI supports frame rate decimation, via frame skipping. Frame
rate decimation is specified by setting the frame intervals at
sink and source pads. The ipuX_csiY entity then applies the best
frame skip setting to the CSI to achieve the desired frame rate
at the source pad.”…””}”(hjÜ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KÿhjË  hžhubhÛ)”}”(hŒjThe following example reduces an assumed incoming 60 Hz frame
rate by half at the IDMAC output source pad:”h]”hŒjThe following example reduces an assumed incoming 60 Hz frame
rate by half at the IDMAC output source pad:”…””}”(hjê  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MhjË  hžhubj¯  )”}”(hŒmmedia-ctl -V "'ipu1_csi0':0[fmt:UYVY2X8/640x480@1/60]"
media-ctl -V "'ipu1_csi0':2[fmt:UYVY2X8/640x480@1/30]"”h]”hŒmmedia-ctl -V "'ipu1_csi0':0[fmt:UYVY2X8/640x480@1/60]"
media-ctl -V "'ipu1_csi0':2[fmt:UYVY2X8/640x480@1/30]"”…””}”hjø  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h MhjË  hžhubeh}”(h]”Œframe-skipping-in-ipux-csiy”ah ]”h"]”Œframe skipping in ipux_csiy”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kýubhµ)”}”(hhh]”(hº)”}”(hŒ#Frame Interval Monitor in ipuX_csiY”h]”hŒ#Frame Interval Monitor in ipuX_csiY”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj  hžhhŸh³h MubhÛ)”}”(hŒSee ref:`imx_api_FIM`.”h]”(hŒSee ref:”…””}”(hj!  hžhhŸNh NubjD  )”}”(hŒ`imx_api_FIM`”h]”hŒimx_api_FIM”…””}”(hj)  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jC  hj!  ubhŒ.”…””}”(hj!  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mhj  hžhubeh}”(h]”Œ#frame-interval-monitor-in-ipux-csiy”ah ]”h"]”Œ#frame interval monitor in ipux_csiy”ah$]”h&]”uh1h´hh¶hžhhŸh³h Mubhµ)”}”(hhh]”(hº)”}”(hŒ	ipuX_vdic”h]”hŒ	ipuX_vdic”…””}”(hjL  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjI  hžhhŸh³h MubhÛ)”}”(hŒøThe VDIC carries out motion compensated de-interlacing, with three
motion compensation modes: low, medium, and high motion. The mode is
specified with the menu control V4L2_CID_DEINTERLACING_MODE. The VDIC
has two sink pads and a single source pad.”h]”hŒøThe VDIC carries out motion compensated de-interlacing, with three
motion compensation modes: low, medium, and high motion. The mode is
specified with the menu control V4L2_CID_DEINTERLACING_MODE. The VDIC
has two sink pads and a single source pad.”…””}”(hjZ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MhjI  hžhubhÛ)”}”(hŒxThe direct sink pad receives from an ipuX_csiY direct pad. With this
link the VDIC can only operate in high motion mode.”h]”hŒxThe direct sink pad receives from an ipuX_csiY direct pad. With this
link the VDIC can only operate in high motion mode.”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MhjI  hžhubhÛ)”}”(hXH  When the IDMAC sink pad is activated, it receives from an output
or mem2mem device node. With this pipeline, the VDIC can also operate
in low and medium modes, because these modes require receiving
frames from memory buffers. Note that an output or mem2mem device
is not implemented yet, so this sink pad currently has no links.”h]”hXH  When the IDMAC sink pad is activated, it receives from an output
or mem2mem device node. With this pipeline, the VDIC can also operate
in low and medium modes, because these modes require receiving
frames from memory buffers. Note that an output or mem2mem device
is not implemented yet, so this sink pad currently has no links.”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MhjI  hžhubhÛ)”}”(hŒBThe source pad routes to the IC pre-processing entity ipuX_ic_prp.”h]”hŒBThe source pad routes to the IC pre-processing entity ipuX_ic_prp.”…””}”(hj„  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M#hjI  hžhubeh}”(h]”Œ	ipux-vdic”ah ]”h"]”Œ	ipux_vdic”ah$]”h&]”uh1h´hh¶hžhhŸh³h Mubhµ)”}”(hhh]”(hº)”}”(hŒipuX_ic_prp”h]”hŒipuX_ic_prp”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjš  hžhhŸh³h M&ubhÛ)”}”(hŒ|This is the IC pre-processing entity. It acts as a router, routing
data from its sink pad to one or both of its source pads.”h]”hŒ|This is the IC pre-processing entity. It acts as a router, routing
data from its sink pad to one or both of its source pads.”…””}”(hj«  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M(hjš  hžhubhÛ)”}”(hŒmThis entity has a single sink pad. The sink pad can receive from the
ipuX_csiY direct pad, or from ipuX_vdic.”h]”hŒmThis entity has a single sink pad. The sink pad can receive from the
ipuX_csiY direct pad, or from ipuX_vdic.”…””}”(hj¹  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M+hjš  hžhubhÛ)”}”(hXß  This entity has two source pads. One source pad routes to the
pre-process encode task entity (ipuX_ic_prpenc), the other to the
pre-process viewfinder task entity (ipuX_ic_prpvf). Both source pads
can be activated at the same time if the sink pad is receiving from
ipuX_csiY. Only the source pad to the pre-process viewfinder task entity
can be activated if the sink pad is receiving from ipuX_vdic (frames
from the VDIC can only be processed by the pre-process viewfinder task).”h]”hXß  This entity has two source pads. One source pad routes to the
pre-process encode task entity (ipuX_ic_prpenc), the other to the
pre-process viewfinder task entity (ipuX_ic_prpvf). Both source pads
can be activated at the same time if the sink pad is receiving from
ipuX_csiY. Only the source pad to the pre-process viewfinder task entity
can be activated if the sink pad is receiving from ipuX_vdic (frames
from the VDIC can only be processed by the pre-process viewfinder task).”…””}”(hjÇ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M.hjš  hžhubeh}”(h]”Œipux-ic-prp”ah ]”h"]”Œipux_ic_prp”ah$]”h&]”uh1h´hh¶hžhhŸh³h M&ubhµ)”}”(hhh]”(hº)”}”(hŒipuX_ic_prpenc”h]”hŒipuX_ic_prpenc”…””}”(hjà  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÝ  hžhhŸh³h M7ubhÛ)”}”(hŒÜThis is the IC pre-processing encode entity. It has a single sink
pad from ipuX_ic_prp, and a single source pad. The source pad is
routed to a capture device node, with a node name of the format
"ipuX_ic_prpenc capture".”h]”hŒàThis is the IC pre-processing encode entity. It has a single sink
pad from ipuX_ic_prp, and a single source pad. The source pad is
routed to a capture device node, with a node name of the format
â€œipuX_ic_prpenc captureâ€.”…””}”(hjî  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M9hjÝ  hžhubhÛ)”}”(hŒòThis entity performs the IC pre-process encode task operations:
color-space conversion, resizing (downscaling and upscaling),
horizontal and vertical flip, and 90/270 degree rotation. Flip
and rotation are provided via standard V4L2 controls.”h]”hŒòThis entity performs the IC pre-process encode task operations:
color-space conversion, resizing (downscaling and upscaling),
horizontal and vertical flip, and 90/270 degree rotation. Flip
and rotation are provided via standard V4L2 controls.”…””}”(hjü  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M>hjÝ  hžhubhÛ)”}”(hŒLike the ipuX_csiY IDMAC source, this entity also supports simple
de-interlace without motion compensation, and pixel reordering.”h]”hŒLike the ipuX_csiY IDMAC source, this entity also supports simple
de-interlace without motion compensation, and pixel reordering.”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MChjÝ  hžhubeh}”(h]”Œipux-ic-prpenc”ah ]”h"]”Œipux_ic_prpenc”ah$]”h&]”uh1h´hh¶hžhhŸh³h M7ubhµ)”}”(hhh]”(hº)”}”(hŒipuX_ic_prpvf”h]”hŒipuX_ic_prpvf”…””}”(hj#  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj   hžhhŸh³h MGubhÛ)”}”(hŒßThis is the IC pre-processing viewfinder entity. It has a single sink
pad from ipuX_ic_prp, and a single source pad. The source pad is routed
to a capture device node, with a node name of the format
"ipuX_ic_prpvf capture".”h]”hŒãThis is the IC pre-processing viewfinder entity. It has a single sink
pad from ipuX_ic_prp, and a single source pad. The source pad is routed
to a capture device node, with a node name of the format
â€œipuX_ic_prpvf captureâ€.”…””}”(hj1  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MIhj   hžhubhÛ)”}”(hŒîThis entity is identical in operation to ipuX_ic_prpenc, with the same
resizing and CSC operations and flip/rotation controls. It will receive
and process de-interlaced frames from the ipuX_vdic if ipuX_ic_prp is
receiving from ipuX_vdic.”h]”hŒîThis entity is identical in operation to ipuX_ic_prpenc, with the same
resizing and CSC operations and flip/rotation controls. It will receive
and process de-interlaced frames from the ipuX_vdic if ipuX_ic_prp is
receiving from ipuX_vdic.”…””}”(hj?  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MNhj   hžhubhÛ)”}”(hX°  Like the ipuX_csiY IDMAC source, this entity supports simple
interweaving without motion compensation. However, note that if the
ipuX_vdic is included in the pipeline (ipuX_ic_prp is receiving from
ipuX_vdic), it's not possible to use interweave in ipuX_ic_prpvf,
since the ipuX_vdic has already carried out de-interlacing (with
motion compensation) and therefore the field type output from
ipuX_vdic can only be none (progressive).”h]”hX²  Like the ipuX_csiY IDMAC source, this entity supports simple
interweaving without motion compensation. However, note that if the
ipuX_vdic is included in the pipeline (ipuX_ic_prp is receiving from
ipuX_vdic), itâ€™s not possible to use interweave in ipuX_ic_prpvf,
since the ipuX_vdic has already carried out de-interlacing (with
motion compensation) and therefore the field type output from
ipuX_vdic can only be none (progressive).”…””}”(hjM  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MShj   hžhubeh}”(h]”Œipux-ic-prpvf”ah ]”h"]”Œipux_ic_prpvf”ah$]”h&]”uh1h´hh¶hžhhŸh³h MGubhµ)”}”(hhh]”(hº)”}”(hŒCapture Pipelines”h]”hŒCapture Pipelines”…””}”(hjf  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjc  hžhhŸh³h M\ubhÛ)”}”(hŒHThe following describe the various use-cases supported by the pipelines.”h]”hŒHThe following describe the various use-cases supported by the pipelines.”…””}”(hjt  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M^hjc  hžhubhÛ)”}”(hŒÁThe links shown do not include the backend sensor, video mux, or mipi
csi-2 receiver links. This depends on the type of sensor interface
(parallel or mipi csi-2). So these pipelines begin with:”h]”hŒÁThe links shown do not include the backend sensor, video mux, or mipi
csi-2 receiver links. This depends on the type of sensor interface
(parallel or mipi csi-2). So these pipelines begin with:”…””}”(hj‚  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M`hjc  hžhubhÛ)”}”(hŒsensor -> ipuX_csiY_mux -> ...”h]”hŒsensor -> ipuX_csiY_mux -> ...”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mdhjc  hžhubhÛ)”}”(hŒfor parallel sensors, or:”h]”hŒfor parallel sensors, or:”…””}”(hjž  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mfhjc  hžhubhÛ)”}”(hŒ2sensor -> imx6-mipi-csi2 -> (ipuX_csiY_mux) -> ...”h]”hŒ2sensor -> imx6-mipi-csi2 -> (ipuX_csiY_mux) -> ...”…””}”(hj¬  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mhhjc  hžhubhÛ)”}”(hŒÛfor mipi csi-2 sensors. The imx6-mipi-csi2 receiver may need to route
to the video mux (ipuX_csiY_mux) before sending to the CSI, depending
on the mipi csi-2 virtual channel, hence ipuX_csiY_mux is shown in
parenthesis.”h]”hŒÛfor mipi csi-2 sensors. The imx6-mipi-csi2 receiver may need to route
to the video mux (ipuX_csiY_mux) before sending to the CSI, depending
on the mipi csi-2 virtual channel, hence ipuX_csiY_mux is shown in
parenthesis.”…””}”(hjº  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mjhjc  hžhubeh}”(h]”Œcapture-pipelines”ah ]”h"]”Œcapture pipelines”ah$]”h&]”uh1h´hh¶hžhhŸh³h M\ubhµ)”}”(hhh]”(hº)”}”(hŒUnprocessed Video Capture:”h]”hŒUnprocessed Video Capture:”…””}”(hjÓ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÐ  hžhhŸh³h MpubhÛ)”}”(hŒvSend frames directly from sensor to camera device interface node, with
no conversions, via ipuX_csiY IDMAC source pad:”h]”hŒvSend frames directly from sensor to camera device interface node, with
no conversions, via ipuX_csiY IDMAC source pad:”…””}”(hjá  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MrhjÐ  hžhubhÛ)”}”(hŒ#-> ipuX_csiY:2 -> ipuX_csiY capture”h]”hŒ#-> ipuX_csiY:2 -> ipuX_csiY capture”…””}”(hjï  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MuhjÐ  hžhubeh}”(h]”Œunprocessed-video-capture”ah ]”h"]”Œunprocessed video capture:”ah$]”h&]”uh1h´hh¶hžhhŸh³h Mpubhµ)”}”(hhh]”(hº)”}”(hŒIC Direct Conversions:”h]”hŒIC Direct Conversions:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj  hžhhŸh³h MxubhÛ)”}”(hŒ´This pipeline uses the preprocess encode entity to route frames directly
from the CSI to the IC, to carry out scaling up to 1024x1024 resolution,
CSC, flipping, and image rotation:”h]”hŒ´This pipeline uses the preprocess encode entity to route frames directly
from the CSI to the IC, to carry out scaling up to 1024x1024 resolution,
CSC, flipping, and image rotation:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mzhj  hžhubhÛ)”}”(hŒQ-> ipuX_csiY:1 -> 0:ipuX_ic_prp:1 -> 0:ipuX_ic_prpenc:1 -> ipuX_ic_prpenc capture”h]”hŒQ-> ipuX_csiY:1 -> 0:ipuX_ic_prp:1 -> 0:ipuX_ic_prpenc:1 -> ipuX_ic_prpenc capture”…””}”(hj$  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M~hj  hžhubeh}”(h]”Œic-direct-conversions”ah ]”h"]”Œic direct conversions:”ah$]”h&]”uh1h´hh¶hžhhŸh³h Mxubhµ)”}”(hhh]”(hº)”}”(hŒ Motion Compensated De-interlace:”h]”hŒ Motion Compensated De-interlace:”…””}”(hj=  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj:  hžhhŸh³h MubhÛ)”}”(hŒ¾This pipeline routes frames from the CSI direct pad to the VDIC entity to
support motion-compensated de-interlacing (high motion mode only),
scaling up to 1024x1024, CSC, flip, and rotation:”h]”hŒ¾This pipeline routes frames from the CSI direct pad to the VDIC entity to
support motion-compensated de-interlacing (high motion mode only),
scaling up to 1024x1024, CSC, flip, and rotation:”…””}”(hjK  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mƒhj:  hžhubhÛ)”}”(hŒ`-> ipuX_csiY:1 -> 0:ipuX_vdic:2 -> 0:ipuX_ic_prp:2 -> 0:ipuX_ic_prpvf:1 -> ipuX_ic_prpvf capture”h]”hŒ`-> ipuX_csiY:1 -> 0:ipuX_vdic:2 -> 0:ipuX_ic_prp:2 -> 0:ipuX_ic_prpvf:1 -> ipuX_ic_prpvf capture”…””}”(hjY  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M‡hj:  hžhubeh}”(h]”Œmotion-compensated-de-interlace”ah ]”h"]”Œ motion compensated de-interlace:”ah$]”h&]”uh1h´hh¶hžhhŸh³h Mubhµ)”}”(hhh]”(hº)”}”(hŒUsage Notes”h]”hŒUsage Notes”…””}”(hjr  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjo  hžhhŸh³h M‹ubhÛ)”}”(hX»  To aid in configuration and for backward compatibility with V4L2
applications that access controls only from video device nodes, the
capture device interfaces inherit controls from the active entities
in the current pipeline, so controls can be accessed either directly
from the subdev or from the active capture device interface. For
example, the FIM controls are available either from the ipuX_csiY
subdevs or from the active capture device.”h]”hX»  To aid in configuration and for backward compatibility with V4L2
applications that access controls only from video device nodes, the
capture device interfaces inherit controls from the active entities
in the current pipeline, so controls can be accessed either directly
from the subdev or from the active capture device interface. For
example, the FIM controls are available either from the ipuX_csiY
subdevs or from the active capture device.”…””}”(hj€  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mhjo  hžhubhÛ)”}”(hŒGThe following are specific usage notes for the Sabre* reference
boards:”h]”hŒGThe following are specific usage notes for the Sabre* reference
boards:”…””}”(hjŽ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M•hjo  hžhubeh}”(h]”Œusage-notes”ah ]”h"]”Œusage notes”ah$]”h&]”uh1h´hh¶hžhhŸh³h M‹ubhµ)”}”(hhh]”(hº)”}”(hŒ'i.MX6Q SabreLite with OV5642 and OV5640”h]”hŒ'i.MX6Q SabreLite with OV5642 and OV5640”…””}”(hj§  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj¤  hžhhŸh³h MšubhÛ)”}”(hŒºThis platform requires the OmniVision OV5642 module with a parallel
camera interface, and the OV5640 module with a MIPI CSI-2
interface. Both modules are available from Boundary Devices:”h]”hŒºThis platform requires the OmniVision OV5642 module with a parallel
camera interface, and the OV5640 module with a MIPI CSI-2
interface. Both modules are available from Boundary Devices:”…””}”(hjµ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mœhj¤  hžhubhù)”}”(hhh]”(hþ)”}”(hŒ-https://boundarydevices.com/product/nit6x_5mp”h]”hÛ)”}”(hjÈ  h]”hŒ	reference”“”)”}”(hjÈ  h]”hŒ-https://boundarydevices.com/product/nit6x_5mp”…””}”(hjÏ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jÈ  uh1jÍ  hjÊ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M hjÆ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhjÃ  hžhhŸh³h Nubhþ)”}”(hŒ3https://boundarydevices.com/product/nit6x_5mp_mipi
”h]”hÛ)”}”(hŒ2https://boundarydevices.com/product/nit6x_5mp_mipi”h]”jÎ  )”}”(hjï  h]”hŒ2https://boundarydevices.com/product/nit6x_5mp_mipi”…””}”(hjñ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jï  uh1jÍ  hjí  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M¡hjé  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhjÃ  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”j  j‘  uh1høhŸh³h M hj¤  hžhubhÛ)”}”(hŒkNote that if only one camera module is available, the other sensor
node can be disabled in the device tree.”h]”hŒkNote that if only one camera module is available, the other sensor
node can be disabled in the device tree.”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M£hj¤  hžhubhÛ)”}”(hŒ‰The OV5642 module is connected to the parallel bus input on the i.MX
internal video mux to IPU1 CSI0. It's i2c bus connects to i2c bus 2.”h]”hŒ‹The OV5642 module is connected to the parallel bus input on the i.MX
internal video mux to IPU1 CSI0. Itâ€™s i2c bus connects to i2c bus 2.”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M¦hj¤  hžhubhÛ)”}”(hX–  The MIPI CSI-2 OV5640 module is connected to the i.MX internal MIPI CSI-2
receiver, and the four virtual channel outputs from the receiver are
routed as follows: vc0 to the IPU1 CSI0 mux, vc1 directly to IPU1 CSI1,
vc2 directly to IPU2 CSI0, and vc3 to the IPU2 CSI1 mux. The OV5640 is
also connected to i2c bus 2 on the SabreLite, therefore the OV5642 and
OV5640 must not share the same i2c slave address.”h]”hX–  The MIPI CSI-2 OV5640 module is connected to the i.MX internal MIPI CSI-2
receiver, and the four virtual channel outputs from the receiver are
routed as follows: vc0 to the IPU1 CSI0 mux, vc1 directly to IPU1 CSI1,
vc2 directly to IPU2 CSI0, and vc3 to the IPU2 CSI1 mux. The OV5640 is
also connected to i2c bus 2 on the SabreLite, therefore the OV5642 and
OV5640 must not share the same i2c slave address.”…””}”(hj-	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M©hj¤  hžhubhÛ)”}”(hXX  The following basic example configures unprocessed video capture
pipelines for both sensors. The OV5642 is routed to ipu1_csi0, and
the OV5640, transmitting on MIPI CSI-2 virtual channel 1 (which is
imx6-mipi-csi2 pad 2), is routed to ipu1_csi1. Both sensors are
configured to output 640x480, and the OV5642 outputs YUYV2X8, the
OV5640 UYVY2X8:”h]”hXX  The following basic example configures unprocessed video capture
pipelines for both sensors. The OV5642 is routed to ipu1_csi0, and
the OV5640, transmitting on MIPI CSI-2 virtual channel 1 (which is
imx6-mipi-csi2 pad 2), is routed to ipu1_csi1. Both sensors are
configured to output 640x480, and the OV5642 outputs YUYV2X8, the
OV5640 UYVY2X8:”…””}”(hj;	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M°hj¤  hžhubj¯  )”}”(hXN  # Setup links for OV5642
media-ctl -l "'ov5642 1-0042':0 -> 'ipu1_csi0_mux':1[1]"
media-ctl -l "'ipu1_csi0_mux':2 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':2 -> 'ipu1_csi0 capture':0[1]"
# Setup links for OV5640
media-ctl -l "'ov5640 1-0040':0 -> 'imx6-mipi-csi2':0[1]"
media-ctl -l "'imx6-mipi-csi2':2 -> 'ipu1_csi1':0[1]"
media-ctl -l "'ipu1_csi1':2 -> 'ipu1_csi1 capture':0[1]"
# Configure pads for OV5642 pipeline
media-ctl -V "'ov5642 1-0042':0 [fmt:YUYV2X8/640x480 field:none]"
media-ctl -V "'ipu1_csi0_mux':2 [fmt:YUYV2X8/640x480 field:none]"
media-ctl -V "'ipu1_csi0':2 [fmt:AYUV32/640x480 field:none]"
# Configure pads for OV5640 pipeline
media-ctl -V "'ov5640 1-0040':0 [fmt:UYVY2X8/640x480 field:none]"
media-ctl -V "'imx6-mipi-csi2':2 [fmt:UYVY2X8/640x480 field:none]"
media-ctl -V "'ipu1_csi1':2 [fmt:AYUV32/640x480 field:none]"”h]”hXN  # Setup links for OV5642
media-ctl -l "'ov5642 1-0042':0 -> 'ipu1_csi0_mux':1[1]"
media-ctl -l "'ipu1_csi0_mux':2 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':2 -> 'ipu1_csi0 capture':0[1]"
# Setup links for OV5640
media-ctl -l "'ov5640 1-0040':0 -> 'imx6-mipi-csi2':0[1]"
media-ctl -l "'imx6-mipi-csi2':2 -> 'ipu1_csi1':0[1]"
media-ctl -l "'ipu1_csi1':2 -> 'ipu1_csi1 capture':0[1]"
# Configure pads for OV5642 pipeline
media-ctl -V "'ov5642 1-0042':0 [fmt:YUYV2X8/640x480 field:none]"
media-ctl -V "'ipu1_csi0_mux':2 [fmt:YUYV2X8/640x480 field:none]"
media-ctl -V "'ipu1_csi0':2 [fmt:AYUV32/640x480 field:none]"
# Configure pads for OV5640 pipeline
media-ctl -V "'ov5640 1-0040':0 [fmt:UYVY2X8/640x480 field:none]"
media-ctl -V "'imx6-mipi-csi2':2 [fmt:UYVY2X8/640x480 field:none]"
media-ctl -V "'ipu1_csi1':2 [fmt:AYUV32/640x480 field:none]"”…””}”hjI	  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h M·hj¤  hžhubhÛ)”}”(hŒäStreaming can then begin independently on the capture device nodes
"ipu1_csi0 capture" and "ipu1_csi1 capture". The v4l2-ctl tool can
be used to select any supported YUV pixelformat on the capture device
nodes, including planar.”h]”hŒìStreaming can then begin independently on the capture device nodes
â€œipu1_csi0 captureâ€ and â€œipu1_csi1 captureâ€. The v4l2-ctl tool can
be used to select any supported YUV pixelformat on the capture device
nodes, including planar.”…””}”(hjY	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MÊhj¤  hžhubeh}”(h]”Œ'i-mx6q-sabrelite-with-ov5642-and-ov5640”ah ]”h"]”Œ'i.mx6q sabrelite with ov5642 and ov5640”ah$]”h&]”uh1h´hh¶hžhhŸh³h Mšubhµ)”}”(hhh]”(hº)”}”(hŒ%i.MX6Q SabreAuto with ADV7180 decoder”h]”hŒ%i.MX6Q SabreAuto with ADV7180 decoder”…””}”(hjr	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjo	  hžhhŸh³h MÐubhÛ)”}”(hŒ†On the i.MX6Q SabreAuto, an on-board ADV7180 SD decoder is connected to the
parallel bus input on the internal video mux to IPU1 CSI0.”h]”hŒ†On the i.MX6Q SabreAuto, an on-board ADV7180 SD decoder is connected to the
parallel bus input on the internal video mux to IPU1 CSI0.”…””}”(hj€	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MÒhjo	  hžhubhÛ)”}”(hX+  The following example configures a pipeline to capture from the ADV7180
video decoder, assuming NTSC 720x480 input signals, using simple
interweave (unconverted and without motion compensation). The adv7180
must output sequential or alternating fields (field type 'seq-bt' for
NTSC, or 'alternate'):”h]”hX3  The following example configures a pipeline to capture from the ADV7180
video decoder, assuming NTSC 720x480 input signals, using simple
interweave (unconverted and without motion compensation). The adv7180
must output sequential or alternating fields (field type â€˜seq-btâ€™ for
NTSC, or â€˜alternateâ€™):”…””}”(hjŽ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MÕhjo	  hžhubj¯  )”}”(hXè  # Setup links
media-ctl -l "'adv7180 3-0021':0 -> 'ipu1_csi0_mux':1[1]"
media-ctl -l "'ipu1_csi0_mux':2 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':2 -> 'ipu1_csi0 capture':0[1]"
# Configure pads
media-ctl -V "'adv7180 3-0021':0 [fmt:UYVY2X8/720x480 field:seq-bt]"
media-ctl -V "'ipu1_csi0_mux':2 [fmt:UYVY2X8/720x480]"
media-ctl -V "'ipu1_csi0':2 [fmt:AYUV32/720x480]"
# Configure "ipu1_csi0 capture" interface (assumed at /dev/video4)
v4l2-ctl -d4 --set-fmt-video=field=interlaced_bt”h]”hXè  # Setup links
media-ctl -l "'adv7180 3-0021':0 -> 'ipu1_csi0_mux':1[1]"
media-ctl -l "'ipu1_csi0_mux':2 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':2 -> 'ipu1_csi0 capture':0[1]"
# Configure pads
media-ctl -V "'adv7180 3-0021':0 [fmt:UYVY2X8/720x480 field:seq-bt]"
media-ctl -V "'ipu1_csi0_mux':2 [fmt:UYVY2X8/720x480]"
media-ctl -V "'ipu1_csi0':2 [fmt:AYUV32/720x480]"
# Configure "ipu1_csi0 capture" interface (assumed at /dev/video4)
v4l2-ctl -d4 --set-fmt-video=field=interlaced_bt”…””}”hjœ	  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h MÛhjo	  hžhubhÛ)”}”(hŒƒStreaming can then begin on /dev/video4. The v4l2-ctl tool can also be
used to select any supported YUV pixelformat on /dev/video4.”h]”hŒƒStreaming can then begin on /dev/video4. The v4l2-ctl tool can also be
used to select any supported YUV pixelformat on /dev/video4.”…””}”(hj¬	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mèhjo	  hžhubhÛ)”}”(hX  This example configures a pipeline to capture from the ADV7180
video decoder, assuming PAL 720x576 input signals, with Motion
Compensated de-interlacing. The adv7180 must output sequential or
alternating fields (field type 'seq-tb' for PAL, or 'alternate').”h]”hX	  This example configures a pipeline to capture from the ADV7180
video decoder, assuming PAL 720x576 input signals, with Motion
Compensated de-interlacing. The adv7180 must output sequential or
alternating fields (field type â€˜seq-tbâ€™ for PAL, or â€˜alternateâ€™).”…””}”(hjº	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mëhjo	  hžhubj¯  )”}”(hXC  # Setup links
media-ctl -l "'adv7180 3-0021':0 -> 'ipu1_csi0_mux':1[1]"
media-ctl -l "'ipu1_csi0_mux':2 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':1 -> 'ipu1_vdic':0[1]"
media-ctl -l "'ipu1_vdic':2 -> 'ipu1_ic_prp':0[1]"
media-ctl -l "'ipu1_ic_prp':2 -> 'ipu1_ic_prpvf':0[1]"
media-ctl -l "'ipu1_ic_prpvf':1 -> 'ipu1_ic_prpvf capture':0[1]"
# Configure pads
media-ctl -V "'adv7180 3-0021':0 [fmt:UYVY2X8/720x576 field:seq-tb]"
media-ctl -V "'ipu1_csi0_mux':2 [fmt:UYVY2X8/720x576]"
media-ctl -V "'ipu1_csi0':1 [fmt:AYUV32/720x576]"
media-ctl -V "'ipu1_vdic':2 [fmt:AYUV32/720x576 field:none]"
media-ctl -V "'ipu1_ic_prp':2 [fmt:AYUV32/720x576 field:none]"
media-ctl -V "'ipu1_ic_prpvf':1 [fmt:AYUV32/720x576 field:none]"
# Configure "ipu1_ic_prpvf capture" interface (assumed at /dev/video2)
v4l2-ctl -d2 --set-fmt-video=field=none”h]”hXC  # Setup links
media-ctl -l "'adv7180 3-0021':0 -> 'ipu1_csi0_mux':1[1]"
media-ctl -l "'ipu1_csi0_mux':2 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':1 -> 'ipu1_vdic':0[1]"
media-ctl -l "'ipu1_vdic':2 -> 'ipu1_ic_prp':0[1]"
media-ctl -l "'ipu1_ic_prp':2 -> 'ipu1_ic_prpvf':0[1]"
media-ctl -l "'ipu1_ic_prpvf':1 -> 'ipu1_ic_prpvf capture':0[1]"
# Configure pads
media-ctl -V "'adv7180 3-0021':0 [fmt:UYVY2X8/720x576 field:seq-tb]"
media-ctl -V "'ipu1_csi0_mux':2 [fmt:UYVY2X8/720x576]"
media-ctl -V "'ipu1_csi0':1 [fmt:AYUV32/720x576]"
media-ctl -V "'ipu1_vdic':2 [fmt:AYUV32/720x576 field:none]"
media-ctl -V "'ipu1_ic_prp':2 [fmt:AYUV32/720x576 field:none]"
media-ctl -V "'ipu1_ic_prpvf':1 [fmt:AYUV32/720x576 field:none]"
# Configure "ipu1_ic_prpvf capture" interface (assumed at /dev/video2)
v4l2-ctl -d2 --set-fmt-video=field=none”…””}”hjÈ	  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h Mðhjo	  hžhubhÛ)”}”(hŒƒStreaming can then begin on /dev/video2. The v4l2-ctl tool can also be
used to select any supported YUV pixelformat on /dev/video2.”h]”hŒƒStreaming can then begin on /dev/video2. The v4l2-ctl tool can also be
used to select any supported YUV pixelformat on /dev/video2.”…””}”(hjØ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mhjo	  hžhubhÛ)”}”(hŒ[This platform accepts Composite Video analog inputs to the ADV7180 on
Ain1 (connector J42).”h]”hŒ[This platform accepts Composite Video analog inputs to the ADV7180 on
Ain1 (connector J42).”…””}”(hjæ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mhjo	  hžhubeh}”(h]”Œ%i-mx6q-sabreauto-with-adv7180-decoder”ah ]”h"]”Œ%i.mx6q sabreauto with adv7180 decoder”ah$]”h&]”uh1h´hh¶hžhhŸh³h MÐubhµ)”}”(hhh]”(hº)”}”(hŒ&i.MX6DL SabreAuto with ADV7180 decoder”h]”hŒ&i.MX6DL SabreAuto with ADV7180 decoder”…””}”(hjÿ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjü	  hžhhŸh³h M
ubhÛ)”}”(hŒ‡On the i.MX6DL SabreAuto, an on-board ADV7180 SD decoder is connected to the
parallel bus input on the internal video mux to IPU1 CSI0.”h]”hŒ‡On the i.MX6DL SabreAuto, an on-board ADV7180 SD decoder is connected to the
parallel bus input on the internal video mux to IPU1 CSI0.”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mhjü	  hžhubhÛ)”}”(hX+  The following example configures a pipeline to capture from the ADV7180
video decoder, assuming NTSC 720x480 input signals, using simple
interweave (unconverted and without motion compensation). The adv7180
must output sequential or alternating fields (field type 'seq-bt' for
NTSC, or 'alternate'):”h]”hX3  The following example configures a pipeline to capture from the ADV7180
video decoder, assuming NTSC 720x480 input signals, using simple
interweave (unconverted and without motion compensation). The adv7180
must output sequential or alternating fields (field type â€˜seq-btâ€™ for
NTSC, or â€˜alternateâ€™):”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mhjü	  hžhubj¯  )”}”(hXè  # Setup links
media-ctl -l "'adv7180 4-0021':0 -> 'ipu1_csi0_mux':4[1]"
media-ctl -l "'ipu1_csi0_mux':5 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':2 -> 'ipu1_csi0 capture':0[1]"
# Configure pads
media-ctl -V "'adv7180 4-0021':0 [fmt:UYVY2X8/720x480 field:seq-bt]"
media-ctl -V "'ipu1_csi0_mux':5 [fmt:UYVY2X8/720x480]"
media-ctl -V "'ipu1_csi0':2 [fmt:AYUV32/720x480]"
# Configure "ipu1_csi0 capture" interface (assumed at /dev/video0)
v4l2-ctl -d0 --set-fmt-video=field=interlaced_bt”h]”hXè  # Setup links
media-ctl -l "'adv7180 4-0021':0 -> 'ipu1_csi0_mux':4[1]"
media-ctl -l "'ipu1_csi0_mux':5 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':2 -> 'ipu1_csi0 capture':0[1]"
# Configure pads
media-ctl -V "'adv7180 4-0021':0 [fmt:UYVY2X8/720x480 field:seq-bt]"
media-ctl -V "'ipu1_csi0_mux':5 [fmt:UYVY2X8/720x480]"
media-ctl -V "'ipu1_csi0':2 [fmt:AYUV32/720x480]"
# Configure "ipu1_csi0 capture" interface (assumed at /dev/video0)
v4l2-ctl -d0 --set-fmt-video=field=interlaced_bt”…””}”hj)
  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h Mhjü	  hžhubhÛ)”}”(hŒƒStreaming can then begin on /dev/video0. The v4l2-ctl tool can also be
used to select any supported YUV pixelformat on /dev/video0.”h]”hŒƒStreaming can then begin on /dev/video0. The v4l2-ctl tool can also be
used to select any supported YUV pixelformat on /dev/video0.”…””}”(hj9
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M"hjü	  hžhubhÛ)”}”(hX  This example configures a pipeline to capture from the ADV7180
video decoder, assuming PAL 720x576 input signals, with Motion
Compensated de-interlacing. The adv7180 must output sequential or
alternating fields (field type 'seq-tb' for PAL, or 'alternate').”h]”hX	  This example configures a pipeline to capture from the ADV7180
video decoder, assuming PAL 720x576 input signals, with Motion
Compensated de-interlacing. The adv7180 must output sequential or
alternating fields (field type â€˜seq-tbâ€™ for PAL, or â€˜alternateâ€™).”…””}”(hjG
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M%hjü	  hžhubj¯  )”}”(hXC  # Setup links
media-ctl -l "'adv7180 4-0021':0 -> 'ipu1_csi0_mux':4[1]"
media-ctl -l "'ipu1_csi0_mux':5 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':1 -> 'ipu1_vdic':0[1]"
media-ctl -l "'ipu1_vdic':2 -> 'ipu1_ic_prp':0[1]"
media-ctl -l "'ipu1_ic_prp':2 -> 'ipu1_ic_prpvf':0[1]"
media-ctl -l "'ipu1_ic_prpvf':1 -> 'ipu1_ic_prpvf capture':0[1]"
# Configure pads
media-ctl -V "'adv7180 4-0021':0 [fmt:UYVY2X8/720x576 field:seq-tb]"
media-ctl -V "'ipu1_csi0_mux':5 [fmt:UYVY2X8/720x576]"
media-ctl -V "'ipu1_csi0':1 [fmt:AYUV32/720x576]"
media-ctl -V "'ipu1_vdic':2 [fmt:AYUV32/720x576 field:none]"
media-ctl -V "'ipu1_ic_prp':2 [fmt:AYUV32/720x576 field:none]"
media-ctl -V "'ipu1_ic_prpvf':1 [fmt:AYUV32/720x576 field:none]"
# Configure "ipu1_ic_prpvf capture" interface (assumed at /dev/video2)
v4l2-ctl -d2 --set-fmt-video=field=none”•†K      h]”hXC  # Setup links
media-ctl -l "'adv7180 4-0021':0 -> 'ipu1_csi0_mux':4[1]"
media-ctl -l "'ipu1_csi0_mux':5 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':1 -> 'ipu1_vdic':0[1]"
media-ctl -l "'ipu1_vdic':2 -> 'ipu1_ic_prp':0[1]"
media-ctl -l "'ipu1_ic_prp':2 -> 'ipu1_ic_prpvf':0[1]"
media-ctl -l "'ipu1_ic_prpvf':1 -> 'ipu1_ic_prpvf capture':0[1]"
# Configure pads
media-ctl -V "'adv7180 4-0021':0 [fmt:UYVY2X8/720x576 field:seq-tb]"
media-ctl -V "'ipu1_csi0_mux':5 [fmt:UYVY2X8/720x576]"
media-ctl -V "'ipu1_csi0':1 [fmt:AYUV32/720x576]"
media-ctl -V "'ipu1_vdic':2 [fmt:AYUV32/720x576 field:none]"
media-ctl -V "'ipu1_ic_prp':2 [fmt:AYUV32/720x576 field:none]"
media-ctl -V "'ipu1_ic_prpvf':1 [fmt:AYUV32/720x576 field:none]"
# Configure "ipu1_ic_prpvf capture" interface (assumed at /dev/video2)
v4l2-ctl -d2 --set-fmt-video=field=none”…””}”hjU
  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h M*hjü	  hžhubhÛ)”}”(hŒƒStreaming can then begin on /dev/video2. The v4l2-ctl tool can also be
used to select any supported YUV pixelformat on /dev/video2.”h]”hŒƒStreaming can then begin on /dev/video2. The v4l2-ctl tool can also be
used to select any supported YUV pixelformat on /dev/video2.”…””}”(hje
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M=hjü	  hžhubhÛ)”}”(hŒ[This platform accepts Composite Video analog inputs to the ADV7180 on
Ain1 (connector J42).”h]”hŒ[This platform accepts Composite Video analog inputs to the ADV7180 on
Ain1 (connector J42).”…””}”(hjs
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M@hjü	  hžhubeh}”(h]”Œ&i-mx6dl-sabreauto-with-adv7180-decoder”ah ]”h"]”Œ&i.mx6dl sabreauto with adv7180 decoder”ah$]”h&]”uh1h´hh¶hžhhŸh³h M
ubhµ)”}”(hhh]”(hº)”}”(hŒ%i.MX6Q SabreSD with MIPI CSI-2 OV5640”h]”hŒ%i.MX6Q SabreSD with MIPI CSI-2 OV5640”…””}”(hjŒ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj‰
  hžhhŸh³h MDubhÛ)”}”(hŒÉSimilarly to i.MX6Q SabreLite, the i.MX6Q SabreSD supports a parallel
interface OV5642 module on IPU1 CSI0, and a MIPI CSI-2 OV5640
module. The OV5642 connects to i2c bus 1 and the OV5640 to i2c bus 2.”h]”hŒÉSimilarly to i.MX6Q SabreLite, the i.MX6Q SabreSD supports a parallel
interface OV5642 module on IPU1 CSI0, and a MIPI CSI-2 OV5640
module. The OV5642 connects to i2c bus 1 and the OV5640 to i2c bus 2.”…””}”(hjš
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MFhj‰
  hžhubhÛ)”}”(hX]  The device tree for SabreSD includes OF graphs for both the parallel
OV5642 and the MIPI CSI-2 OV5640, but as of this writing only the MIPI
CSI-2 OV5640 has been tested, so the OV5642 node is currently disabled.
The OV5640 module connects to MIPI connector J5. The NXP part number
for the OV5640 module that connects to the SabreSD board is H120729.”h]”hX]  The device tree for SabreSD includes OF graphs for both the parallel
OV5642 and the MIPI CSI-2 OV5640, but as of this writing only the MIPI
CSI-2 OV5640 has been tested, so the OV5642 node is currently disabled.
The OV5640 module connects to MIPI connector J5. The NXP part number
for the OV5640 module that connects to the SabreSD board is H120729.”…””}”(hj¨
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MJhj‰
  hžhubhÛ)”}”(hŒThe following example configures unprocessed video capture pipeline to
capture from the OV5640, transmitting on MIPI CSI-2 virtual channel 0:”h]”hŒThe following example configures unprocessed video capture pipeline to
capture from the OV5640, transmitting on MIPI CSI-2 virtual channel 0:”…””}”(hj¶
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MPhj‰
  hžhubj¯  )”}”(hXØ  # Setup links
media-ctl -l "'ov5640 1-003c':0 -> 'imx6-mipi-csi2':0[1]"
media-ctl -l "'imx6-mipi-csi2':1 -> 'ipu1_csi0_mux':0[1]"
media-ctl -l "'ipu1_csi0_mux':2 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':2 -> 'ipu1_csi0 capture':0[1]"
# Configure pads
media-ctl -V "'ov5640 1-003c':0 [fmt:UYVY2X8/640x480]"
media-ctl -V "'imx6-mipi-csi2':1 [fmt:UYVY2X8/640x480]"
media-ctl -V "'ipu1_csi0_mux':0 [fmt:UYVY2X8/640x480]"
media-ctl -V "'ipu1_csi0':0 [fmt:AYUV32/640x480]"”h]”hXØ  # Setup links
media-ctl -l "'ov5640 1-003c':0 -> 'imx6-mipi-csi2':0[1]"
media-ctl -l "'imx6-mipi-csi2':1 -> 'ipu1_csi0_mux':0[1]"
media-ctl -l "'ipu1_csi0_mux':2 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':2 -> 'ipu1_csi0 capture':0[1]"
# Configure pads
media-ctl -V "'ov5640 1-003c':0 [fmt:UYVY2X8/640x480]"
media-ctl -V "'imx6-mipi-csi2':1 [fmt:UYVY2X8/640x480]"
media-ctl -V "'ipu1_csi0_mux':0 [fmt:UYVY2X8/640x480]"
media-ctl -V "'ipu1_csi0':0 [fmt:AYUV32/640x480]"”…””}”hjÄ
  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h MShj‰
  hžhubhÛ)”}”(hŒ“Streaming can then begin on "ipu1_csi0 capture" node. The v4l2-ctl
tool can be used to select any supported pixelformat on the capture
device node.”h]”hŒ—Streaming can then begin on â€œipu1_csi0 captureâ€ node. The v4l2-ctl
tool can be used to select any supported pixelformat on the capture
device node.”…””}”(hjÔ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M`hj‰
  hžhubhÛ)”}”(hŒNTo determine what is the /dev/video node correspondent to
"ipu1_csi0 capture":”h]”hŒRTo determine what is the /dev/video node correspondent to
â€œipu1_csi0 captureâ€:”…””}”(hjâ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mdhj‰
  hžhubj¯  )”}”(hŒ,media-ctl -e "ipu1_csi0 capture"
/dev/video0”h]”hŒ,media-ctl -e "ipu1_csi0 capture"
/dev/video0”…””}”hjð
  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h Mghj‰
  hžhubhÛ)”}”(hŒ2/dev/video0 is the streaming element in this case.”h]”hŒ2/dev/video0 is the streaming element in this case.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mlhj‰
  hžhubhÛ)”}”(hŒ$Starting the streaming via v4l2-ctl:”h]”hŒ$Starting the streaming via v4l2-ctl:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mnhj‰
  hžhubj¯  )”}”(hŒ%v4l2-ctl --stream-mmap -d /dev/video0”h]”hŒ%v4l2-ctl --stream-mmap -d /dev/video0”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h Mphj‰
  hžhubhÛ)”}”(hŒLStarting the streaming via Gstreamer and sending the content to the display:”h]”hŒLStarting the streaming via Gstreamer and sending the content to the display:”…””}”(hj,  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mthj‰
  hžhubj¯  )”}”(hŒ3gst-launch-1.0 v4l2src device=/dev/video0 ! kmssink”h]”hŒ3gst-launch-1.0 v4l2src device=/dev/video0 ! kmssink”…””}”hj:  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h Mvhj‰
  hžhubhÛ)”}”(hŒÅThe following example configures a direct conversion pipeline to capture
from the OV5640, transmitting on MIPI CSI-2 virtual channel 0. It also
shows colorspace conversion and scaling at IC output.”h]”hŒÅThe following example configures a direct conversion pipeline to capture
from the OV5640, transmitting on MIPI CSI-2 virtual channel 0. It also
shows colorspace conversion and scaling at IC output.”…””}”(hjJ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mzhj‰
  hžhubj¯  )”}”(hX   # Setup links
media-ctl -l "'ov5640 1-003c':0 -> 'imx6-mipi-csi2':0[1]"
media-ctl -l "'imx6-mipi-csi2':1 -> 'ipu1_csi0_mux':0[1]"
media-ctl -l "'ipu1_csi0_mux':2 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':1 -> 'ipu1_ic_prp':0[1]"
media-ctl -l "'ipu1_ic_prp':1 -> 'ipu1_ic_prpenc':0[1]"
media-ctl -l "'ipu1_ic_prpenc':1 -> 'ipu1_ic_prpenc capture':0[1]"
# Configure pads
media-ctl -V "'ov5640 1-003c':0 [fmt:UYVY2X8/640x480]"
media-ctl -V "'imx6-mipi-csi2':1 [fmt:UYVY2X8/640x480]"
media-ctl -V "'ipu1_csi0_mux':2 [fmt:UYVY2X8/640x480]"
media-ctl -V "'ipu1_csi0':1 [fmt:AYUV32/640x480]"
media-ctl -V "'ipu1_ic_prp':1 [fmt:AYUV32/640x480]"
media-ctl -V "'ipu1_ic_prpenc':1 [fmt:ARGB8888_1X32/800x600]"
# Set a format at the capture interface
v4l2-ctl -d /dev/video1 --set-fmt-video=pixelformat=RGB3”h]”hX   # Setup links
media-ctl -l "'ov5640 1-003c':0 -> 'imx6-mipi-csi2':0[1]"
media-ctl -l "'imx6-mipi-csi2':1 -> 'ipu1_csi0_mux':0[1]"
media-ctl -l "'ipu1_csi0_mux':2 -> 'ipu1_csi0':0[1]"
media-ctl -l "'ipu1_csi0':1 -> 'ipu1_ic_prp':0[1]"
media-ctl -l "'ipu1_ic_prp':1 -> 'ipu1_ic_prpenc':0[1]"
media-ctl -l "'ipu1_ic_prpenc':1 -> 'ipu1_ic_prpenc capture':0[1]"
# Configure pads
media-ctl -V "'ov5640 1-003c':0 [fmt:UYVY2X8/640x480]"
media-ctl -V "'imx6-mipi-csi2':1 [fmt:UYVY2X8/640x480]"
media-ctl -V "'ipu1_csi0_mux':2 [fmt:UYVY2X8/640x480]"
media-ctl -V "'ipu1_csi0':1 [fmt:AYUV32/640x480]"
media-ctl -V "'ipu1_ic_prp':1 [fmt:AYUV32/640x480]"
media-ctl -V "'ipu1_ic_prpenc':1 [fmt:ARGB8888_1X32/800x600]"
# Set a format at the capture interface
v4l2-ctl -d /dev/video1 --set-fmt-video=pixelformat=RGB3”…””}”hjX  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h M~hj‰
  hžhubhÛ)”}”(hŒ:Streaming can then begin on "ipu1_ic_prpenc capture" node.”h]”hŒ>Streaming can then begin on â€œipu1_ic_prpenc captureâ€ node.”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M‘hj‰
  hžhubhÛ)”}”(hŒSTo determine what is the /dev/video node correspondent to
"ipu1_ic_prpenc capture":”h]”hŒWTo determine what is the /dev/video node correspondent to
â€œipu1_ic_prpenc captureâ€:”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M“hj‰
  hžhubj¯  )”}”(hŒ1media-ctl -e "ipu1_ic_prpenc capture"
/dev/video1”h]”hŒ1media-ctl -e "ipu1_ic_prpenc capture"
/dev/video1”…””}”hj„  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h M–hj‰
  hžhubhÛ)”}”(hŒ2/dev/video1 is the streaming element in this case.”h]”hŒ2/dev/video1 is the streaming element in this case.”…””}”(hj”  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mœhj‰
  hžhubhÛ)”}”(hŒ$Starting the streaming via v4l2-ctl:”h]”hŒ$Starting the streaming via v4l2-ctl:”…””}”(hj¢  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Mžhj‰
  hžhubj¯  )”}”(hŒ%v4l2-ctl --stream-mmap -d /dev/video1”h]”hŒ%v4l2-ctl --stream-mmap -d /dev/video1”…””}”hj°  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h M hj‰
  hžhubhÛ)”}”(hŒLStarting the streaming via Gstreamer and sending the content to the display:”h]”hŒLStarting the streaming via Gstreamer and sending the content to the display:”…””}”(hjÀ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M¤hj‰
  hžhubj¯  )”}”(hŒ3gst-launch-1.0 v4l2src device=/dev/video1 ! kmssink”h]”hŒ3gst-launch-1.0 v4l2src device=/dev/video1 ! kmssink”…””}”hjÎ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²j¾  ‰j¿  Œnone”jÁ  }”uh1j®  hŸh³h M¦hj‰
  hžhubeh}”(h]”Œ%i-mx6q-sabresd-with-mipi-csi-2-ov5640”ah ]”h"]”Œ%i.mx6q sabresd with mipi csi-2 ov5640”ah$]”h&]”uh1h´hh¶hžhhŸh³h MDubhµ)”}”(hhh]”(hº)”}”(hŒKnown Issues”h]”hŒKnown Issues”…””}”(hjé  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjæ  hžhhŸh³h M«ubhŒenumerated_list”“”)”}”(hhh]”hþ)”}”(hXu  When using 90 or 270 degree rotation control at capture resolutions
near the IC resizer limit of 1024x1024, and combined with planar
pixel formats (YUV420, YUV422p), frame capture will often fail with
no end-of-frame interrupts from the IDMAC channel. To work around
this, use lower resolution and/or packed formats (YUYV, RGB3, etc.)
when 90 or 270 rotations are needed.

”h]”hÛ)”}”(hXs  When using 90 or 270 degree rotation control at capture resolutions
near the IC resizer limit of 1024x1024, and combined with planar
pixel formats (YUV420, YUV422p), frame capture will often fail with
no end-of-frame interrupts from the IDMAC channel. To work around
this, use lower resolution and/or packed formats (YUYV, RGB3, etc.)
when 90 or 270 rotations are needed.”h]”hXs  When using 90 or 270 degree rotation control at capture resolutions
near the IC resizer limit of 1024x1024, and combined with planar
pixel formats (YUV420, YUV422p), frame capture will often fail with
no end-of-frame interrupts from the IDMAC channel. To work around
this, use lower resolution and/or packed formats (YUYV, RGB3, etc.)
when 90 or 270 rotations are needed.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M­hjü  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhjù  hžhhŸh³h Nubah}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ.”uh1j÷  hjæ  hžhhŸh³h M­ubeh}”(h]”Œknown-issues”ah ]”h"]”Œknown issues”ah$]”h&]”uh1h´hh¶hžhhŸh³h M«ubhµ)”}”(hhh]”(hº)”}”(hŒ	File list”h]”hŒ	File list”…””}”(hj*  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj'  hžhhŸh³h M¶ubhÛ)”}”(hŒHdrivers/staging/media/imx/
include/media/imx.h
include/linux/imx-media.h”h]”hŒHdrivers/staging/media/imx/
include/media/imx.h
include/linux/imx-media.h”…””}”(hj8  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M¸hj'  hžhubeh}”(h]”Œ	file-list”ah ]”h"]”Œ	file list”ah$]”h&]”uh1h´hh¶hžhhŸh³h M¶ubhµ)”}”(hhh]”(hº)”}”(hŒ
References”h]”hŒ
References”…””}”(hjQ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjN  hžhhŸh³h M½ubhŒfootnote”“”)”}”(hŒJhttp://www.nxp.com/assets/documents/data/en/reference-manuals/IMX6DQRM.pdf”h]”(hŒlabel”“”)”}”(hhh]”hŒ1”…””}”(hjg  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1je  hja  hžhhŸNh NubhÛ)”}”(hjc  h]”jÎ  )”}”(hjc  h]”hŒJhttp://www.nxp.com/assets/documents/data/en/reference-manuals/IMX6DQRM.pdf”…””}”(hjw  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jc  uh1jÍ  hjt  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h M¿hja  ubeh}”(h]”jd  ah ]”h"]”Œf1”ah$]”h&]”j]  ajb  Kje  jf  uh1j_  hŸh³h M¿hjN  hžhubj`  )”}”(hŒMhttp://www.nxp.com/assets/documents/data/en/reference-manuals/IMX6SDLRM.pdf

”h]”(jf  )”}”(hhh]”hŒ2”…””}”(hj–  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1je  hj’  hžhhŸNh NubhÛ)”}”(hŒKhttp://www.nxp.com/assets/documents/data/en/reference-manuals/IMX6SDLRM.pdf”h]”jÎ  )”}”(hj¥  h]”hŒKhttp://www.nxp.com/assets/documents/data/en/reference-manuals/IMX6SDLRM.pdf”…””}”(hj§  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j¥  uh1jÍ  hj£  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MÀhj’  ubeh}”(h]”j{  ah ]”h"]”Œf2”ah$]”h&]”jv  ajb  Kje  jf  uh1j_  hŸh³h MÀhjN  hžhubeh}”(h]”Œ
references”ah ]”h"]”Œ
references”ah$]”h&]”uh1h´hh¶hžhhŸh³h M½ubhµ)”}”(hhh]”(hº)”}”(hŒAuthors”h]”hŒAuthors”…””}”(hjÍ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÊ  hžhhŸh³h MÄubhù)”}”(hhh]”(hþ)”}”(hŒ.Steve Longerbeam <steve_longerbeam@mentor.com>”h]”hÛ)”}”(hjà  h]”(hŒSteve Longerbeam <”…””}”(hjâ  hžhhŸNh NubjÎ  )”}”(hŒsteve_longerbeam@mentor.com”h]”hŒsteve_longerbeam@mentor.com”…””}”(hjé  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ"mailto:steve_longerbeam@mentor.com”uh1jÍ  hjâ  ubhŒ>”…””}”(hjâ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MÆhjÞ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhjÛ  hžhhŸh³h Nubhþ)”}”(hŒ%Philipp Zabel <kernel@pengutronix.de>”h]”hÛ)”}”(hj  h]”(hŒPhilipp Zabel <”…””}”(hj  hžhhŸNh NubjÎ  )”}”(hŒkernel@pengutronix.de”h]”hŒkernel@pengutronix.de”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:kernel@pengutronix.de”uh1jÍ  hj  ubhŒ>”…””}”(hj  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MÇhj	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhjÛ  hžhhŸh³h Nubhþ)”}”(hŒ%Russell King <linux@armlinux.org.uk>
”h]”hÛ)”}”(hŒ$Russell King <linux@armlinux.org.uk>”h]”(hŒRussell King <”…””}”(hj8  hžhhŸNh NubjÎ  )”}”(hŒlinux@armlinux.org.uk”h]”hŒlinux@armlinux.org.uk”…””}”(hj@  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:linux@armlinux.org.uk”uh1jÍ  hj8  ubhŒ>”…””}”(hj8  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MÈhj4  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hýhjÛ  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”j  j‘  uh1høhŸh³h MÆhjÊ  hžhubhÛ)”}”(hŒ,Copyright (C) 2012-2017 Mentor Graphics Inc.”h]”hŒ,Copyright (C) 2012-2017 Mentor Graphics Inc.”…””}”(hjf  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h MÊhjÊ  hžhubeh}”(h]”Œauthors”ah ]”h"]”Œauthors”ah$]”h&]”uh1h´hh¶hžhhŸh³h MÄubeh}”(h]”Œi-mx-video-capture-driver”ah ]”h"]”Œi.mx video capture driver”ah$]”h&]”uh1h´hhhžhhŸh³h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¹NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j§  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”(Œf1”]”jS  aŒf2”]”jl  auŒrefids”}”(jŸ  ]”j•  ajd  ]”jS  aj{  ]”jl  auŒnameids”}”(j  j~  j‹  jˆ  jc  j`  j  j  jÛ  jŸ  j1  j.  j‚  j  jÅ  jÂ  jb  j_  jÈ  jÅ  j  j
  jF  jC  j—  j”  jÚ  j×  j  j  j`  j]  jÍ  jÊ  j  jÿ  j7  j4  jl  ji  j¡  jž  jl	  ji	  jù	  jö	  j†
  jƒ
  jã  jà  j$  j!  jK  jH  jÇ  jÄ  j  jd  j¿  j{  jy  jv  uŒ	nametypes”}”(j  ‰j‹  ‰jc  ‰j  ‰jÛ  ˆj1  ‰j‚  ‰jÅ  ‰jb  ‰jÈ  ‰j  ‰jF  ‰j—  ‰jÚ  ‰j  ‰j`  ‰jÍ  ‰j  ‰j7  ‰jl  ‰j¡  ‰jl	  ‰jù	  ‰j†
  ‰jã  ‰j$  ‰jK  ‰jÇ  ‰j  ˆj¿  ˆjy  ‰uh}”(j~  h¶jˆ  hÉj]  jS  jv  jl  j`  jŽ  j  jf  jŸ  j£  j.  j  j  j4  jÂ  j…  j_  jÈ  jÅ  je  j
  jË  jC  j  j”  jI  j×  jš  j  jÝ  j]  j   jÊ  jc  jÿ  jÐ  j4  j  ji  j:  jž  jo  ji	  j¤  jö	  jo	  jƒ
  jü	  jà  j‰
  j!  jæ  jH  j'  jÄ  jN  jd  ja  j{  j’  jv  jÊ  jÐ  j¨  j  jå  uŒfootnote_refs”}”(jç  ]”jS  ajé  ]”jl  auŒcitation_refs”}”Œautofootnotes”]”(ja  j’  eŒautofootnote_refs”]”(jS  jl  eŒsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”jµ  Ks…”R”Œparse_messages”]”Œtransform_messages”]”hŒsystem_message”“”)”}”(hhh]”hÛ)”}”(hhh]”hŒ:Hyperlink target "imx6q-topology-graph" is not referenced.”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhj  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œsource”h³Œline”Kxuh1j  ubaŒtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.