Lines Matching full:may
25 2. The meaning of words "must", "may", "should", etc. is as per `RFC
30 4. :c:func:`VIDIOC_G_EXT_CTRLS` and :c:func:`VIDIOC_S_EXT_CTRLS` may be used
34 5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
76 the order in which frames are decoded; may differ from display order if the
123 a point in the bytestream from which decoding may start/continue, without
211 client may call :c:func:`VIDIOC_ENUM_FMT` on ``OUTPUT``.
220 2. To enumerate the set of supported raw formats, the client may call
230 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
244 ``OUTPUT``, if applicable, may be queried using their respective controls
267 desired size of ``OUTPUT`` buffers; the decoder may adjust it to
289 Changing the ``OUTPUT`` format may change the currently set ``CAPTURE``
314 The actual number of allocated buffers may differ from the ``count``
342 The actual number of allocated buffers may differ from the ``count``
380 its own may attempt to set the width and height of the ``OUTPUT`` format
422 The value of ``pixelformat`` may be any pixel format supported by the
425 YUV format may be preferred over an RGB format if an additional
486 client may use this ioctl to discover which raw formats are supported for
494 may be supported by the decoder in general. In other words, the set
498 For example, a decoder may support YUV and RGB formats for resolutions
501 :c:func:`VIDIOC_ENUM_FMT` may return a set of YUV and RGB pixel formats,
506 discovering a resolution change within the same stream may switch
511 ``CAPTURE`` queue. The client may choose a different format than
524 what was returned with :c:func:`VIDIOC_G_FMT`, but it may be different
556 The decoder may adjust the compose rectangle to the nearest
560 6. If all the following conditions are met, the client may resume the decoding
568 requirement, the client may use :c:func:`VIDIOC_CREATE_BUFS` to add new
571 In that case, the remaining steps do not apply and the client may resume
581 memory usage or for any other reasons, it may be achieved by following
632 The actual number of allocated buffers may differ from the ``count``
639 depth), the client may query the ``V4L2_CID_MIN_BUFFERS_FOR_CAPTURE``
671 The actual number of allocated buffers may differ from the ``count``
687 The format obtained in the query may be then used with
702 format and may be affected by codec-specific extended controls, as stated in
707 frames dequeued from the ``CAPTURE`` queue may differ from the order of queuing
715 * a buffer queued to ``OUTPUT`` may result in no buffers being produced
719 * a buffer queued to ``OUTPUT`` may result in more than one buffer produced
724 * a buffer queued to ``OUTPUT`` may result in a buffer being produced on
729 * buffers may become available on the ``CAPTURE`` queue without additional
755 During the decoding, the decoder may initiate one of the special sequences, as
784 error code. The client may close the file handle and open a new one, or
793 it may be affected as per normal decoder operation.
828 operation may result in an unspecified number of corrupted decoded frames
852 A seek may result in the `Dynamic Resolution Change` sequence being
863 The decoder may return a number of remaining ``CAPTURE`` buffers containing
869 queued before the seek sequence may have matching ``CAPTURE`` buffers
880 seek, the client may observe the timestamps to match the CAPTURE and OUTPUT
886 To achieve instantaneous seek, the client may restart streaming on the
892 Streams that include resolution metadata in the bytestream may require switching
933 The last buffer may be empty (with :c:type:`v4l2_buffer` ``bytesused``
1016 The last buffer may be empty (with :c:type:`v4l2_buffer`
1064 Although not mandatory, the availability of decoder commands may be queried
1080 1. Setting the format on the ``OUTPUT`` queue may change the set of formats
1082 that the ``CAPTURE`` format may be reset and the client must not rely on the