From: Steve Longerbeam <slongerbeam@gmail.com>
To: Fabio Estevam <festevam@gmail.com>, hverkuil-cisco@xs4all.nl
Cc: p.zabel@pengutronix.de, linux-media@vger.kernel.org
Subject: Re: [PATCH 4/4] media: imx.rst: Provide streaming examples for imx6q-sabresd
Date: Wed, 8 Apr 2020 09:42:29 -0700 [thread overview]
Message-ID: <fa7db6c5-5f76-7621-412f-97f67f48e303@gmail.com> (raw)
In-Reply-To: <20200408123215.2531-4-festevam@gmail.com>
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
> ------------
next prev parent reply other threads:[~2020-04-08 16:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 12:32 [PATCH 1/4] media: imx.rst: Fix the MIPI CSI-2 virtual channel Fabio Estevam
2020-04-08 12:32 ` [PATCH 2/4] media: imx.rst: Provide an example for unprocessed video capture Fabio Estevam
2020-04-08 16:37 ` Steve Longerbeam
2020-04-08 12:32 ` [PATCH 3/4] media: imx.rst: Provide the OV560 module part number Fabio Estevam
2020-04-08 16:37 ` Steve Longerbeam
2020-04-08 12:32 ` [PATCH 4/4] media: imx.rst: Provide streaming examples for imx6q-sabresd Fabio Estevam
2020-04-08 16:42 ` Steve Longerbeam [this message]
2020-04-08 16:35 ` [PATCH 1/4] media: imx.rst: Fix the MIPI CSI-2 virtual channel Steve Longerbeam
2020-04-08 17:24 ` Fabio Estevam
2020-04-08 19:16 ` Steve Longerbeam
2020-04-08 19:28 ` Fabio Estevam
2020-04-08 19:33 ` Fabio Estevam
2020-04-08 19:51 ` Steve Longerbeam
2020-04-08 20:04 ` Steve Longerbeam
2020-04-08 19:48 ` Steve Longerbeam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa7db6c5-5f76-7621-412f-97f67f48e303@gmail.com \
--to=slongerbeam@gmail.com \
--cc=festevam@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.