Lines Matching refs: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
82 the order in which frames are decoded; may differ from display order if the
130 a point in the bytestream from which decoding may start/continue, without
218 client may call :c:func:`VIDIOC_ENUM_FMT` on ``OUTPUT``.
227 2. To enumerate the set of supported raw formats, the client may call
237 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
251 ``OUTPUT``, if applicable, may be queried using their respective controls
274 desired size of ``OUTPUT`` buffers; the decoder may adjust it to
296 Changing the ``OUTPUT`` format may change the currently set ``CAPTURE``
321 The actual number of allocated buffers may differ from the ``count``
349 The actual number of allocated buffers may differ from the ``count``
387 its own may attempt to set the width and height of the ``OUTPUT`` format
429 The value of ``pixelformat`` may be any pixel format supported by the
432 YUV format may be preferred over an RGB format if an additional
493 client may use this ioctl to discover which raw formats are supported for
501 may be supported by the decoder in general. In other words, the set
505 For example, a decoder may support YUV and RGB formats for resolutions
508 :c:func:`VIDIOC_ENUM_FMT` may return a set of YUV and RGB pixel formats,
513 discovering a resolution change within the same stream may switch
518 ``CAPTURE`` queue. The client may choose a different format than
531 what was returned with :c:func:`VIDIOC_G_FMT`, but it may be different
563 The decoder may adjust the compose rectangle to the nearest
567 6. If all the following conditions are met, the client may resume the decoding
575 requirement, the client may use :c:func:`VIDIOC_CREATE_BUFS` to add new
578 In that case, the remaining steps do not apply and the client may resume
588 memory usage or for any other reasons, it may be achieved by following
639 The actual number of allocated buffers may differ from the ``count``
646 depth), the client may query the ``V4L2_CID_MIN_BUFFERS_FOR_CAPTURE``
678 The actual number of allocated buffers may differ from the ``count``
694 The format obtained in the query may be then used with
709 format and may be affected by codec-specific extended controls, as stated in
714 frames dequeued from the ``CAPTURE`` queue may differ from the order of queuing
722 * a buffer queued to ``OUTPUT`` may result in no buffers being produced
726 * a buffer queued to ``OUTPUT`` may result in more than one buffer produced
731 * a buffer queued to ``OUTPUT`` may result in a buffer being produced on
736 * buffers may become available on the ``CAPTURE`` queue without additional
765 by the stream may be read by the hardware even after they are dequeued.
767 ``CAPTURE`` queue is streaming. Failure to observe this may result in
775 submitted under a different buffer ID, the driver may misidentify it and
779 During the decoding, the decoder may initiate one of the special sequences, as
808 error code. The client may close the file handle and open a new one, or
817 it may be affected as per normal decoder operation.
852 operation may result in an unspecified number of corrupted decoded frames
876 A seek may result in the `Dynamic Resolution Change` sequence being
887 The decoder may return a number of remaining ``CAPTURE`` buffers containing
893 queued before the seek sequence may have matching ``CAPTURE`` buffers
904 seek, the client may observe the timestamps to match the CAPTURE and OUTPUT
910 To achieve instantaneous seek, the client may restart streaming on the
916 Streams that include resolution metadata in the bytestream may require switching
957 The last buffer may be empty (with :c:type:`v4l2_buffer` ``bytesused``
1040 The last buffer may be empty (with :c:type:`v4l2_buffer`
1088 Although not mandatory, the availability of decoder commands may be queried
1104 1. Setting the format on the ``OUTPUT`` queue may change the set of formats
1106 that the ``CAPTURE`` format may be reset and the client must not rely on the