diff options
author | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2016-07-01 13:42:29 -0300 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2016-07-01 14:54:10 -0300 |
commit | af4a4d0db8ab2c4e2088bc48cfa49511b766dca6 (patch) | |
tree | d2869d62845e58a1083ac808c7ebd78542ccac0a /Documentation/linux_tv/media/v4l/format.rst | |
parent | 789818845202ac243836b526e406fe8c97ec8cc2 (diff) |
doc-rst: linux_tv: Replace reference names to match ioctls
Due to a limitation at the DocBook language, the references
were using lowercase and slashes, instead of the name of the
ioctls. On ReST, make them identical. This will hopefully
help to cleanup the code a little bit.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'Documentation/linux_tv/media/v4l/format.rst')
-rw-r--r-- | Documentation/linux_tv/media/v4l/format.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/linux_tv/media/v4l/format.rst b/Documentation/linux_tv/media/v4l/format.rst index c1e30a64c833..a754fa81f707 100644 --- a/Documentation/linux_tv/media/v4l/format.rst +++ b/Documentation/linux_tv/media/v4l/format.rst @@ -23,9 +23,9 @@ current selection. A single mechanism exists to negotiate all data formats using the aggregate struct :ref:`v4l2_format <v4l2-format>` and the -:ref:`VIDIOC_G_FMT <vidioc-g-fmt>` and -:ref:`VIDIOC_S_FMT <vidioc-g-fmt>` ioctls. Additionally the -:ref:`VIDIOC_TRY_FMT <vidioc-g-fmt>` ioctl can be used to examine +:ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and +:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls. Additionally the +:ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to examine what the hardware *could* do, without actually selecting a new data format. The data formats supported by the V4L2 API are covered in the respective device section in :ref:`devices`. For a closer look at @@ -52,7 +52,7 @@ image size. When applications omit the ``VIDIOC_S_FMT`` ioctl its locking side effects are implied by the next step, the selection of an I/O method -with the :ref:`VIDIOC_REQBUFS <vidioc-reqbufs>` ioctl or implicit +with the :ref:`VIDIOC_REQBUFS <VIDIOC_REQBUFS>` ioctl or implicit with the first :ref:`read() <func-read>` or :ref:`write() <func-write>` call. @@ -75,7 +75,7 @@ Apart of the generic format negotiation functions a special ioctl to enumerate all image formats supported by video capture, overlay or output devices is available. [1]_ -The :ref:`VIDIOC_ENUM_FMT <vidioc-enum-fmt>` ioctl must be supported +The :ref:`VIDIOC_ENUM_FMT <VIDIOC_ENUM_FMT>` ioctl must be supported by all drivers exchanging image data with applications. **Important** |