Commit 9eb88a81 authored by Jordan Hand's avatar Jordan Hand Committed by Mauro Carvalho Chehab
Browse files

media: ipu3.rst: Format media-ctl and yavta commands as code blocks 



Fix improper line breaks and format all example yavta and media-ctl
commands as code blocks to improve readability.

Signed-off-by: default avatarJordan Hand <jorhand@linux.microsoft.com>
Signed-off-by: default avatarSakari Ailus <sakari.ailus@linux.intel.com>
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab+huawei@kernel.org>
parent 2110d00b

Documentation/admin-guide/media/ipu3.rst

+55 −49
Original line number Diff line number Diff line
@@ -89,12 +89,12 @@ Let us take the example of ov5670 sensor connected to CSI2 port 0, for a 
Using the media contorller APIs, the ov5670 sensor is configured to send

frames in packed raw Bayer format to IPU3 CSI2 receiver.



# This example assumes /dev/media0 as the CIO2 media device

.. code-block:: none



    # This example assumes /dev/media0 as the CIO2 media device

    export MDEV=/dev/media0



    # and that ov5670 sensor is connected to i2c bus 10 with address 0x36



    export SDEV=$(media-ctl -d $MDEV -e "ov5670 10-0036")



    # Establish the link for the media devices using media-ctl [#f3]_
@@ -102,9 +102,7 @@ media-ctl -d $MDEV -l "ov5670:0 -> ipu3-csi2 0:0[1]" 


    # Set the format for the media devices

    media-ctl -d $MDEV -V "ov5670:0 [fmt:SGRBG10/2592x1944]"



    media-ctl -d $MDEV -V "ipu3-csi2 0:0 [fmt:SGRBG10/2592x1944]"



    media-ctl -d $MDEV -V "ipu3-csi2 0:1 [fmt:SGRBG10/2592x1944]"



Once the media pipeline is configured, desired sensor specific settings
@@ -112,16 +110,18 @@ Once the media pipeline is configured, desired sensor specific settings 


e.g



yavta -w 0x009e0903 444 $SDEV

.. code-block:: none



    yavta -w 0x009e0903 444 $SDEV

    yavta -w 0x009e0913 1024 $SDEV



    yavta -w 0x009e0911 2046 $SDEV



Once the desired sensor settings are set, frame captures can be done as below.



e.g



.. code-block:: none



    yavta --data-prefix -u -c10 -n5 -I -s2592x1944 --file=/tmp/frame-#.bin \

          -f IPU3_SGRBG10 $(media-ctl -d $MDEV -e "ipu3-cio2 0")
@@ -269,20 +269,20 @@ all the video nodes setup correctly. 


Let us take "ipu3-imgu 0" subdev as an example.



media-ctl -d $MDEV -r

.. code-block:: none



    media-ctl -d $MDEV -r

    media-ctl -d $MDEV -l "ipu3-imgu 0 input":0 -> "ipu3-imgu 0":0[1]



    media-ctl -d $MDEV -l "ipu3-imgu 0":2 -> "ipu3-imgu 0 output":0[1]



    media-ctl -d $MDEV -l "ipu3-imgu 0":3 -> "ipu3-imgu 0 viewfinder":0[1]



    media-ctl -d $MDEV -l "ipu3-imgu 0":4 -> "ipu3-imgu 0 3a stat":0[1]



Also the pipe mode of the corresponding V4L2 subdev should be set as desired

(e.g 0 for video mode or 1 for still mode) through the control id 0x009819a1 as

below.



.. code-block:: none



    yavta -w "0x009819A1 1" /dev/v4l-subdev7



Certain hardware blocks in ImgU pipeline can change the frame resolution by
@@ -371,16 +371,18 @@ v4l2n command can be used. This helps process the raw Bayer frames and produces 
the desired results for the main output image and the viewfinder output, in NV12

format.



.. code-block:: none



    v4l2n --pipe=4 --load=/tmp/frame-#.bin --open=/dev/video4

--fmt=type:VIDEO_OUTPUT_MPLANE,width=2592,height=1944,pixelformat=0X47337069

--reqbufs=type:VIDEO_OUTPUT_MPLANE,count:1 --pipe=1 --output=/tmp/frames.out

--open=/dev/video5

--fmt=type:VIDEO_CAPTURE_MPLANE,width=2560,height=1920,pixelformat=NV12

--reqbufs=type:VIDEO_CAPTURE_MPLANE,count:1 --pipe=2 --output=/tmp/frames.vf

--open=/dev/video6

--fmt=type:VIDEO_CAPTURE_MPLANE,width=2560,height=1920,pixelformat=NV12

--reqbufs=type:VIDEO_CAPTURE_MPLANE,count:1 --pipe=3 --open=/dev/video7

--output=/tmp/frames.3A --fmt=type:META_CAPTURE,?

          --fmt=type:VIDEO_OUTPUT_MPLANE,width=2592,height=1944,pixelformat=0X47337069 \

          --reqbufs=type:VIDEO_OUTPUT_MPLANE,count:1 --pipe=1 \

          --output=/tmp/frames.out --open=/dev/video5 \

          --fmt=type:VIDEO_CAPTURE_MPLANE,width=2560,height=1920,pixelformat=NV12 \

          --reqbufs=type:VIDEO_CAPTURE_MPLANE,count:1 --pipe=2 \

          --output=/tmp/frames.vf --open=/dev/video6 \

          --fmt=type:VIDEO_CAPTURE_MPLANE,width=2560,height=1920,pixelformat=NV12 \

          --reqbufs=type:VIDEO_CAPTURE_MPLANE,count:1 --pipe=3 --open=/dev/video7 \

          --output=/tmp/frames.3A --fmt=type:META_CAPTURE,? \

          --reqbufs=count:1,type:META_CAPTURE --pipe=1,2,3,4 --stream=5



You can also use yavta [#f2]_ command to do same thing as above:
@@ -408,6 +410,8 @@ as below. 
Main output frames

~~~~~~~~~~~~~~~~~~



.. code-block:: none



    raw2pnm -x2560 -y1920 -fNV12 /tmp/frames.out /tmp/frames.out.ppm



where 2560x1920 is output resolution, NV12 is the video format, followed
@@ -416,6 +420,8 @@ by input frame and output PNM file. 
Viewfinder output frames

~~~~~~~~~~~~~~~~~~~~~~~~



.. code-block:: none



    raw2pnm -x2560 -y1920 -fNV12 /tmp/frames.vf /tmp/frames.vf.ppm



where 2560x1920 is output resolution, NV12 is the video format, followed