diff options
| author | Hans Verkuil <hverkuil-cisco@xs4all.nl> | 2019-04-23 10:05:09 -0400 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab+samsung@kernel.org> | 2019-05-08 14:01:57 -0400 |
| commit | 823a633eeb7775171cbb9f423401316504745dc7 (patch) | |
| tree | b4703a73ba61a5eead7ef05a79fa5f97a25dd8e6 | |
| parent | 16204b8a1c1af77725533b77936e6c73953486ae (diff) | |
media: field-order.rst: clarify FIELD_ANY and FIELD_NONE
Rephrased the FIELD_ANY description: rather than explicitly list
field values, just say 'when any field format is acceptable'. The
list of FIELD values was outdated, so it was a bit confusing.
The FIELD_NONE description said that 'The driver may also indicate
this order when it cannot distinguish between V4L2_FIELD_TOP and
V4L2_FIELD_BOTTOM'. This is false, NONE really means a full frame
and userspace depends on that. So drop this line completely. There
are no drivers that do this anyway.
FIELD_TOP/BOTTOM/ALTERNATE indicate that the number of lines in the
buffer are that of a field, not frame, so returning NONE here would
cause huge problems.
Finally attempt to clarify 'progressive' and 'interlaced' a little
bit.
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
| -rw-r--r-- | Documentation/media/uapi/v4l/field-order.rst | 16 |
1 files changed, 7 insertions, 9 deletions
diff --git a/Documentation/media/uapi/v4l/field-order.rst b/Documentation/media/uapi/v4l/field-order.rst index 3fb473e3b8e2..d640e922a974 100644 --- a/Documentation/media/uapi/v4l/field-order.rst +++ b/Documentation/media/uapi/v4l/field-order.rst | |||
| @@ -75,12 +75,11 @@ enum v4l2_field | |||
| 75 | 75 | ||
| 76 | * - ``V4L2_FIELD_ANY`` | 76 | * - ``V4L2_FIELD_ANY`` |
| 77 | - 0 | 77 | - 0 |
| 78 | - Applications request this field order when any one of the | 78 | - Applications request this field order when any field format |
| 79 | ``V4L2_FIELD_NONE``, ``V4L2_FIELD_TOP``, ``V4L2_FIELD_BOTTOM``, or | 79 | is acceptable. Drivers choose depending on hardware capabilities or |
| 80 | ``V4L2_FIELD_INTERLACED`` formats is acceptable. Drivers choose | 80 | e.g. the requested image size, and return the actual field order. |
| 81 | depending on hardware capabilities or e. g. the requested image | 81 | Drivers must never return ``V4L2_FIELD_ANY``. |
| 82 | size, and return the actual field order. Drivers must never return | 82 | If multiple field orders are possible the |
| 83 | ``V4L2_FIELD_ANY``. If multiple field orders are possible the | ||
| 84 | driver must choose one of the possible field orders during | 83 | driver must choose one of the possible field orders during |
| 85 | :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` or | 84 | :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` or |
| 86 | :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>`. struct | 85 | :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>`. struct |
| @@ -88,9 +87,8 @@ enum v4l2_field | |||
| 88 | ``V4L2_FIELD_ANY``. | 87 | ``V4L2_FIELD_ANY``. |
| 89 | * - ``V4L2_FIELD_NONE`` | 88 | * - ``V4L2_FIELD_NONE`` |
| 90 | - 1 | 89 | - 1 |
| 91 | - Images are in progressive format, not interlaced. The driver may | 90 | - Images are in progressive (frame-based) format, not interlaced |
| 92 | also indicate this order when it cannot distinguish between | 91 | (field-based). |
| 93 | ``V4L2_FIELD_TOP`` and ``V4L2_FIELD_BOTTOM``. | ||
| 94 | * - ``V4L2_FIELD_TOP`` | 92 | * - ``V4L2_FIELD_TOP`` |
| 95 | - 2 | 93 | - 2 |
| 96 | - Images consist of the top (aka odd) field only. | 94 | - Images consist of the top (aka odd) field only. |
