[media] Documentation: Fix V4L2_CTRL_FLAG_VOLATILE

V4L2_CTRL_FLAG_VOLATILE behaviour when V4L2_CTRL_FLAG_EXECUTE_ON_WRITE
is set was not properly explained.

Also set some hyperlink to ease the Documentation browsing.

Credit-to: Hans Verkuil <hansverk@cisco.com>

[mchehab@s-opensource.com: fix a trivial merge conflict]
Reported-by: Dimitrios Katsaros <patcherwork@gmail.com>
Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>

Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
This commit is contained in:
Ricardo Ribalda 2016-07-22 16:09:06 -03:00 committed by Mauro Carvalho Chehab
parent 3f8d56b022
commit f22bede313
1 changed files with 7 additions and 4 deletions

View File

@ -754,10 +754,12 @@ See also the examples in :ref:`control`.
.. note:: .. note::
Setting a new value for a volatile control will have no Setting a new value for a volatile control will be ignored
effect and no ``V4L2_EVENT_CTRL_CH_VALUE`` will be sent, unless unless
the ``V4L2_CTRL_FLAG_EXECUTE_ON_WRITE`` flag (see below) is :ref:`V4L2_CTRL_FLAG_EXECUTE_ON_WRITE <FLAG_EXECUTE_ON_WRITE>`
also set. Otherwise the new value will just be ignored. is also set.
Setting a new value for a volatile control will *never* trigger a
:ref:`V4L2_EVENT_CTRL_CH_VALUE <ctrl-changes-flags>` event.
- .. row 9 - .. row 9
@ -773,6 +775,7 @@ See also the examples in :ref:`control`.
payload of the control. payload of the control.
- .. row 10 - .. row 10
.. _FLAG_EXECUTE_ON_WRITE:
- ``V4L2_CTRL_FLAG_EXECUTE_ON_WRITE`` - ``V4L2_CTRL_FLAG_EXECUTE_ON_WRITE``