diff mbox series

[4/4] media: imx.rst: Provide streaming examples for imx6q-sabresd

Message ID 20200408123215.2531-4-festevam@gmail.com (mailing list archive)
State Superseded, archived
Delegated to: Hans Verkuil
Headers
Series [1/4] media: imx.rst: Fix the MIPI CSI-2 virtual channel |

Commit Message

Fabio Estevam April 8, 2020, 12:32 p.m. UTC 
  Improve the documentation by providing examples on how to test camera
capture on imx6q-sabresd via v4l2-ctl and Gstreamer. 

Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
 Documentation/media/v4l-drivers/imx.rst | 42 +++++++++++++++++++++++++
 1 file changed, 42 insertions(+)

Comments

Steve Longerbeam April 8, 2020, 4:42 p.m. UTC | #1 
On 4/8/20 5:32 AM, Fabio Estevam wrote:
> Improve the documentation by providing examples on how to test camera
> capture on imx6q-sabresd via v4l2-ctl and Gstreamer.
>
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
> ---
>   Documentation/media/v4l-drivers/imx.rst | 42 +++++++++++++++++++++++++
>   1 file changed, 42 insertions(+)
>
> diff --git a/Documentation/media/v4l-drivers/imx.rst b/Documentation/media/v4l-drivers/imx.rst
> index 37b944f12d93..c872cc84d9fc 100644
> --- a/Documentation/media/v4l-drivers/imx.rst
> +++ b/Documentation/media/v4l-drivers/imx.rst
> @@ -670,6 +670,28 @@ Streaming can then begin on "ipu1_ic_prpenc capture" node. The v4l2-ctl
>   tool can be used to select any supported YUV or RGB pixelformat on the
>   capture device node.
>   
> +In order to determine what is the /dev/video node correspondent to
> +"ipu1_ic_prpenc":
> +
> +.. code-block:: none
> +
> +   # dmesg | grep ipu1_ic_prpenc | grep Registered

A better way is to use "media-ctl -e":

# media-ctl -e "ipu1_ic_prpenc capture"
/dev/video1

Grepping from dmesg can fail when the log fills up and pushes out the 
boot "Registered ..." messages.

Steve

> +   ipu1_ic_prpenc: Registered ipu1_ic_prpenc capture as /dev/video1
> +
> +/dev/video1 is the streaming element in this case.
> +
> +Starting the streaming via v4l2-ctl:
> +
> +.. code-block:: none
> +
> +   v4l2-ctl --stream-mmap -d /dev/video1
> +
> +Starting the streaming via Gstreamer and sending the content to the display:
> +
> +.. code-block:: none
> +
> +   gst-launch-1.0 v4l2src device=/dev/video1 ! kmssink
> +
>   The following example configures unprocessed video capture pipeline to
>   capture from the OV5640, transmitting on MIPI CSI-2 virtual channel 0:
>   
> @@ -690,6 +712,26 @@ Streaming can then begin on "ipu1_csi0 capture" node. The v4l2-ctl
>   tool can be used to select any supported YUV or RGB pixelformat on the
>   capture device node.
>   
> +In order to determine what is the /dev/video node correspondent to "ipu1_csi0":
> +
> +.. code-block:: none
> +
> +   # dmesg | grep ipu1_csi0 | grep Registered
> +   ipu1_csi0: Registered ipu1_csi0 capture as /dev/video0
> +
> +/dev/video0 is the streaming element in this case.
> +
> +Starting the streaming via v4l2-ctl:
> +
> +.. code-block:: none
> +
> +   v4l2-ctl --stream-mmap -d /dev/video0
> +
> +Starting the streaming via Gstreamer and sending the content to the display:
> +
> +.. code-block:: none
> +
> +   gst-launch-1.0 v4l2src device=/dev/video0 ! kmssink
>   
>   Known Issues
>   ------------
diff mbox series

Patch

diff --git a/Documentation/media/v4l-drivers/imx.rst b/Documentation/media/v4l-drivers/imx.rst
index 37b944f12d93..c872cc84d9fc 100644
--- a/Documentation/media/v4l-drivers/imx.rst
+++ b/Documentation/media/v4l-drivers/imx.rst
@@ -670,6 +670,28 @@  Streaming can then begin on "ipu1_ic_prpenc capture" node. The v4l2-ctl
 tool can be used to select any supported YUV or RGB pixelformat on the
 capture device node.
 
+In order to determine what is the /dev/video node correspondent to
+"ipu1_ic_prpenc":
+
+.. code-block:: none
+
+   # dmesg | grep ipu1_ic_prpenc | grep Registered
+   ipu1_ic_prpenc: Registered ipu1_ic_prpenc capture as /dev/video1
+
+/dev/video1 is the streaming element in this case.
+
+Starting the streaming via v4l2-ctl:
+
+.. code-block:: none
+
+   v4l2-ctl --stream-mmap -d /dev/video1
+
+Starting the streaming via Gstreamer and sending the content to the display:
+
+.. code-block:: none
+
+   gst-launch-1.0 v4l2src device=/dev/video1 ! kmssink
+
 The following example configures unprocessed video capture pipeline to
 capture from the OV5640, transmitting on MIPI CSI-2 virtual channel 0:
 
@@ -690,6 +712,26 @@  Streaming can then begin on "ipu1_csi0 capture" node. The v4l2-ctl
 tool can be used to select any supported YUV or RGB pixelformat on the
 capture device node.
 
+In order to determine what is the /dev/video node correspondent to "ipu1_csi0":
+
+.. code-block:: none
+
+   # dmesg | grep ipu1_csi0 | grep Registered
+   ipu1_csi0: Registered ipu1_csi0 capture as /dev/video0
+
+/dev/video0 is the streaming element in this case.
+
+Starting the streaming via v4l2-ctl:
+
+.. code-block:: none
+
+   v4l2-ctl --stream-mmap -d /dev/video0
+
+Starting the streaming via Gstreamer and sending the content to the display:
+
+.. code-block:: none
+
+   gst-launch-1.0 v4l2src device=/dev/video0 ! kmssink
 
 Known Issues
 ------------