Re: [PATCH v4 5/7] media: open.rst: Adjust some terms to match the glossary

From: Hans Verkuil
Date: Mon Aug 28 2017 - 05:37:24 EST


On 26/08/17 13:53, Mauro Carvalho Chehab wrote:
> As we now have a glossary, some terms used on open.rst
> require adjustments.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxxx>

Acked-by: Hans Verkuil <hans.verkuil@xxxxxxxxx>

Regards,

Hans

> ---
> Documentation/media/uapi/v4l/open.rst | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/media/uapi/v4l/open.rst b/Documentation/media/uapi/v4l/open.rst
> index 51acb8de8ba8..64b1de047b1b 100644
> --- a/Documentation/media/uapi/v4l/open.rst
> +++ b/Documentation/media/uapi/v4l/open.rst
> @@ -147,7 +147,7 @@ Related Devices
> Devices can support several functions. For example video capturing, VBI
> capturing and radio support.
>
> -The V4L2 API creates different nodes for each of these functions.
> +The V4L2 API creates different V4L2 device nodes for each of these functions.
>
> The V4L2 API was designed with the idea that one device node could
> support all functions. However, in practice this never worked: this
> @@ -157,17 +157,17 @@ switching a device node between different functions only works when
> using the streaming I/O API, not with the
> :ref:`read() <func-read>`/\ :ref:`write() <func-write>` API.
>
> -Today each device node supports just one function.
> +Today each V4L2 device node supports just one function.
>
> Besides video input or output the hardware may also support audio
> sampling or playback. If so, these functions are implemented as ALSA PCM
> devices with optional ALSA audio mixer devices.
>
> One problem with all these devices is that the V4L2 API makes no
> -provisions to find these related devices. Some really complex devices
> -use the Media Controller (see :ref:`media_controller`) which can be
> -used for this purpose. But most drivers do not use it, and while some
> -code exists that uses sysfs to discover related devices (see
> +provisions to find these related V4L2 device nodes. Some really complex
> +hardware use the Media Controller (see :ref:`media_controller`) which can
> +be used for this purpose. But several drivers do not use it, and while some
> +code exists that uses sysfs to discover related V4L2 device nodes (see
> libmedia_dev in the
> `v4l-utils <http://git.linuxtv.org/cgit.cgi/v4l-utils.git/>`__ git
> repository), there is no library yet that can provide a single API
>