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
88    client may call :c:func:`VIDIOC_ENUM_FMT` on ``CAPTURE``.
93 2. To enumerate the set of supported raw formats, the client may call
103 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
116 4. The client may use :c:func:`VIDIOC_ENUM_FRAMEINTERVALS` to detect supported
137    ``CAPTURE``, if applicable, may be queried using their respective controls
140 6. Any additional encoder capabilities may be discovered by querying
157          desired size of ``CAPTURE`` buffers; the encoder may adjust it to
177       Changing the ``CAPTURE`` format may change the currently set ``OUTPUT``
221          may be adjusted to match encoder minimums, maximums and alignment
245 	 the desired frame interval; the encoder may adjust it to
259       ``OUTPUT`` queue is just a hint, the application may provide raw
296 	 the desired coded frame interval; the encoder may adjust it to
339          rectangle and may be subject to adjustment to match codec and
364             e.g.  the common 1920x1080 resolution may require the source
371       The encoder may adjust the crop/compose rectangles to the nearest
376    :c:func:`VIDIOC_REQBUFS`. This may be performed in any order.
397       The actual number of allocated buffers may differ from the ``count``
404       depth), the client may query the ``V4L2_CID_MIN_BUFFERS_FOR_OUTPUT``
429    :c:func:`VIDIOC_STREAMON`. This may be performed in any order. The actual
437    on the coded format, but may include the following implications:
455 format and may be affected by codec-specific extended controls, as stated
460 dequeued from the ``CAPTURE`` queue may differ from the order of queuing raw
468 * a buffer queued to ``OUTPUT`` may result in more than one buffer produced on
471   order; however, there may be other reasons for this as well),
473 * a buffer queued to ``OUTPUT`` may result in a buffer being produced on
478 * buffers may become available on the ``CAPTURE`` queue without additional
483 * buffers queued to ``OUTPUT`` may not become available to dequeue instantly
533 error code. The client may close the file handle and open a new one, or
545 per the standard semantics of the V4L2 control interface. The client may
548 configuration change to be allowed. To do this, it may follow the `Drain`
596         The last buffer may be empty (with :c:type:`v4l2_buffer`
665    Although not mandatory, the availability of encoder commands may be queried
671 The client may want to request the encoder to reinitialize the encoding, so
673 generated before. Depending on the coded format, that may imply that:
697 This sequence may be also used to change encoding parameters for encoders
706 1. Setting the format on the ``CAPTURE`` queue may change the set of formats
708    that the ``OUTPUT`` format may be reset and the client must not rely on the