Documentation: userspace-api/media: drop doubled words

    File descriptor returned by :ref:`open() <frontend_f_open>`.

``argp``

    pointer to struct struct

    :c:type:`dvb_frontend_info`

    pointer to struct :c:type:`dvb_frontend_info`

Description

:ref:`VIDIOC_QBUF <VIDIOC_QBUF>` and

:ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` ioctl. In the multi-planar API,

some plane-specific members of struct :c:type:`v4l2_buffer`,

such as pointers and sizes for each plane, are stored in struct

struct :c:type:`v4l2_plane` instead. In that case, struct

such as pointers and sizes for each plane, are stored in

struct :c:type:`v4l2_plane` instead. In that case,

struct :c:type:`v4l2_buffer` contains an array of plane structures.

Dequeued video buffers come with timestamps. The driver decides at which

``base`` field of struct :c:type:`v4l2_framebuffer`.

The framebuffer device ioctl ``FBIOGET_FSCREENINFO`` returns the same

address in the ``smem_start`` field of struct

struct :c:type:`fb_fix_screeninfo`. The ``FBIOGET_FSCREENINFO``

:c:type:`fb_fix_screeninfo`. The ``FBIOGET_FSCREENINFO``

ioctl and struct :c:type:`fb_fix_screeninfo` are defined in

the ``linux/fb.h`` header file.

``V4L2_BUF_TYPE_SDR_CAPTURE`` or ``V4L2_BUF_TYPE_SDR_OUTPUT`` and use

the struct :c:type:`v4l2_sdr_format` ``sdr`` member

of the ``fmt`` union as needed per the desired operation. Currently

there is two fields, ``pixelformat`` and ``buffersize``, of struct

there are two fields, ``pixelformat`` and ``buffersize``, of

struct :c:type:`v4l2_sdr_format` which are used.

Content of the ``pixelformat`` is V4L2 FourCC code of the data format.

The ``buffersize`` field is maximum buffer size in bytes required for

1998-09-28: Revamped video standard. Made video controls individually

enumerable.

1998-10-02: The ``id`` field was removed from struct

1998-10-02: The ``id`` field was removed from

struct ``video_standard`` and the color subcarrier fields were

renamed. The :ref:`VIDIOC_QUERYSTD` ioctl was

renamed to :ref:`VIDIOC_ENUMSTD`,

2000-09-18: ``V4L2_BUF_TYPE_VBI`` was added. This may *break

compatibility* as the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and

:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls may fail now if the struct

:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls may fail now if the

struct ``v4l2_fmt`` ``type`` field does not contain

``V4L2_BUF_TYPE_VBI``. In the documentation of the struct

:c:type:`v4l2_vbi_format` ``offset`` field the