← Documents Documentation/userspace-api/media/v4l/dev-decoder.rst GitHub 원문 ↗

Linux 6.18.37 · Userspace API / Media / V4L

메모리 대 메모리 상태 유지형 비디오 디코더 인터페이스

상태 유지형 decoder의 queue 모델, format 협상, decode·seek·해상도 변경·drain 상태 절차를 정의합니다.

Source pathDocumentation/userspace-api/media/v4l/dev-decoder.rst
Source versionLinux v6.18.37
TranslationDUJINLABS 전문 번역 + 해설

요약·해설과 원문, 전문 번역을 서로 분리했습니다. API 이름, symbol, source path는 원문 표기를 사용합니다.

1. 요약·해설

원문의 핵심 논리와 kernel programming 관점의 보충 설명입니다. 아래의 전문 번역과는 별도로 작성했습니다.

요약·해설

dev-decoder.rst:1-1127

상태 유지형 decoder에서는 OUTPUT이 encoded source와 format 협상을 지배하고 CAPTURE가 display order의 raw frame을 받습니다. 두 queue는 독립적이므로 event, LAST flag, timestamp와 상태 전이를 기준으로 동기화해야 합니다.

2. 영어 원문 전체

번역 기준이 된 Linux v6.18.37 원문입니다. 줄 번호는 이 버전의 파일 좌표입니다.

원문 전체 펼치기
1 .. SPDX-License-Identifier: GPL-2.0
2
3 .. _decoder:
4
5 *************************************************
6 Memory-to-Memory Stateful Video Decoder Interface
7 *************************************************
8
9 A stateful video decoder takes complete chunks of the bytestream (e.g. Annex-B
10 H.264/HEVC stream, raw VP8/9 stream) and decodes them into raw video frames in
11 display order. The decoder is expected not to require any additional information
12 from the client to process these buffers.
13
14 Performing software parsing, processing etc. of the stream in the driver in
15 order to support this interface is strongly discouraged. In case such
16 operations are needed, use of the Stateless Video Decoder Interface (in
17 development) is strongly advised.
18
19 Conventions and Notations Used in This Document
20 ===============================================
21
22 1. The general V4L2 API rules apply if not specified in this document
23 otherwise.
24
25 2. The meaning of words "must", "may", "should", etc. is as per `RFC
26 2119 <https://tools.ietf.org/html/rfc2119>`_.
27
28 3. All steps not marked "optional" are required.
29
30 4. :c:func:`VIDIOC_G_EXT_CTRLS` and :c:func:`VIDIOC_S_EXT_CTRLS` may be used
31 interchangeably with :c:func:`VIDIOC_G_CTRL` and :c:func:`VIDIOC_S_CTRL`,
32 unless specified otherwise.
33
34 5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
35 used interchangeably with multi-planar API, unless specified otherwise,
36 depending on decoder capabilities and following the general V4L2 guidelines.
37
38 6. i = [a..b]: sequence of integers from a to b, inclusive, i.e. i =
39 [0..2]: i = 0, 1, 2.
40
41 7. Given an ``OUTPUT`` buffer A, then A' represents a buffer on the ``CAPTURE``
42 queue containing data that resulted from processing buffer A.
43
44 .. _decoder-glossary:
45
46 Glossary
47 ========
48
49 CAPTURE
50 the destination buffer queue; for decoders, the queue of buffers containing
51 decoded frames; for encoders, the queue of buffers containing an encoded
52 bytestream; ``V4L2_BUF_TYPE_VIDEO_CAPTURE`` or
53 ``V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE``; data is captured from the hardware
54 into ``CAPTURE`` buffers.
55
56 client
57 the application communicating with the decoder or encoder implementing
58 this interface.
59
60 coded format
61 encoded/compressed video bytestream format (e.g. H.264, VP8, etc.); see
62 also: raw format.
63
64 coded height
65 height for given coded resolution.
66
67 coded resolution
68 stream resolution in pixels aligned to codec and hardware requirements;
69 typically visible resolution rounded up to full macroblocks;
70 see also: visible resolution.
71
72 coded width
73 width for given coded resolution.
74
75 coding tree unit
76 processing unit of the HEVC codec (corresponds to macroblock units in
77 H.264, VP8, VP9),
78 can use block structures of up to 64×64 pixels.
79 Good at sub-partitioning the picture into variable sized structures.
80
81 decode order
82 the order in which frames are decoded; may differ from display order if the
83 coded format includes a feature of frame reordering; for decoders,
84 ``OUTPUT`` buffers must be queued by the client in decode order; for
85 encoders ``CAPTURE`` buffers must be returned by the encoder in decode order.
86
87 destination
88 data resulting from the decode process; see ``CAPTURE``.
89
90 display order
91 the order in which frames must be displayed; for encoders, ``OUTPUT``
92 buffers must be queued by the client in display order; for decoders,
93 ``CAPTURE`` buffers must be returned by the decoder in display order.
94
95 DPB
96 Decoded Picture Buffer; an H.264/HEVC term for a buffer that stores a decoded
97 raw frame available for reference in further decoding steps.
98
99 EOS
100 end of stream.
101
102 IDR
103 Instantaneous Decoder Refresh; a type of a keyframe in an H.264/HEVC-encoded
104 stream, which clears the list of earlier reference frames (DPBs).
105
106 keyframe
107 an encoded frame that does not reference frames decoded earlier, i.e.
108 can be decoded fully on its own.
109
110 macroblock
111 a processing unit in image and video compression formats based on linear
112 block transforms (e.g. H.264, VP8, VP9); codec-specific, but for most of
113 popular codecs the size is 16x16 samples (pixels). The HEVC codec uses a
114 slightly more flexible processing unit called coding tree unit (CTU).
115
116 OUTPUT
117 the source buffer queue; for decoders, the queue of buffers containing
118 an encoded bytestream; for encoders, the queue of buffers containing raw
119 frames; ``V4L2_BUF_TYPE_VIDEO_OUTPUT`` or
120 ``V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE``; the hardware is fed with data
121 from ``OUTPUT`` buffers.
122
123 PPS
124 Picture Parameter Set; a type of metadata entity in an H.264/HEVC bytestream.
125
126 raw format
127 uncompressed format containing raw pixel data (e.g. YUV, RGB formats).
128
129 resume point
130 a point in the bytestream from which decoding may start/continue, without
131 any previous state/data present, e.g.: a keyframe (VP8/VP9) or
132 SPS/PPS/IDR sequence (H.264/HEVC); a resume point is required to start decode
133 of a new stream, or to resume decoding after a seek.
134
135 source
136 data fed to the decoder or encoder; see ``OUTPUT``.
137
138 source height
139 height in pixels for given source resolution; relevant to encoders only.
140
141 source resolution
142 resolution in pixels of source frames being source to the encoder and
143 subject to further cropping to the bounds of visible resolution; relevant to
144 encoders only.
145
146 source width
147 width in pixels for given source resolution; relevant to encoders only.
148
149 SPS
150 Sequence Parameter Set; a type of metadata entity in an H.264/HEVC bytestream.
151
152 stream metadata
153 additional (non-visual) information contained inside encoded bytestream;
154 for example: coded resolution, visible resolution, codec profile.
155
156 visible height
157 height for given visible resolution; display height.
158
159 visible resolution
160 stream resolution of the visible picture, in pixels, to be used for
161 display purposes; must be smaller or equal to coded resolution;
162 display resolution.
163
164 visible width
165 width for given visible resolution; display width.
166
167 State Machine
168 =============
169
170 .. kernel-render:: DOT
171 :alt: DOT digraph of decoder state machine
172 :caption: Decoder State Machine
173
174 digraph decoder_state_machine {
175 node [shape = doublecircle, label="Decoding"] Decoding;
176
177 node [shape = circle, label="Initialization"] Initialization;
178 node [shape = circle, label="Capture\nsetup"] CaptureSetup;
179 node [shape = circle, label="Dynamic\nResolution\nChange"] ResChange;
180 node [shape = circle, label="Stopped"] Stopped;
181 node [shape = circle, label="Drain"] Drain;
182 node [shape = circle, label="Seek"] Seek;
183 node [shape = circle, label="End of Stream"] EoS;
184
185 node [shape = point]; qi
186 qi -> Initialization [ label = "open()" ];
187
188 Initialization -> CaptureSetup [ label = "CAPTURE\nformat\nestablished" ];
189
190 CaptureSetup -> Stopped [ label = "CAPTURE\nbuffers\nready" ];
191
192 Decoding -> ResChange [ label = "Stream\nresolution\nchange" ];
193 Decoding -> Drain [ label = "V4L2_DEC_CMD_STOP" ];
194 Decoding -> EoS [ label = "EoS mark\nin the stream" ];
195 Decoding -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];
196 Decoding -> Stopped [ label = "VIDIOC_STREAMOFF(CAPTURE)" ];
197 Decoding -> Decoding;
198
199 ResChange -> CaptureSetup [ label = "CAPTURE\nformat\nestablished" ];
200 ResChange -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];
201
202 EoS -> Drain [ label = "Implicit\ndrain" ];
203
204 Drain -> Stopped [ label = "All CAPTURE\nbuffers dequeued\nor\nVIDIOC_STREAMOFF(CAPTURE)" ];
205 Drain -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];
206
207 Seek -> Decoding [ label = "VIDIOC_STREAMON(OUTPUT)" ];
208 Seek -> Initialization [ label = "VIDIOC_REQBUFS(OUTPUT, 0)" ];
209
210 Stopped -> Decoding [ label = "V4L2_DEC_CMD_START\nor\nVIDIOC_STREAMON(CAPTURE)" ];
211 Stopped -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];
212 }
213
214 Querying Capabilities
215 =====================
216
217 1. To enumerate the set of coded formats supported by the decoder, the
218 client may call :c:func:`VIDIOC_ENUM_FMT` on ``OUTPUT``.
219
220 * The full set of supported formats will be returned, regardless of the
221 format set on ``CAPTURE``.
222 * Check the flags field of :c:type:`v4l2_fmtdesc` for more information
223 about the decoder's capabilities with respect to each coded format.
224 In particular whether or not the decoder has a full-fledged bytestream
225 parser and if the decoder supports dynamic resolution changes.
226
227 2. To enumerate the set of supported raw formats, the client may call
228 :c:func:`VIDIOC_ENUM_FMT` on ``CAPTURE``.
229
230 * Only the formats supported for the format currently active on ``OUTPUT``
231 will be returned.
232
233 * In order to enumerate raw formats supported by a given coded format,
234 the client must first set that coded format on ``OUTPUT`` and then
235 enumerate formats on ``CAPTURE``.
236
237 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
238 resolutions for a given format, passing desired pixel format in
239 :c:type:`v4l2_frmsizeenum` ``pixel_format``.
240
241 * Values returned by :c:func:`VIDIOC_ENUM_FRAMESIZES` for a coded pixel
242 format will include all possible coded resolutions supported by the
243 decoder for given coded pixel format.
244
245 * Values returned by :c:func:`VIDIOC_ENUM_FRAMESIZES` for a raw pixel format
246 will include all possible frame buffer resolutions supported by the
247 decoder for given raw pixel format and the coded format currently set on
248 ``OUTPUT``.
249
250 4. Supported profiles and levels for the coded format currently set on
251 ``OUTPUT``, if applicable, may be queried using their respective controls
252 via :c:func:`VIDIOC_QUERYCTRL`.
253
254 Initialization
255 ==============
256
257 1. Set the coded format on ``OUTPUT`` via :c:func:`VIDIOC_S_FMT`.
258
259 * **Required fields:**
260
261 ``type``
262 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.
263
264 ``pixelformat``
265 a coded pixel format.
266
267 ``width``, ``height``
268 coded resolution of the stream; required only if it cannot be parsed
269 from the stream for the given coded format; otherwise the decoder will
270 use this resolution as a placeholder resolution that will likely change
271 as soon as it can parse the actual coded resolution from the stream.
272
273 ``sizeimage``
274 desired size of ``OUTPUT`` buffers; the decoder may adjust it to
275 match hardware requirements.
276
277 other fields
278 follow standard semantics.
279
280 * **Returned fields:**
281
282 ``sizeimage``
283 adjusted size of ``OUTPUT`` buffers.
284
285 * The ``CAPTURE`` format will be updated with an appropriate frame buffer
286 resolution instantly based on the width and height returned by
287 :c:func:`VIDIOC_S_FMT`.
288 However, for coded formats that include stream resolution information,
289 after the decoder is done parsing the information from the stream, it will
290 update the ``CAPTURE`` format with new values and signal a source change
291 event, regardless of whether they match the values set by the client or
292 not.
293
294 .. important::
295
296 Changing the ``OUTPUT`` format may change the currently set ``CAPTURE``
297 format. How the new ``CAPTURE`` format is determined is up to the decoder
298 and the client must ensure it matches its needs afterwards.
299
300 2. Allocate source (bytestream) buffers via :c:func:`VIDIOC_REQBUFS` on
301 ``OUTPUT``.
302
303 * **Required fields:**
304
305 ``count``
306 requested number of buffers to allocate; greater than zero.
307
308 ``type``
309 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.
310
311 ``memory``
312 follows standard semantics.
313
314 * **Returned fields:**
315
316 ``count``
317 the actual number of buffers allocated.
318
319 .. warning::
320
321 The actual number of allocated buffers may differ from the ``count``
322 given. The client must check the updated value of ``count`` after the
323 call returns.
324
325 Alternatively, :c:func:`VIDIOC_CREATE_BUFS` on the ``OUTPUT`` queue can be
326 used to have more control over buffer allocation.
327
328 * **Required fields:**
329
330 ``count``
331 requested number of buffers to allocate; greater than zero.
332
333 ``type``
334 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.
335
336 ``memory``
337 follows standard semantics.
338
339 ``format``
340 follows standard semantics.
341
342 * **Returned fields:**
343
344 ``count``
345 adjusted to the number of allocated buffers.
346
347 .. warning::
348
349 The actual number of allocated buffers may differ from the ``count``
350 given. The client must check the updated value of ``count`` after the
351 call returns.
352
353 3. Start streaming on the ``OUTPUT`` queue via :c:func:`VIDIOC_STREAMON`.
354
355 4. **This step only applies to coded formats that contain resolution information
356 in the stream.** Continue queuing/dequeuing bytestream buffers to/from the
357 ``OUTPUT`` queue via :c:func:`VIDIOC_QBUF` and :c:func:`VIDIOC_DQBUF`. The
358 buffers will be processed and returned to the client in order, until
359 required metadata to configure the ``CAPTURE`` queue are found. This is
360 indicated by the decoder sending a ``V4L2_EVENT_SOURCE_CHANGE`` event with
361 ``changes`` set to ``V4L2_EVENT_SRC_CH_RESOLUTION``.
362
363 * It is not an error if the first buffer does not contain enough data for
364 this to occur. Processing of the buffers will continue as long as more
365 data is needed.
366
367 * If data in a buffer that triggers the event is required to decode the
368 first frame, it will not be returned to the client, until the
369 initialization sequence completes and the frame is decoded.
370
371 * If the client has not set the coded resolution of the stream on its own,
372 calling :c:func:`VIDIOC_G_FMT`, :c:func:`VIDIOC_S_FMT`,
373 :c:func:`VIDIOC_TRY_FMT` or :c:func:`VIDIOC_REQBUFS` on the ``CAPTURE``
374 queue will not return the real values for the stream until a
375 ``V4L2_EVENT_SOURCE_CHANGE`` event with ``changes`` set to
376 ``V4L2_EVENT_SRC_CH_RESOLUTION`` is signaled.
377
378 .. important::
379
380 Any client query issued after the decoder queues the event will return
381 values applying to the just parsed stream, including queue formats,
382 selection rectangles and controls.
383
384 .. note::
385
386 A client capable of acquiring stream parameters from the bytestream on
387 its own may attempt to set the width and height of the ``OUTPUT`` format
388 to non-zero values matching the coded size of the stream, skip this step
389 and continue with the `Capture Setup` sequence. However, it must not
390 rely on any driver queries regarding stream parameters, such as
391 selection rectangles and controls, since the decoder has not parsed them
392 from the stream yet. If the values configured by the client do not match
393 those parsed by the decoder, a `Dynamic Resolution Change` will be
394 triggered to reconfigure them.
395
396 .. note::
397
398 No decoded frames are produced during this phase.
399
400 5. Continue with the `Capture Setup` sequence.
401
402 Capture Setup
403 =============
404
405 1. Call :c:func:`VIDIOC_G_FMT` on the ``CAPTURE`` queue to get format for the
406 destination buffers parsed/decoded from the bytestream.
407
408 * **Required fields:**
409
410 ``type``
411 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
412
413 * **Returned fields:**
414
415 ``width``, ``height``
416 frame buffer resolution for the decoded frames.
417
418 ``pixelformat``
419 pixel format for decoded frames.
420
421 ``num_planes`` (for _MPLANE ``type`` only)
422 number of planes for pixelformat.
423
424 ``sizeimage``, ``bytesperline``
425 as per standard semantics; matching frame buffer format.
426
427 .. note::
428
429 The value of ``pixelformat`` may be any pixel format supported by the
430 decoder for the current stream. The decoder should choose a
431 preferred/optimal format for the default configuration. For example, a
432 YUV format may be preferred over an RGB format if an additional
433 conversion step would be required for the latter.
434
435 2. **Optional.** Acquire the visible resolution via
436 :c:func:`VIDIOC_G_SELECTION`.
437
438 * **Required fields:**
439
440 ``type``
441 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
442
443 ``target``
444 set to ``V4L2_SEL_TGT_COMPOSE``.
445
446 * **Returned fields:**
447
448 ``r.left``, ``r.top``, ``r.width``, ``r.height``
449 the visible rectangle; it must fit within the frame buffer resolution
450 returned by :c:func:`VIDIOC_G_FMT` on ``CAPTURE``.
451
452 * The following selection targets are supported on ``CAPTURE``:
453
454 ``V4L2_SEL_TGT_CROP_BOUNDS``
455 corresponds to the coded resolution of the stream.
456
457 ``V4L2_SEL_TGT_CROP_DEFAULT``
458 the rectangle covering the part of the ``CAPTURE`` buffer that
459 contains meaningful picture data (visible area); width and height
460 will be equal to the visible resolution of the stream.
461
462 ``V4L2_SEL_TGT_CROP``
463 the rectangle within the coded resolution to be output to
464 ``CAPTURE``; defaults to ``V4L2_SEL_TGT_CROP_DEFAULT``; read-only on
465 hardware without additional compose/scaling capabilities.
466
467 ``V4L2_SEL_TGT_COMPOSE_BOUNDS``
468 the maximum rectangle within a ``CAPTURE`` buffer, which the cropped
469 frame can be composed into; equal to ``V4L2_SEL_TGT_CROP`` if the
470 hardware does not support compose/scaling.
471
472 ``V4L2_SEL_TGT_COMPOSE_DEFAULT``
473 equal to ``V4L2_SEL_TGT_CROP``.
474
475 ``V4L2_SEL_TGT_COMPOSE``
476 the rectangle inside a ``CAPTURE`` buffer into which the cropped
477 frame is written; defaults to ``V4L2_SEL_TGT_COMPOSE_DEFAULT``;
478 read-only on hardware without additional compose/scaling capabilities.
479
480 ``V4L2_SEL_TGT_COMPOSE_PADDED``
481 the rectangle inside a ``CAPTURE`` buffer which is overwritten by the
482 hardware; equal to ``V4L2_SEL_TGT_COMPOSE`` if the hardware does not
483 write padding pixels.
484
485 .. warning::
486
487 The values are guaranteed to be meaningful only after the decoder
488 successfully parses the stream metadata. The client must not rely on the
489 query before that happens.
490
491 3. **Optional.** Enumerate ``CAPTURE`` formats via :c:func:`VIDIOC_ENUM_FMT` on
492 the ``CAPTURE`` queue. Once the stream information is parsed and known, the
493 client may use this ioctl to discover which raw formats are supported for
494 given stream and select one of them via :c:func:`VIDIOC_S_FMT`.
495
496 .. important::
497
498 The decoder will return only formats supported for the currently
499 established coded format, as per the ``OUTPUT`` format and/or stream
500 metadata parsed in this initialization sequence, even if more formats
501 may be supported by the decoder in general. In other words, the set
502 returned will be a subset of the initial query mentioned in the
503 `Querying Capabilities` section.
504
505 For example, a decoder may support YUV and RGB formats for resolutions
506 1920x1088 and lower, but only YUV for higher resolutions (due to
507 hardware limitations). After parsing a resolution of 1920x1088 or lower,
508 :c:func:`VIDIOC_ENUM_FMT` may return a set of YUV and RGB pixel formats,
509 but after parsing resolution higher than 1920x1088, the decoder will not
510 return RGB, unsupported for this resolution.
511
512 However, subsequent resolution change event triggered after
513 discovering a resolution change within the same stream may switch
514 the stream into a lower resolution and :c:func:`VIDIOC_ENUM_FMT`
515 would return RGB formats again in that case.
516
517 4. **Optional.** Set the ``CAPTURE`` format via :c:func:`VIDIOC_S_FMT` on the
518 ``CAPTURE`` queue. The client may choose a different format than
519 selected/suggested by the decoder in :c:func:`VIDIOC_G_FMT`.
520
521 * **Required fields:**
522
523 ``type``
524 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
525
526 ``pixelformat``
527 a raw pixel format.
528
529 ``width``, ``height``
530 frame buffer resolution of the decoded stream; typically unchanged from
531 what was returned with :c:func:`VIDIOC_G_FMT`, but it may be different
532 if the hardware supports composition and/or scaling.
533
534 * Setting the ``CAPTURE`` format will reset the compose selection rectangles
535 to their default values, based on the new resolution, as described in the
536 previous step.
537
538 5. **Optional.** Set the compose rectangle via :c:func:`VIDIOC_S_SELECTION` on
539 the ``CAPTURE`` queue if it is desired and if the decoder has compose and/or
540 scaling capabilities.
541
542 * **Required fields:**
543
544 ``type``
545 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
546
547 ``target``
548 set to ``V4L2_SEL_TGT_COMPOSE``.
549
550 ``r.left``, ``r.top``, ``r.width``, ``r.height``
551 the rectangle inside a ``CAPTURE`` buffer into which the cropped
552 frame is written; defaults to ``V4L2_SEL_TGT_COMPOSE_DEFAULT``;
553 read-only on hardware without additional compose/scaling capabilities.
554
555 * **Returned fields:**
556
557 ``r.left``, ``r.top``, ``r.width``, ``r.height``
558 the visible rectangle; it must fit within the frame buffer resolution
559 returned by :c:func:`VIDIOC_G_FMT` on ``CAPTURE``.
560
561 .. warning::
562
563 The decoder may adjust the compose rectangle to the nearest
564 supported one to meet codec and hardware requirements. The client needs
565 to check the adjusted rectangle returned by :c:func:`VIDIOC_S_SELECTION`.
566
567 6. If all the following conditions are met, the client may resume the decoding
568 instantly:
569
570 * ``sizeimage`` of the new format (determined in previous steps) is less
571 than or equal to the size of currently allocated buffers,
572
573 * the number of buffers currently allocated is greater than or equal to the
574 minimum number of buffers acquired in previous steps. To fulfill this
575 requirement, the client may use :c:func:`VIDIOC_CREATE_BUFS` to add new
576 buffers.
577
578 In that case, the remaining steps do not apply and the client may resume
579 the decoding by one of the following actions:
580
581 * if the ``CAPTURE`` queue is streaming, call :c:func:`VIDIOC_DECODER_CMD`
582 with the ``V4L2_DEC_CMD_START`` command,
583
584 * if the ``CAPTURE`` queue is not streaming, call :c:func:`VIDIOC_STREAMON`
585 on the ``CAPTURE`` queue.
586
587 However, if the client intends to change the buffer set, to lower
588 memory usage or for any other reasons, it may be achieved by following
589 the steps below.
590
591 7. **If the** ``CAPTURE`` **queue is streaming,** keep queuing and dequeuing
592 buffers on the ``CAPTURE`` queue until a buffer marked with the
593 ``V4L2_BUF_FLAG_LAST`` flag is dequeued.
594
595 8. **If the** ``CAPTURE`` **queue is streaming,** call :c:func:`VIDIOC_STREAMOFF`
596 on the ``CAPTURE`` queue to stop streaming.
597
598 .. warning::
599
600 The ``OUTPUT`` queue must remain streaming. Calling
601 :c:func:`VIDIOC_STREAMOFF` on it would abort the sequence and trigger a
602 seek.
603
604 9. **If the** ``CAPTURE`` **queue has buffers allocated,** free the ``CAPTURE``
605 buffers using :c:func:`VIDIOC_REQBUFS`.
606
607 * **Required fields:**
608
609 ``count``
610 set to 0.
611
612 ``type``
613 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
614
615 ``memory``
616 follows standard semantics.
617
618 10. Allocate ``CAPTURE`` buffers via :c:func:`VIDIOC_REQBUFS` on the
619 ``CAPTURE`` queue.
620
621 * **Required fields:**
622
623 ``count``
624 requested number of buffers to allocate; greater than zero.
625
626 ``type``
627 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
628
629 ``memory``
630 follows standard semantics.
631
632 * **Returned fields:**
633
634 ``count``
635 actual number of buffers allocated.
636
637 .. warning::
638
639 The actual number of allocated buffers may differ from the ``count``
640 given. The client must check the updated value of ``count`` after the
641 call returns.
642
643 .. note::
644
645 To allocate more than the minimum number of buffers (for pipeline
646 depth), the client may query the ``V4L2_CID_MIN_BUFFERS_FOR_CAPTURE``
647 control to get the minimum number of buffers required, and pass the
648 obtained value plus the number of additional buffers needed in the
649 ``count`` field to :c:func:`VIDIOC_REQBUFS`.
650
651 Alternatively, :c:func:`VIDIOC_CREATE_BUFS` on the ``CAPTURE`` queue can be
652 used to have more control over buffer allocation. For example, by
653 allocating buffers larger than the current ``CAPTURE`` format, future
654 resolution changes can be accommodated.
655
656 * **Required fields:**
657
658 ``count``
659 requested number of buffers to allocate; greater than zero.
660
661 ``type``
662 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
663
664 ``memory``
665 follows standard semantics.
666
667 ``format``
668 a format representing the maximum framebuffer resolution to be
669 accommodated by newly allocated buffers.
670
671 * **Returned fields:**
672
673 ``count``
674 adjusted to the number of allocated buffers.
675
676 .. warning::
677
678 The actual number of allocated buffers may differ from the ``count``
679 given. The client must check the updated value of ``count`` after the
680 call returns.
681
682 .. note::
683
684 To allocate buffers for a format different than parsed from the stream
685 metadata, the client must proceed as follows, before the metadata
686 parsing is initiated:
687
688 * set width and height of the ``OUTPUT`` format to desired coded resolution to
689 let the decoder configure the ``CAPTURE`` format appropriately,
690
691 * query the ``CAPTURE`` format using :c:func:`VIDIOC_G_FMT` and save it
692 until this step.
693
694 The format obtained in the query may be then used with
695 :c:func:`VIDIOC_CREATE_BUFS` in this step to allocate the buffers.
696
697 11. Call :c:func:`VIDIOC_STREAMON` on the ``CAPTURE`` queue to start decoding
698 frames.
699
700 Decoding
701 ========
702
703 This state is reached after the `Capture Setup` sequence finishes successfully.
704 In this state, the client queues and dequeues buffers to both queues via
705 :c:func:`VIDIOC_QBUF` and :c:func:`VIDIOC_DQBUF`, following the standard
706 semantics.
707
708 The content of the source ``OUTPUT`` buffers depends on the active coded pixel
709 format and may be affected by codec-specific extended controls, as stated in
710 the documentation of each format.
711
712 Both queues operate independently, following the standard behavior of V4L2
713 buffer queues and memory-to-memory devices. In addition, the order of decoded
714 frames dequeued from the ``CAPTURE`` queue may differ from the order of queuing
715 coded frames to the ``OUTPUT`` queue, due to properties of the selected coded
716 format, e.g. frame reordering.
717
718 The client must not assume any direct relationship between ``CAPTURE``
719 and ``OUTPUT`` buffers and any specific timing of buffers becoming
720 available to dequeue. Specifically:
721
722 * a buffer queued to ``OUTPUT`` may result in no buffers being produced
723 on ``CAPTURE`` (e.g. if it does not contain encoded data, or if only
724 metadata syntax structures are present in it),
725
726 * a buffer queued to ``OUTPUT`` may result in more than one buffer produced
727 on ``CAPTURE`` (if the encoded data contained more than one frame, or if
728 returning a decoded frame allowed the decoder to return a frame that
729 preceded it in decode, but succeeded it in the display order),
730
731 * a buffer queued to ``OUTPUT`` may result in a buffer being produced on
732 ``CAPTURE`` later into decode process, and/or after processing further
733 ``OUTPUT`` buffers, or be returned out of order, e.g. if display
734 reordering is used,
735
736 * buffers may become available on the ``CAPTURE`` queue without additional
737 buffers queued to ``OUTPUT`` (e.g. during drain or ``EOS``), because of the
738 ``OUTPUT`` buffers queued in the past whose decoding results are only
739 available at later time, due to specifics of the decoding process.
740
741 .. note::
742
743 To allow matching decoded ``CAPTURE`` buffers with ``OUTPUT`` buffers they
744 originated from, the client can set the ``timestamp`` field of the
745 :c:type:`v4l2_buffer` struct when queuing an ``OUTPUT`` buffer. The
746 ``CAPTURE`` buffer(s), which resulted from decoding that ``OUTPUT`` buffer
747 will have their ``timestamp`` field set to the same value when dequeued.
748
749 In addition to the straightforward case of one ``OUTPUT`` buffer producing
750 one ``CAPTURE`` buffer, the following cases are defined:
751
752 * one ``OUTPUT`` buffer generates multiple ``CAPTURE`` buffers: the same
753 ``OUTPUT`` timestamp will be copied to multiple ``CAPTURE`` buffers.
754
755 * multiple ``OUTPUT`` buffers generate one ``CAPTURE`` buffer: timestamp of
756 the ``OUTPUT`` buffer queued first will be copied.
757
758 * the decoding order differs from the display order (i.e. the ``CAPTURE``
759 buffers are out-of-order compared to the ``OUTPUT`` buffers): ``CAPTURE``
760 timestamps will not retain the order of ``OUTPUT`` timestamps.
761
762 .. note::
763
764 The backing memory of ``CAPTURE`` buffers that are used as reference frames
765 by the stream may be read by the hardware even after they are dequeued.
766 Consequently, the client should avoid writing into this memory while the
767 ``CAPTURE`` queue is streaming. Failure to observe this may result in
768 corruption of decoded frames.
769
770 Similarly, when using a memory type other than ``V4L2_MEMORY_MMAP``, the
771 client should make sure that each ``CAPTURE`` buffer is always queued with
772 the same backing memory for as long as the ``CAPTURE`` queue is streaming.
773 The reason for this is that V4L2 buffer indices can be used by drivers to
774 identify frames. Thus, if the backing memory of a reference frame is
775 submitted under a different buffer ID, the driver may misidentify it and
776 decode a new frame into it while it is still in use, resulting in corruption
777 of the following frames.
778
779 During the decoding, the decoder may initiate one of the special sequences, as
780 listed below. The sequences will result in the decoder returning all the
781 ``CAPTURE`` buffers that originated from all the ``OUTPUT`` buffers processed
782 before the sequence started. Last of the buffers will have the
783 ``V4L2_BUF_FLAG_LAST`` flag set. To determine the sequence to follow, the client
784 must check if there is any pending event and:
785
786 * if a ``V4L2_EVENT_SOURCE_CHANGE`` event with ``changes`` set to
787 ``V4L2_EVENT_SRC_CH_RESOLUTION`` is pending, the `Dynamic Resolution
788 Change` sequence needs to be followed,
789
790 * if a ``V4L2_EVENT_EOS`` event is pending, the `End of Stream` sequence needs
791 to be followed.
792
793 Some of the sequences can be intermixed with each other and need to be handled
794 as they happen. The exact operation is documented for each sequence.
795
796 Should a decoding error occur, it will be reported to the client with the level
797 of details depending on the decoder capabilities. Specifically:
798
799 * the CAPTURE buffer that contains the results of the failed decode operation
800 will be returned with the V4L2_BUF_FLAG_ERROR flag set,
801
802 * if the decoder is able to precisely report the OUTPUT buffer that triggered
803 the error, such buffer will be returned with the V4L2_BUF_FLAG_ERROR flag
804 set.
805
806 In case of a fatal failure that does not allow the decoding to continue, any
807 further operations on corresponding decoder file handle will return the -EIO
808 error code. The client may close the file handle and open a new one, or
809 alternatively reinitialize the instance by stopping streaming on both queues,
810 releasing all buffers and performing the Initialization sequence again.
811
812 Seek
813 ====
814
815 Seek is controlled by the ``OUTPUT`` queue, as it is the source of coded data.
816 The seek does not require any specific operation on the ``CAPTURE`` queue, but
817 it may be affected as per normal decoder operation.
818
819 1. Stop the ``OUTPUT`` queue to begin the seek sequence via
820 :c:func:`VIDIOC_STREAMOFF`.
821
822 * **Required fields:**
823
824 ``type``
825 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.
826
827 * The decoder will drop all the pending ``OUTPUT`` buffers and they must be
828 treated as returned to the client (following standard semantics).
829
830 2. Restart the ``OUTPUT`` queue via :c:func:`VIDIOC_STREAMON`.
831
832 * **Required fields:**
833
834 ``type``
835 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.
836
837 * The decoder will start accepting new source bytestream buffers after the
838 call returns.
839
840 3. Start queuing buffers containing coded data after the seek to the ``OUTPUT``
841 queue until a suitable resume point is found.
842
843 .. note::
844
845 There is no requirement to begin queuing coded data starting exactly
846 from a resume point (e.g. SPS or a keyframe). Any queued ``OUTPUT``
847 buffers will be processed and returned to the client until a suitable
848 resume point is found. While looking for a resume point, the decoder
849 should not produce any decoded frames into ``CAPTURE`` buffers.
850
851 Some hardware is known to mishandle seeks to a non-resume point. Such an
852 operation may result in an unspecified number of corrupted decoded frames
853 being made available on the ``CAPTURE`` queue. Drivers must ensure that
854 no fatal decoding errors or crashes occur, and implement any necessary
855 handling and workarounds for hardware issues related to seek operations.
856
857 .. warning::
858
859 In case of the H.264/HEVC codec, the client must take care not to seek
860 over a change of SPS/PPS. Even though the target frame could be a
861 keyframe, the stale SPS/PPS inside decoder state would lead to undefined
862 results when decoding. Although the decoder must handle that case without
863 a crash or a fatal decode error, the client must not expect a sensible
864 decode output.
865
866 If the hardware can detect such corrupted decoded frames, then
867 corresponding buffers will be returned to the client with the
868 V4L2_BUF_FLAG_ERROR set. See the `Decoding` section for further
869 description of decode error reporting.
870
871 4. After a resume point is found, the decoder will start returning ``CAPTURE``
872 buffers containing decoded frames.
873
874 .. important::
875
876 A seek may result in the `Dynamic Resolution Change` sequence being
877 initiated, due to the seek target having decoding parameters different from
878 the part of the stream decoded before the seek. The sequence must be handled
879 as per normal decoder operation.
880
881 .. warning::
882
883 It is not specified when the ``CAPTURE`` queue starts producing buffers
884 containing decoded data from the ``OUTPUT`` buffers queued after the seek,
885 as it operates independently from the ``OUTPUT`` queue.
886
887 The decoder may return a number of remaining ``CAPTURE`` buffers containing
888 decoded frames originating from the ``OUTPUT`` buffers queued before the
889 seek sequence is performed.
890
891 The ``VIDIOC_STREAMOFF`` operation discards any remaining queued
892 ``OUTPUT`` buffers, which means that not all of the ``OUTPUT`` buffers
893 queued before the seek sequence may have matching ``CAPTURE`` buffers
894 produced. For example, given the sequence of operations on the
895 ``OUTPUT`` queue:
896
897 QBUF(A), QBUF(B), STREAMOFF(), STREAMON(), QBUF(G), QBUF(H),
898
899 any of the following results on the ``CAPTURE`` queue is allowed:
900
901 {A', B', G', H'}, {A', G', H'}, {G', H'}.
902
903 To determine the CAPTURE buffer containing the first decoded frame after the
904 seek, the client may observe the timestamps to match the CAPTURE and OUTPUT
905 buffers or use V4L2_DEC_CMD_STOP and V4L2_DEC_CMD_START to drain the
906 decoder.
907
908 .. note::
909
910 To achieve instantaneous seek, the client may restart streaming on the
911 ``CAPTURE`` queue too to discard decoded, but not yet dequeued buffers.
912
913 Dynamic Resolution Change
914 =========================
915
916 Streams that include resolution metadata in the bytestream may require switching
917 to a different resolution during the decoding.
918
919 .. note::
920
921 Not all decoders can detect resolution changes. Those that do set the
922 ``V4L2_FMT_FLAG_DYN_RESOLUTION`` flag for the coded format when
923 :c:func:`VIDIOC_ENUM_FMT` is called.
924
925 The sequence starts when the decoder detects a coded frame with one or more of
926 the following parameters different from those previously established (and
927 reflected by corresponding queries):
928
929 * coded resolution (``OUTPUT`` width and height),
930
931 * visible resolution (selection rectangles),
932
933 * the minimum number of buffers needed for decoding,
934
935 * bit-depth of the bitstream has been changed.
936
937 Whenever that happens, the decoder must proceed as follows:
938
939 1. After encountering a resolution change in the stream, the decoder sends a
940 ``V4L2_EVENT_SOURCE_CHANGE`` event with ``changes`` set to
941 ``V4L2_EVENT_SRC_CH_RESOLUTION``.
942
943 .. important::
944
945 Any client query issued after the decoder queues the event will return
946 values applying to the stream after the resolution change, including
947 queue formats, selection rectangles and controls.
948
949 2. The decoder will then process and decode all remaining buffers from before
950 the resolution change point.
951
952 * The last buffer from before the change must be marked with the
953 ``V4L2_BUF_FLAG_LAST`` flag, similarly to the `Drain` sequence above.
954
955 .. warning::
956
957 The last buffer may be empty (with :c:type:`v4l2_buffer` ``bytesused``
958 = 0) and in that case it must be ignored by the client, as it does not
959 contain a decoded frame.
960
961 .. note::
962
963 Any attempt to dequeue more ``CAPTURE`` buffers beyond the buffer marked
964 with ``V4L2_BUF_FLAG_LAST`` will result in a -EPIPE error from
965 :c:func:`VIDIOC_DQBUF`.
966
967 The client must continue the sequence as described below to continue the
968 decoding process.
969
970 1. Dequeue the source change event.
971
972 .. important::
973
974 A source change triggers an implicit decoder drain, similar to the
975 explicit `Drain` sequence. The decoder is stopped after it completes.
976 The decoding process must be resumed with either a pair of calls to
977 :c:func:`VIDIOC_STREAMOFF` and :c:func:`VIDIOC_STREAMON` on the
978 ``CAPTURE`` queue, or a call to :c:func:`VIDIOC_DECODER_CMD` with the
979 ``V4L2_DEC_CMD_START`` command.
980
981 2. Continue with the `Capture Setup` sequence.
982
983 .. note::
984
985 During the resolution change sequence, the ``OUTPUT`` queue must remain
986 streaming. Calling :c:func:`VIDIOC_STREAMOFF` on the ``OUTPUT`` queue would
987 abort the sequence and initiate a seek.
988
989 In principle, the ``OUTPUT`` queue operates separately from the ``CAPTURE``
990 queue and this remains true for the duration of the entire resolution change
991 sequence as well.
992
993 The client should, for best performance and simplicity, keep queuing/dequeuing
994 buffers to/from the ``OUTPUT`` queue even while processing this sequence.
995
996 Drain
997 =====
998
999 To ensure that all queued ``OUTPUT`` buffers have been processed and related
1000 ``CAPTURE`` buffers are given to the client, the client must follow the drain
1001 sequence described below. After the drain sequence ends, the client has
1002 received all decoded frames for all ``OUTPUT`` buffers queued before the
1003 sequence was started.
1005 1. Begin drain by issuing :c:func:`VIDIOC_DECODER_CMD`.
1007 * **Required fields:**
1009 ``cmd``
1010 set to ``V4L2_DEC_CMD_STOP``.
1012 ``flags``
1013 set to 0.
1015 ``pts``
1016 set to 0.
1018 .. warning::
1020 The sequence can be only initiated if both ``OUTPUT`` and ``CAPTURE``
1021 queues are streaming. For compatibility reasons, the call to
1022 :c:func:`VIDIOC_DECODER_CMD` will not fail even if any of the queues is
1023 not streaming, but at the same time it will not initiate the `Drain`
1024 sequence and so the steps described below would not be applicable.
1026 2. Any ``OUTPUT`` buffers queued by the client before the
1027 :c:func:`VIDIOC_DECODER_CMD` was issued will be processed and decoded as
1028 normal. The client must continue to handle both queues independently,
1029 similarly to normal decode operation. This includes:
1031 * handling any operations triggered as a result of processing those buffers,
1032 such as the `Dynamic Resolution Change` sequence, before continuing with
1033 the drain sequence,
1035 * queuing and dequeuing ``CAPTURE`` buffers, until a buffer marked with the
1036 ``V4L2_BUF_FLAG_LAST`` flag is dequeued,
1038 .. warning::
1040 The last buffer may be empty (with :c:type:`v4l2_buffer`
1041 ``bytesused`` = 0) and in that case it must be ignored by the client,
1042 as it does not contain a decoded frame.
1044 .. note::
1046 Any attempt to dequeue more ``CAPTURE`` buffers beyond the buffer
1047 marked with ``V4L2_BUF_FLAG_LAST`` will result in a -EPIPE error from
1048 :c:func:`VIDIOC_DQBUF`.
1050 * dequeuing processed ``OUTPUT`` buffers, until all the buffers queued
1051 before the ``V4L2_DEC_CMD_STOP`` command are dequeued,
1053 * dequeuing the ``V4L2_EVENT_EOS`` event, if the client subscribed to it.
1055 .. note::
1057 For backwards compatibility, the decoder will signal a ``V4L2_EVENT_EOS``
1058 event when the last frame has been decoded and all frames are ready to be
1059 dequeued. It is a deprecated behavior and the client must not rely on it.
1060 The ``V4L2_BUF_FLAG_LAST`` buffer flag should be used instead.
1062 3. Once all the ``OUTPUT`` buffers queued before the ``V4L2_DEC_CMD_STOP`` call
1063 are dequeued and the last ``CAPTURE`` buffer is dequeued, the decoder is
1064 stopped and it will accept, but not process, any newly queued ``OUTPUT``
1065 buffers until the client issues any of the following operations:
1067 * ``V4L2_DEC_CMD_START`` - the decoder will not be reset and will resume
1068 operation normally, with all the state from before the drain,
1070 * a pair of :c:func:`VIDIOC_STREAMOFF` and :c:func:`VIDIOC_STREAMON` on the
1071 ``CAPTURE`` queue - the decoder will resume the operation normally,
1072 however any ``CAPTURE`` buffers still in the queue will be returned to the
1073 client,
1075 * a pair of :c:func:`VIDIOC_STREAMOFF` and :c:func:`VIDIOC_STREAMON` on the
1076 ``OUTPUT`` queue - any pending source buffers will be returned to the
1077 client and the `Seek` sequence will be triggered.
1079 .. note::
1081 Once the drain sequence is initiated, the client needs to drive it to
1082 completion, as described by the steps above, unless it aborts the process by
1083 issuing :c:func:`VIDIOC_STREAMOFF` on any of the ``OUTPUT`` or ``CAPTURE``
1084 queues. The client is not allowed to issue ``V4L2_DEC_CMD_START`` or
1085 ``V4L2_DEC_CMD_STOP`` again while the drain sequence is in progress and they
1086 will fail with -EBUSY error code if attempted.
1088 Although not mandatory, the availability of decoder commands may be queried
1089 using :c:func:`VIDIOC_TRY_DECODER_CMD`.
1091 End of Stream
1092 =============
1094 If the decoder encounters an end of stream marking in the stream, the decoder
1095 will initiate the `Drain` sequence, which the client must handle as described
1096 above, skipping the initial :c:func:`VIDIOC_DECODER_CMD`.
1098 Commit Points
1099 =============
1101 Setting formats and allocating buffers trigger changes in the behavior of the
1102 decoder.
1104 1. Setting the format on the ``OUTPUT`` queue may change the set of formats
1105 supported/advertised on the ``CAPTURE`` queue. In particular, it also means
1106 that the ``CAPTURE`` format may be reset and the client must not rely on the
1107 previously set format being preserved.
1109 2. Enumerating formats on the ``CAPTURE`` queue always returns only formats
1110 supported for the current ``OUTPUT`` format.
1112 3. Setting the format on the ``CAPTURE`` queue does not change the list of
1113 formats available on the ``OUTPUT`` queue. An attempt to set a ``CAPTURE``
1114 format that is not supported for the currently selected ``OUTPUT`` format
1115 will result in the decoder adjusting the requested ``CAPTURE`` format to a
1116 supported one.
1118 4. Enumerating formats on the ``OUTPUT`` queue always returns the full set of
1119 supported coded formats, irrespectively of the current ``CAPTURE`` format.
1121 5. While buffers are allocated on any of the ``OUTPUT`` or ``CAPTURE`` queues,
1122 the client must not change the format on the ``OUTPUT`` queue. Drivers will
1123 return the -EBUSY error code for any such format change attempt.
1125 To summarize, setting formats and allocation must always start with the
1126 ``OUTPUT`` queue and the ``OUTPUT`` queue is the master that governs the
1127 set of supported formats for the ``CAPTURE`` queue.

3. 한국어 전문 번역

영어 원문의 문단 순서와 의미를 유지한 전체 번역입니다. 코드, 함수명, symbol과 URL은 원문 표기를 유지합니다.

상태 유지형 디코더와 문서 규칙

1-43

상태 유지형 비디오 디코더는 Annex-B H.264/HEVC stream이나 raw VP8/VP9 stream 같은 bytestream의 완전한 chunk를 받아 display order의 raw video frame으로 디코딩합니다. 디코더는 이 buffer들을 처리하기 위해 client로부터 추가 정보를 요구하지 않아야 합니다.

이 인터페이스를 지원하려고 드라이버 내부에서 stream을 software로 parsing하거나 처리하는 구현은 강하게 권장되지 않습니다. 그런 작업이 필요하다면 Stateless Video Decoder Interface를 사용하는 것이 바람직합니다.

이 문서에서 별도로 정하지 않은 사항에는 일반 V4L2 API 규칙이 적용되고, must·may·should 등의 의미는 RFC 2119를 따릅니다. optional로 표시하지 않은 단계는 모두 필수입니다.

별도 규정이 없으면 `VIDIOC_G_EXT_CTRLS`와 `VIDIOC_S_EXT_CTRLS`는 각각 `VIDIOC_G_CTRL`과 `VIDIOC_S_CTRL` 대신 사용할 수 있고 그 반대도 가능합니다.

문서의 표기 규칙
항목설명
일반 규칙별도 규정이 없으면 일반 V4L2 API 규칙 적용
규범 용어must, may, should 등은 RFC 2119 의미 사용
단계 의무optional 표시가 없는 모든 단계는 필수
Control ioctlG/S_EXT_CTRLS와 G/S_CTRL은 별도 규정이 없으면 상호 교환 가능
Planar APIdecoder capability와 일반 지침에 따라 single-planar와 multi-planar API를 교환 사용 가능
i = [a..b]a부터 b까지 양 끝을 포함하는 정수열
A와 A'OUTPUT buffer A를 처리해 생긴 데이터를 담는 CAPTURE buffer를 A'로 표기

ioctl, planar API와 buffer 대응 표기를 해석하는 기준입니다.

.. SPDX-License-Identifier: GPL-2.0

.. _decoder:

*************************************************
Memory-to-Memory Stateful Video Decoder Interface
*************************************************

A stateful video decoder takes complete chunks of the bytestream (e.g. Annex-B
H.264/HEVC stream, raw VP8/9 stream) and decodes them into raw video frames in
display order. The decoder is expected not to require any additional information
from the client to process these buffers.

Performing software parsing, processing etc. of the stream in the driver in
order to support this interface is strongly discouraged. In case such
operations are needed, use of the Stateless Video Decoder Interface (in
development) is strongly advised.

Conventions and Notations Used in This Document
===============================================

1. The general V4L2 API rules apply if not specified in this document
   otherwise.

2. The meaning of words "must", "may", "should", etc. is as per `RFC
   2119 <https://tools.ietf.org/html/rfc2119>`_.

3. All steps not marked "optional" are required.

4. :c:func:`VIDIOC_G_EXT_CTRLS` and :c:func:`VIDIOC_S_EXT_CTRLS` may be used
   interchangeably with :c:func:`VIDIOC_G_CTRL` and :c:func:`VIDIOC_S_CTRL`,
   unless specified otherwise.

5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
   used interchangeably with multi-planar API, unless specified otherwise,
   depending on decoder capabilities and following the general V4L2 guidelines.

6. i = [a..b]: sequence of integers from a to b, inclusive, i.e. i =
   [0..2]: i = 0, 1, 2.

7. Given an ``OUTPUT`` buffer A, then A' represents a buffer on the ``CAPTURE``
   queue containing data that resulted from processing buffer A.

디코더 용어

44-166

`OUTPUT`은 encoded bytestream을 하드웨어에 공급하는 source queue이고, `CAPTURE`는 디코딩된 raw frame을 하드웨어에서 받아 오는 destination queue입니다. encoder에서는 두 queue의 데이터 역할이 반대지만 V4L2 buffer type 이름은 같습니다.

coded resolution은 codec과 하드웨어 정렬 요구를 만족하는 stream 크기이며, 보통 visible resolution을 macroblock 또는 coding tree unit 경계까지 올림한 값입니다. visible resolution은 실제 표시할 picture 크기이므로 coded resolution보다 작거나 같아야 합니다.

decode order와 display order는 frame 재정렬을 사용하는 format에서 다를 수 있습니다. client는 decoder의 `OUTPUT` buffer를 decode order로 queue하고, decoder는 `CAPTURE` buffer를 display order로 반환합니다.

상태 유지형 codec 용어
항목설명
CAPTUREdestination buffer queue. decoder에서는 decoded frame, encoder에서는 encoded bytestream을 담음
client이 인터페이스를 구현한 decoder 또는 encoder와 통신하는 애플리케이션
coded formatH.264, VP8 같은 encoded/compressed video bytestream format
coded height주어진 coded resolution의 높이
coded resolutioncodec과 하드웨어 요구에 맞춰 정렬된 stream 해상도
coded width주어진 coded resolution의 폭
coding tree unitHEVC 처리 단위. 최대 64x64 pixel block과 가변 하위 분할을 사용
decode orderframe을 디코딩하는 순서. decoder OUTPUT은 이 순서로 queue
destinationdecode 결과 데이터, 즉 CAPTURE
display orderframe을 표시해야 하는 순서. decoder CAPTURE는 이 순서로 반환
DPBDecoded Picture Buffer. 이후 decode의 reference로 쓸 raw frame 저장소
EOSend of stream
IDR이전 reference frame 목록을 비우는 H.264/HEVC keyframe 종류
keyframe이전 decoded frame을 참조하지 않아 독립적으로 decode 가능한 encoded frame
macroblock선형 block 변환 codec의 처리 단위. 널리 쓰이는 codec에서는 보통 16x16 sample
OUTPUTsource buffer queue. decoder에서는 encoded bytestream을 하드웨어에 공급
PPSH.264/HEVC bytestream의 Picture Parameter Set metadata
raw formatYUV, RGB처럼 압축되지 않은 pixel data format
resume point이전 상태 없이 decode를 시작하거나 계속할 수 있는 keyframe 또는 SPS/PPS/IDR 지점
sourcedecoder 또는 encoder에 공급하는 데이터, 즉 OUTPUT
source heightencoder source resolution의 pixel 높이
source resolutionencoder에 공급되어 visible bounds로 crop될 source frame 해상도
source widthencoder source resolution의 pixel 폭
SPSH.264/HEVC bytestream의 Sequence Parameter Set metadata
stream metadatacoded/visible resolution, codec profile 같은 비시각적 bytestream 정보
visible heightvisible resolution의 표시 높이
visible resolution표시에 사용하는 visible picture 해상도. coded resolution 이하
visible widthvisible resolution의 표시 폭

원문 glossary의 모든 용어와 이 인터페이스에서의 의미입니다.

.. _decoder-glossary:

Glossary
========

CAPTURE
   the destination buffer queue; for decoders, the queue of buffers containing
   decoded frames; for encoders, the queue of buffers containing an encoded
   bytestream; ``V4L2_BUF_TYPE_VIDEO_CAPTURE`` or
   ``V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE``; data is captured from the hardware
   into ``CAPTURE`` buffers.

client
   the application communicating with the decoder or encoder implementing
   this interface.

coded format
   encoded/compressed video bytestream format (e.g. H.264, VP8, etc.); see
   also: raw format.

coded height
   height for given coded resolution.

coded resolution
   stream resolution in pixels aligned to codec and hardware requirements;
   typically visible resolution rounded up to full macroblocks;
   see also: visible resolution.

coded width
   width for given coded resolution.

coding tree unit
   processing unit of the HEVC codec (corresponds to macroblock units in
   H.264, VP8, VP9),
   can use block structures of up to 64×64 pixels.
   Good at sub-partitioning the picture into variable sized structures.

decode order
   the order in which frames are decoded; may differ from display order if the
   coded format includes a feature of frame reordering; for decoders,
   ``OUTPUT`` buffers must be queued by the client in decode order; for
   encoders ``CAPTURE`` buffers must be returned by the encoder in decode order.

destination
   data resulting from the decode process; see ``CAPTURE``.

display order
   the order in which frames must be displayed; for encoders, ``OUTPUT``
   buffers must be queued by the client in display order; for decoders,
   ``CAPTURE`` buffers must be returned by the decoder in display order.

DPB
   Decoded Picture Buffer; an H.264/HEVC term for a buffer that stores a decoded
   raw frame available for reference in further decoding steps.

EOS
   end of stream.

IDR
   Instantaneous Decoder Refresh; a type of a keyframe in an H.264/HEVC-encoded
   stream, which clears the list of earlier reference frames (DPBs).

keyframe
   an encoded frame that does not reference frames decoded earlier, i.e.
   can be decoded fully on its own.

macroblock
   a processing unit in image and video compression formats based on linear
   block transforms (e.g. H.264, VP8, VP9); codec-specific, but for most of
   popular codecs the size is 16x16 samples (pixels). The HEVC codec uses a
   slightly more flexible processing unit called coding tree unit (CTU).

OUTPUT
   the source buffer queue; for decoders, the queue of buffers containing
   an encoded bytestream; for encoders, the queue of buffers containing raw
   frames; ``V4L2_BUF_TYPE_VIDEO_OUTPUT`` or
   ``V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE``; the hardware is fed with data
   from ``OUTPUT`` buffers.

PPS
   Picture Parameter Set; a type of metadata entity in an H.264/HEVC bytestream.

raw format
   uncompressed format containing raw pixel data (e.g. YUV, RGB formats).

resume point
   a point in the bytestream from which decoding may start/continue, without
   any previous state/data present, e.g.: a keyframe (VP8/VP9) or
   SPS/PPS/IDR sequence (H.264/HEVC); a resume point is required to start decode
   of a new stream, or to resume decoding after a seek.

source
   data fed to the decoder or encoder; see ``OUTPUT``.

source height
   height in pixels for given source resolution; relevant to encoders only.

source resolution
   resolution in pixels of source frames being source to the encoder and
   subject to further cropping to the bounds of visible resolution; relevant to
   encoders only.

source width
   width in pixels for given source resolution; relevant to encoders only.

SPS
   Sequence Parameter Set; a type of metadata entity in an H.264/HEVC bytestream.

stream metadata
   additional (non-visual) information contained inside encoded bytestream;
   for example: coded resolution, visible resolution, codec profile.

visible height
   height for given visible resolution; display height.

visible resolution
   stream resolution of the visible picture, in pixels, to be used for
   display purposes; must be smaller or equal to coded resolution;
   display resolution.

visible width
   width for given visible resolution; display width.

디코더 상태 기계

167-213

상태 기계는 `open()`의 Initialization에서 시작해 CAPTURE format 확정, buffer 준비, Stopped를 거쳐 Decoding으로 이동합니다. Decoding 중에는 resolution change, drain, EOS, seek, CAPTURE 정지 같은 사건이 각각 전용 상태 전이를 일으킵니다.

원문의 DOT graph는 아래 흐름과 전이 표로 구조화했습니다. `OUTPUT` STREAMOFF는 여러 상태에서 Seek로 이동하고, `CAPTURE` STREAMOFF는 decode나 drain을 Stopped로 끝내는 핵심 차이가 있습니다.

주요 decoder 생명주기
open() -> InitializationCAPTURE format established -> Capture setupCAPTURE buffers ready -> StoppedSTART 또는 CAPTURE STREAMON -> Decodingresolution change -> Dynamic Resolution Change -> Capture setupSTOP 또는 EOS -> Drain -> StoppedOUTPUT STREAMOFF -> Seek -> OUTPUT STREAMON -> Decoding

초기화부터 정상 decode, 재구성과 재시작까지의 중심 경로입니다.

상태 전이
항목설명
Initialization -> Capture setupCAPTURE format established
Capture setup -> StoppedCAPTURE buffers ready
Decoding -> Dynamic Resolution Changestream resolution change
Decoding -> DrainV4L2_DEC_CMD_STOP
Decoding -> End of Streamstream 안의 EOS mark
Decoding -> SeekVIDIOC_STREAMOFF(OUTPUT)
Decoding -> StoppedVIDIOC_STREAMOFF(CAPTURE)
Dynamic Resolution Change -> Capture setup새 CAPTURE format 확정
End of Stream -> Drainimplicit drain
Drain -> Stopped모든 CAPTURE buffer dequeue 또는 CAPTURE STREAMOFF
Drain -> SeekOUTPUT STREAMOFF
Seek -> DecodingOUTPUT STREAMON
Seek -> InitializationREQBUFS(OUTPUT, 0)
Stopped -> DecodingDEC_CMD_START 또는 CAPTURE STREAMON

DOT graph의 사건별 출발 상태와 도착 상태입니다.

State Machine
=============

.. kernel-render:: DOT
   :alt: DOT digraph of decoder state machine
   :caption: Decoder State Machine

   digraph decoder_state_machine {
       node [shape = doublecircle, label="Decoding"] Decoding;

       node [shape = circle, label="Initialization"] Initialization;
       node [shape = circle, label="Capture\nsetup"] CaptureSetup;
       node [shape = circle, label="Dynamic\nResolution\nChange"] ResChange;
       node [shape = circle, label="Stopped"] Stopped;
       node [shape = circle, label="Drain"] Drain;
       node [shape = circle, label="Seek"] Seek;
       node [shape = circle, label="End of Stream"] EoS;

       node [shape = point]; qi
       qi -> Initialization [ label = "open()" ];

       Initialization -> CaptureSetup [ label = "CAPTURE\nformat\nestablished" ];

       CaptureSetup -> Stopped [ label = "CAPTURE\nbuffers\nready" ];

       Decoding -> ResChange [ label = "Stream\nresolution\nchange" ];
       Decoding -> Drain [ label = "V4L2_DEC_CMD_STOP" ];
       Decoding -> EoS [ label = "EoS mark\nin the stream" ];
       Decoding -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];
       Decoding -> Stopped [ label = "VIDIOC_STREAMOFF(CAPTURE)" ];
       Decoding -> Decoding;

       ResChange -> CaptureSetup [ label = "CAPTURE\nformat\nestablished" ];
       ResChange -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];

       EoS -> Drain [ label = "Implicit\ndrain" ];

       Drain -> Stopped [ label = "All CAPTURE\nbuffers dequeued\nor\nVIDIOC_STREAMOFF(CAPTURE)" ];
       Drain -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];

       Seek -> Decoding [ label = "VIDIOC_STREAMON(OUTPUT)" ];
       Seek -> Initialization [ label = "VIDIOC_REQBUFS(OUTPUT, 0)" ];

       Stopped -> Decoding [ label = "V4L2_DEC_CMD_START\nor\nVIDIOC_STREAMON(CAPTURE)" ];
       Stopped -> Seek [ label = "VIDIOC_STREAMOFF(OUTPUT)" ];
   }

지원 format과 해상도 조회

214-253

decoder의 coded format 전체를 열거하려면 `OUTPUT`에서 `VIDIOC_ENUM_FMT`를 호출합니다. 현재 `CAPTURE` format과 관계없이 지원하는 전체 coded format이 반환됩니다. `struct v4l2_fmtdesc`의 `flags`에서 완전한 bytestream parser 보유 여부와 dynamic resolution change 지원 여부 등 format별 capability를 확인할 수 있습니다.

지원 raw format을 열거하려면 `CAPTURE`에서 `VIDIOC_ENUM_FMT`를 호출합니다. 여기서는 현재 `OUTPUT`에 활성화된 coded format과 함께 사용할 수 있는 format만 반환되므로, 특정 coded format의 raw format을 알아보려면 먼저 `OUTPUT`에 coded format을 설정해야 합니다.

`VIDIOC_ENUM_FRAMESIZES`에 원하는 pixel format을 `struct v4l2_frmsizeenum.pixel_format`으로 전달하면 지원 해상도를 확인할 수 있습니다. coded pixel format에는 decoder가 지원하는 모든 coded resolution이, raw pixel format에는 현재 `OUTPUT` coded format과 조합할 수 있는 모든 frame buffer resolution이 포함됩니다.

현재 `OUTPUT`에 설정한 coded format에 profile과 level 개념이 있다면 각각의 control을 `VIDIOC_QUERYCTRL`로 조회할 수 있습니다.

Capability 조회 방향
항목설명
ENUM_FMT on OUTPUT현재 CAPTURE와 무관한 전체 coded format
ENUM_FMT on CAPTURE현재 OUTPUT coded format이 지원하는 raw format 부분집합
ENUM_FRAMESIZES coded해당 coded format의 모든 coded resolution
ENUM_FRAMESIZES raw현재 OUTPUT format과 조합 가능한 frame buffer resolution
QUERYCTRL현재 coded format의 profile과 level

queue와 ioctl 조합에 따라 반환 범위가 달라집니다.

Querying Capabilities
=====================

1. To enumerate the set of coded formats supported by the decoder, the
   client may call :c:func:`VIDIOC_ENUM_FMT` on ``OUTPUT``.

   * The full set of supported formats will be returned, regardless of the
     format set on ``CAPTURE``.
   * Check the flags field of :c:type:`v4l2_fmtdesc` for more information
     about the decoder's capabilities with respect to each coded format.
     In particular whether or not the decoder has a full-fledged bytestream
     parser and if the decoder supports dynamic resolution changes.

2. To enumerate the set of supported raw formats, the client may call
   :c:func:`VIDIOC_ENUM_FMT` on ``CAPTURE``.

   * Only the formats supported for the format currently active on ``OUTPUT``
     will be returned.

   * In order to enumerate raw formats supported by a given coded format,
     the client must first set that coded format on ``OUTPUT`` and then
     enumerate formats on ``CAPTURE``.

3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
   resolutions for a given format, passing desired pixel format in
   :c:type:`v4l2_frmsizeenum` ``pixel_format``.

   * Values returned by :c:func:`VIDIOC_ENUM_FRAMESIZES` for a coded pixel
     format will include all possible coded resolutions supported by the
     decoder for given coded pixel format.

   * Values returned by :c:func:`VIDIOC_ENUM_FRAMESIZES` for a raw pixel format
     will include all possible frame buffer resolutions supported by the
     decoder for given raw pixel format and the coded format currently set on
     ``OUTPUT``.

4. Supported profiles and levels for the coded format currently set on
   ``OUTPUT``, if applicable, may be queried using their respective controls
   via :c:func:`VIDIOC_QUERYCTRL`.

OUTPUT format과 source buffer 초기화

254-352

초기화의 첫 단계는 `VIDIOC_S_FMT`로 `OUTPUT`에 coded format을 설정하는 것입니다. 필수 입력은 OUTPUT에 맞는 `type`, coded `pixelformat`, 필요할 경우 stream의 coded `width`와 `height`, 원하는 OUTPUT buffer 크기 `sizeimage`입니다. 그 밖의 필드는 표준 의미를 따릅니다.

stream에서 해상도를 parse할 수 있는 format이면 width와 height는 실제 정보가 발견될 때까지 쓰는 placeholder일 뿐입니다. 드라이버는 하드웨어 요구에 맞춰 `sizeimage`를 조정해 반환합니다.

S_FMT가 돌려준 width와 height를 바탕으로 `CAPTURE` format의 frame buffer resolution도 즉시 갱신됩니다. stream 자체에 해상도 정보가 있다면 decoder는 이를 parse한 뒤 client가 설정한 값과 일치하는지와 관계없이 CAPTURE format을 다시 갱신하고 source change event를 보냅니다.

`OUTPUT` format을 바꾸면 현재 `CAPTURE` format도 바뀔 수 있습니다. 새 CAPTURE format을 결정하는 방식은 decoder에 달려 있으므로 client는 변경 뒤 자신의 요구와 맞는지 반드시 확인해야 합니다.

그 다음 `OUTPUT`에서 `VIDIOC_REQBUFS`로 source bytestream buffer를 할당합니다. `count`는 0보다 커야 하고 `type`은 OUTPUT용이며 `memory`는 표준 의미를 따릅니다. 반환된 실제 `count`는 요청과 다를 수 있으므로 반드시 다시 읽어야 합니다.

더 세밀한 buffer 할당이 필요하면 `OUTPUT`에서 `VIDIOC_CREATE_BUFS`를 사용할 수 있습니다. 이때 `count`, `type`, `memory`, `format`을 입력하고 조정된 실제 `count`를 확인합니다.

OUTPUT 초기화 필드
항목설명
S_FMT.typeOUTPUT에 맞는 V4L2_BUF_TYPE_*
S_FMT.pixelformatcoded pixel format
S_FMT.width/height필요할 때 stream coded resolution 또는 placeholder
S_FMT.sizeimage원하는 OUTPUT buffer 크기, 드라이버가 조정 가능
REQBUFScount > 0, OUTPUT type, memory; 실제 count 반환
CREATE_BUFScount > 0, OUTPUT type, memory, format; 실제 count 반환

format 설정과 두 buffer 할당 방식의 필수·반환 항목입니다.

OUTPUT 초기화
VIDIOC_S_FMT(OUTPUT)으로 coded format 설정반환된 width, height, sizeimage 확인자동으로 갱신된 CAPTURE placeholder format 인지VIDIOC_REQBUFS 또는 CREATE_BUFS로 OUTPUT buffer 할당반환된 실제 buffer count 확인

coded format부터 source buffer 준비까지의 순서입니다.

Initialization
==============

1. Set the coded format on ``OUTPUT`` via :c:func:`VIDIOC_S_FMT`.

   * **Required fields:**

     ``type``
         a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.

     ``pixelformat``
         a coded pixel format.

     ``width``, ``height``
         coded resolution of the stream; required only if it cannot be parsed
         from the stream for the given coded format; otherwise the decoder will
         use this resolution as a placeholder resolution that will likely change
         as soon as it can parse the actual coded resolution from the stream.

     ``sizeimage``
         desired size of ``OUTPUT`` buffers; the decoder may adjust it to
         match hardware requirements.

     other fields
         follow standard semantics.

   * **Returned fields:**

     ``sizeimage``
         adjusted size of ``OUTPUT`` buffers.

   * The ``CAPTURE`` format will be updated with an appropriate frame buffer
     resolution instantly based on the width and height returned by
     :c:func:`VIDIOC_S_FMT`.
     However, for coded formats that include stream resolution information,
     after the decoder is done parsing the information from the stream, it will
     update the ``CAPTURE`` format with new values and signal a source change
     event, regardless of whether they match the values set by the client or
     not.

   .. important::

      Changing the ``OUTPUT`` format may change the currently set ``CAPTURE``
      format. How the new ``CAPTURE`` format is determined is up to the decoder
      and the client must ensure it matches its needs afterwards.

2.  Allocate source (bytestream) buffers via :c:func:`VIDIOC_REQBUFS` on
    ``OUTPUT``.

    * **Required fields:**

      ``count``
          requested number of buffers to allocate; greater than zero.

      ``type``
          a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.

      ``memory``
          follows standard semantics.

    * **Returned fields:**

      ``count``
          the actual number of buffers allocated.

    .. warning::

       The actual number of allocated buffers may differ from the ``count``
       given. The client must check the updated value of ``count`` after the
       call returns.

    Alternatively, :c:func:`VIDIOC_CREATE_BUFS` on the ``OUTPUT`` queue can be
    used to have more control over buffer allocation.

    * **Required fields:**

      ``count``
          requested number of buffers to allocate; greater than zero.

      ``type``
          a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.

      ``memory``
          follows standard semantics.

      ``format``
          follows standard semantics.

    * **Returned fields:**

      ``count``
          adjusted to the number of allocated buffers.

    .. warning::

       The actual number of allocated buffers may differ from the ``count``
       given. The client must check the updated value of ``count`` after the
       call returns.

stream metadata parsing과 source change

353-401

`VIDIOC_STREAMON`으로 `OUTPUT` queue의 streaming을 시작합니다. stream 안에 resolution 정보가 들어 있는 coded format에만 이어지는 metadata parsing 단계가 적용됩니다.

client는 `VIDIOC_QBUF`와 `VIDIOC_DQBUF`로 OUTPUT bytestream buffer를 계속 넣고 돌려받습니다. CAPTURE queue를 구성하는 데 필요한 metadata를 찾으면 decoder가 `changes = V4L2_EVENT_SRC_CH_RESOLUTION`인 `V4L2_EVENT_SOURCE_CHANGE` event를 보냅니다.

첫 buffer에 충분한 정보가 없어도 오류가 아니며 필요한 만큼 처리가 계속됩니다. event를 일으킨 buffer의 데이터가 첫 frame decode에 필요하면 초기화와 첫 frame decode가 끝날 때까지 그 buffer를 client에 반환하지 않습니다.

client가 coded resolution을 직접 설정하지 않았다면 source change event 전의 CAPTURE `VIDIOC_G_FMT`, `VIDIOC_S_FMT`, `VIDIOC_TRY_FMT`, `VIDIOC_REQBUFS`는 실제 stream 값을 반환하지 않습니다. decoder가 event를 queue한 뒤의 format, selection rectangle, control 조회는 방금 parse한 stream에 적용되는 값을 반환합니다.

client가 bytestream에서 parameter를 자체 추출할 수 있다면 OUTPUT width와 height를 0이 아닌 coded size로 설정하고 parsing 대기 단계를 건너뛸 수 있습니다. 그러나 decoder가 아직 metadata를 parse하지 않았으므로 selection과 control 같은 driver 조회값에 의존해서는 안 됩니다. client 값과 나중에 parse한 값이 다르면 Dynamic Resolution Change가 발생합니다.

이 metadata 탐색 단계에서는 decoded frame을 만들지 않습니다. source change를 확인하거나 유효하게 단계를 건너뛴 뒤 Capture Setup으로 진행합니다.

stream 정보 확정
STREAMON(OUTPUT)QBUF/DQBUF로 bytestream chunk 공급decoder가 coded/visible resolution metadata parseSOURCE_CHANGE + SRC_CH_RESOLUTION event queueevent 이후 실제 format, selection, control 조회Capture Setup으로 이동

resolution metadata가 있는 coded format의 준비 절차입니다.

3.  Start streaming on the ``OUTPUT`` queue via :c:func:`VIDIOC_STREAMON`.

4.  **This step only applies to coded formats that contain resolution information
    in the stream.** Continue queuing/dequeuing bytestream buffers to/from the
    ``OUTPUT`` queue via :c:func:`VIDIOC_QBUF` and :c:func:`VIDIOC_DQBUF`. The
    buffers will be processed and returned to the client in order, until
    required metadata to configure the ``CAPTURE`` queue are found. This is
    indicated by the decoder sending a ``V4L2_EVENT_SOURCE_CHANGE`` event with
    ``changes`` set to ``V4L2_EVENT_SRC_CH_RESOLUTION``.

    * It is not an error if the first buffer does not contain enough data for
      this to occur. Processing of the buffers will continue as long as more
      data is needed.

    * If data in a buffer that triggers the event is required to decode the
      first frame, it will not be returned to the client, until the
      initialization sequence completes and the frame is decoded.

    * If the client has not set the coded resolution of the stream on its own,
      calling :c:func:`VIDIOC_G_FMT`, :c:func:`VIDIOC_S_FMT`,
      :c:func:`VIDIOC_TRY_FMT` or :c:func:`VIDIOC_REQBUFS` on the ``CAPTURE``
      queue will not return the real values for the stream until a
      ``V4L2_EVENT_SOURCE_CHANGE`` event with ``changes`` set to
      ``V4L2_EVENT_SRC_CH_RESOLUTION`` is signaled.

    .. important::

       Any client query issued after the decoder queues the event will return
       values applying to the just parsed stream, including queue formats,
       selection rectangles and controls.

    .. note::

       A client capable of acquiring stream parameters from the bytestream on
       its own may attempt to set the width and height of the ``OUTPUT`` format
       to non-zero values matching the coded size of the stream, skip this step
       and continue with the `Capture Setup` sequence. However, it must not
       rely on any driver queries regarding stream parameters, such as
       selection rectangles and controls, since the decoder has not parsed them
       from the stream yet. If the values configured by the client do not match
       those parsed by the decoder, a `Dynamic Resolution Change` will be
       triggered to reconfigure them.

    .. note::

       No decoded frames are produced during this phase.

5.  Continue with the `Capture Setup` sequence.

CAPTURE format, selection과 raw format

402-516

Capture Setup 첫 단계에서 `CAPTURE` queue에 `VIDIOC_G_FMT`를 호출해 bytestream에서 parse되고 decode될 destination buffer format을 얻습니다. 입력은 CAPTURE용 `type`이며, 반환값은 decoded frame의 `width`, `height`, `pixelformat`, multi-planar일 때 `num_planes`, 표준 frame buffer 의미의 `sizeimage`와 `bytesperline`입니다.

기본 `pixelformat`은 현재 stream에 대해 decoder가 지원하는 어느 format이든 될 수 있으며 decoder는 최적 format을 선택해야 합니다. 예를 들어 RGB 변환이 추가로 필요하다면 YUV가 기본값으로 선호될 수 있습니다.

선택 단계로 `VIDIOC_G_SELECTION`에 CAPTURE용 `type`과 `target = V4L2_SEL_TGT_COMPOSE`를 주면 visible rectangle `r.left`, `r.top`, `r.width`, `r.height`를 얻을 수 있습니다. 이 rectangle은 CAPTURE G_FMT의 frame buffer resolution 안에 들어가야 합니다.

CAPTURE selection target은 coded bounds, 의미 있는 picture 영역, crop 결과, compose 가능 bounds, 기본 compose, 실제 compose, 하드웨어가 덮어쓰는 padded 영역을 각각 표현합니다. stream metadata parsing 전에는 이 값들의 의미가 보장되지 않습니다.

CAPTURE selection target
항목설명
V4L2_SEL_TGT_CROP_BOUNDSstream의 coded resolution
V4L2_SEL_TGT_CROP_DEFAULTCAPTURE buffer에서 의미 있는 visible picture 영역
V4L2_SEL_TGT_CROPcoded resolution 중 CAPTURE로 출력할 영역. 기본값은 CROP_DEFAULT
V4L2_SEL_TGT_COMPOSE_BOUNDScropped frame을 배치할 수 있는 CAPTURE buffer 최대 rectangle
V4L2_SEL_TGT_COMPOSE_DEFAULTV4L2_SEL_TGT_CROP과 동일
V4L2_SEL_TGT_COMPOSEcropped frame이 실제 기록되는 CAPTURE buffer 내부 rectangle
V4L2_SEL_TGT_COMPOSE_PADDED하드웨어가 덮어쓰는 영역. padding을 쓰지 않으면 COMPOSE와 동일

coded picture에서 CAPTURE buffer까지의 crop과 compose 경계를 구분합니다.

stream 정보가 확정된 뒤 `CAPTURE`에서 `VIDIOC_ENUM_FMT`를 호출하면 현재 stream에 지원되는 raw format을 열거할 수 있고, 그중 하나를 S_FMT로 선택할 수 있습니다. 이 목록은 decoder 전체 capability가 아니라 현재 OUTPUT format과 parse된 metadata에 맞는 부분집합입니다.

예를 들어 어떤 decoder가 1920x1088 이하에서는 YUV와 RGB를 모두 지원하지만 그보다 높은 해상도에서는 YUV만 지원할 수 있습니다. 높은 해상도를 parse한 뒤에는 RGB가 열거되지 않지만, 같은 stream의 후속 resolution change로 낮은 해상도로 전환되면 RGB가 다시 반환될 수 있습니다.

CAPTURE G_FMT 반환값
항목설명
width, heightdecoded frame buffer resolution
pixelformatdecoded frame의 raw pixel format
num_planes_MPLANE type의 plane 수
sizeimage, bytesperline선택된 frame buffer format의 표준 메모리 배치

decoded frame buffer를 구성하는 핵심 필드입니다.

Capture Setup
=============

1.  Call :c:func:`VIDIOC_G_FMT` on the ``CAPTURE`` queue to get format for the
    destination buffers parsed/decoded from the bytestream.

    * **Required fields:**

      ``type``
          a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.

    * **Returned fields:**

      ``width``, ``height``
          frame buffer resolution for the decoded frames.

      ``pixelformat``
          pixel format for decoded frames.

      ``num_planes`` (for _MPLANE ``type`` only)
          number of planes for pixelformat.

      ``sizeimage``, ``bytesperline``
          as per standard semantics; matching frame buffer format.

    .. note::

       The value of ``pixelformat`` may be any pixel format supported by the
       decoder for the current stream. The decoder should choose a
       preferred/optimal format for the default configuration. For example, a
       YUV format may be preferred over an RGB format if an additional
       conversion step would be required for the latter.

2.  **Optional.** Acquire the visible resolution via
    :c:func:`VIDIOC_G_SELECTION`.

    * **Required fields:**

      ``type``
          a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.

      ``target``
          set to ``V4L2_SEL_TGT_COMPOSE``.

    * **Returned fields:**

      ``r.left``, ``r.top``, ``r.width``, ``r.height``
          the visible rectangle; it must fit within the frame buffer resolution
          returned by :c:func:`VIDIOC_G_FMT` on ``CAPTURE``.

    * The following selection targets are supported on ``CAPTURE``:

      ``V4L2_SEL_TGT_CROP_BOUNDS``
          corresponds to the coded resolution of the stream.

      ``V4L2_SEL_TGT_CROP_DEFAULT``
          the rectangle covering the part of the ``CAPTURE`` buffer that
          contains meaningful picture data (visible area); width and height
          will be equal to the visible resolution of the stream.

      ``V4L2_SEL_TGT_CROP``
          the rectangle within the coded resolution to be output to
          ``CAPTURE``; defaults to ``V4L2_SEL_TGT_CROP_DEFAULT``; read-only on
          hardware without additional compose/scaling capabilities.

      ``V4L2_SEL_TGT_COMPOSE_BOUNDS``
          the maximum rectangle within a ``CAPTURE`` buffer, which the cropped
          frame can be composed into; equal to ``V4L2_SEL_TGT_CROP`` if the
          hardware does not support compose/scaling.

      ``V4L2_SEL_TGT_COMPOSE_DEFAULT``
          equal to ``V4L2_SEL_TGT_CROP``.

      ``V4L2_SEL_TGT_COMPOSE``
          the rectangle inside a ``CAPTURE`` buffer into which the cropped
          frame is written; defaults to ``V4L2_SEL_TGT_COMPOSE_DEFAULT``;
          read-only on hardware without additional compose/scaling capabilities.

      ``V4L2_SEL_TGT_COMPOSE_PADDED``
          the rectangle inside a ``CAPTURE`` buffer which is overwritten by the
          hardware; equal to ``V4L2_SEL_TGT_COMPOSE`` if the hardware does not
          write padding pixels.

    .. warning::

       The values are guaranteed to be meaningful only after the decoder
       successfully parses the stream metadata. The client must not rely on the
       query before that happens.

3.  **Optional.** Enumerate ``CAPTURE`` formats via :c:func:`VIDIOC_ENUM_FMT` on
    the ``CAPTURE`` queue. Once the stream information is parsed and known, the
    client may use this ioctl to discover which raw formats are supported for
    given stream and select one of them via :c:func:`VIDIOC_S_FMT`.

    .. important::

       The decoder will return only formats supported for the currently
       established coded format, as per the ``OUTPUT`` format and/or stream
       metadata parsed in this initialization sequence, even if more formats
       may be supported by the decoder in general. In other words, the set
       returned will be a subset of the initial query mentioned in the
       `Querying Capabilities` section.

       For example, a decoder may support YUV and RGB formats for resolutions
       1920x1088 and lower, but only YUV for higher resolutions (due to
       hardware limitations). After parsing a resolution of 1920x1088 or lower,
       :c:func:`VIDIOC_ENUM_FMT` may return a set of YUV and RGB pixel formats,
       but after parsing resolution higher than 1920x1088, the decoder will not
       return RGB, unsupported for this resolution.

       However, subsequent resolution change event triggered after
       discovering a resolution change within the same stream may switch
       the stream into a lower resolution and :c:func:`VIDIOC_ENUM_FMT`
       would return RGB formats again in that case.

CAPTURE format 설정과 buffer 재사용 판단

517-617

client는 선택적으로 `CAPTURE`의 `VIDIOC_S_FMT`로 G_FMT가 제안한 것과 다른 raw format을 고를 수 있습니다. 필수 필드는 CAPTURE용 `type`, raw `pixelformat`, decoded stream의 frame buffer `width`와 `height`입니다. composition 또는 scaling을 지원하면 width와 height가 G_FMT 결과와 달라질 수 있습니다.

CAPTURE format을 설정하면 새 resolution을 기준으로 compose selection rectangle이 기본값으로 초기화됩니다. compose나 scaling을 지원하는 decoder에서는 이어서 `VIDIOC_S_SELECTION`에 CAPTURE용 type, `V4L2_SEL_TGT_COMPOSE`, 원하는 rectangle을 줄 수 있습니다.

S_SELECTION은 조정된 visible rectangle을 반환합니다. codec과 하드웨어 제약 때문에 가장 가까운 지원 rectangle으로 바뀔 수 있으므로 client는 반환된 `r.left`, `r.top`, `r.width`, `r.height`를 확인해야 합니다.

새 format의 `sizeimage`가 현재 buffer 크기 이하이고, 현재 할당 수가 필요한 최소 buffer 수 이상이면 CAPTURE buffer를 다시 할당하지 않고 즉시 decode를 재개할 수 있습니다. 부족한 수만 `VIDIOC_CREATE_BUFS`로 추가해 이 조건을 만족시킬 수도 있습니다.

CAPTURE가 streaming 중이면 `V4L2_DEC_CMD_START`, 정지 상태이면 CAPTURE `VIDIOC_STREAMON`으로 재개합니다. 메모리 절약 등으로 buffer 집합을 바꾸려면 fast path 대신 이후 재할당 단계를 따릅니다.

재할당 경로에서는 CAPTURE가 streaming 중일 때 `V4L2_BUF_FLAG_LAST` buffer까지 queue/dequeue한 뒤 CAPTURE에 STREAMOFF를 호출합니다. 이때 OUTPUT은 반드시 streaming 상태를 유지해야 하며 OUTPUT STREAMOFF는 절차를 중단하고 seek를 일으킵니다. CAPTURE buffer가 있으면 REQBUFS의 `count = 0`, CAPTURE용 `type`, 표준 `memory`로 해제합니다.

CAPTURE buffer 재사용 fast path
새 sizeimage <= 기존 buffer 크기 확인기존 count >= 최소 필요 buffer 수 확인필요하면 CREATE_BUFS로 buffer 추가streaming이면 DEC_CMD_START정지 상태이면 STREAMON(CAPTURE)

해상도 변경 뒤 기존 메모리를 유지할 수 있는 조건과 재개 동작입니다.

CAPTURE 재할당 경로
LAST가 dequeue될 때까지 CAPTURE 처리STREAMOFF(CAPTURE), OUTPUT은 계속 streamingREQBUFS(CAPTURE, count=0)으로 기존 buffer 해제새 CAPTURE buffer 할당 단계로 이동

기존 buffer가 충분하지 않거나 집합을 바꾸려는 경우입니다.

4.  **Optional.** Set the ``CAPTURE`` format via :c:func:`VIDIOC_S_FMT` on the
    ``CAPTURE`` queue. The client may choose a different format than
    selected/suggested by the decoder in :c:func:`VIDIOC_G_FMT`.

    * **Required fields:**

      ``type``
          a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.

      ``pixelformat``
          a raw pixel format.

      ``width``, ``height``
         frame buffer resolution of the decoded stream; typically unchanged from
	 what was returned with :c:func:`VIDIOC_G_FMT`, but it may be different
	 if the hardware supports composition and/or scaling.

   * Setting the ``CAPTURE`` format will reset the compose selection rectangles
     to their default values, based on the new resolution, as described in the
     previous step.

5. **Optional.** Set the compose rectangle via :c:func:`VIDIOC_S_SELECTION` on
   the ``CAPTURE`` queue if it is desired and if the decoder has compose and/or
   scaling capabilities.

   * **Required fields:**

     ``type``
         a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.

     ``target``
         set to ``V4L2_SEL_TGT_COMPOSE``.

     ``r.left``, ``r.top``, ``r.width``, ``r.height``
         the rectangle inside a ``CAPTURE`` buffer into which the cropped
         frame is written; defaults to ``V4L2_SEL_TGT_COMPOSE_DEFAULT``;
         read-only on hardware without additional compose/scaling capabilities.

   * **Returned fields:**

     ``r.left``, ``r.top``, ``r.width``, ``r.height``
         the visible rectangle; it must fit within the frame buffer resolution
         returned by :c:func:`VIDIOC_G_FMT` on ``CAPTURE``.

   .. warning::

      The decoder may adjust the compose rectangle to the nearest
      supported one to meet codec and hardware requirements. The client needs
      to check the adjusted rectangle returned by :c:func:`VIDIOC_S_SELECTION`.

6.  If all the following conditions are met, the client may resume the decoding
    instantly:

    * ``sizeimage`` of the new format (determined in previous steps) is less
      than or equal to the size of currently allocated buffers,

    * the number of buffers currently allocated is greater than or equal to the
      minimum number of buffers acquired in previous steps. To fulfill this
      requirement, the client may use :c:func:`VIDIOC_CREATE_BUFS` to add new
      buffers.

    In that case, the remaining steps do not apply and the client may resume
    the decoding by one of the following actions:

    * if the ``CAPTURE`` queue is streaming, call :c:func:`VIDIOC_DECODER_CMD`
      with the ``V4L2_DEC_CMD_START`` command,

    * if the ``CAPTURE`` queue is not streaming, call :c:func:`VIDIOC_STREAMON`
      on the ``CAPTURE`` queue.

    However, if the client intends to change the buffer set, to lower
    memory usage or for any other reasons, it may be achieved by following
    the steps below.

7.  **If the** ``CAPTURE`` **queue is streaming,** keep queuing and dequeuing
    buffers on the ``CAPTURE`` queue until a buffer marked with the
    ``V4L2_BUF_FLAG_LAST`` flag is dequeued.

8.  **If the** ``CAPTURE`` **queue is streaming,** call :c:func:`VIDIOC_STREAMOFF`
    on the ``CAPTURE`` queue to stop streaming.

    .. warning::

       The ``OUTPUT`` queue must remain streaming. Calling
       :c:func:`VIDIOC_STREAMOFF` on it would abort the sequence and trigger a
       seek.

9.  **If the** ``CAPTURE`` **queue has buffers allocated,** free the ``CAPTURE``
    buffers using :c:func:`VIDIOC_REQBUFS`.

    * **Required fields:**

      ``count``
          set to 0.

      ``type``
          a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.

      ``memory``
          follows standard semantics.

CAPTURE buffer 할당과 decode 시작

618-699

`CAPTURE`에서 `VIDIOC_REQBUFS`를 호출해 decoded frame buffer를 할당합니다. 요청 `count`는 0보다 커야 하고 `type`은 CAPTURE용이며 `memory`는 표준 의미를 따릅니다. 실제 할당 수는 요청과 다를 수 있으므로 반환된 `count`를 확인해야 합니다.

pipeline depth를 위해 최소 수보다 더 많은 buffer를 원하면 `V4L2_CID_MIN_BUFFERS_FOR_CAPTURE` control로 최소 수를 조회하고, 추가할 수를 더한 값을 REQBUFS의 `count`로 전달합니다.

더 많은 제어가 필요하면 CAPTURE의 `VIDIOC_CREATE_BUFS`를 사용할 수 있습니다. 현재 CAPTURE format보다 큰 buffer를 미리 할당하면 미래의 resolution change를 수용할 수 있습니다. 필수 입력은 `count`, CAPTURE용 `type`, `memory`, 새 buffer가 수용할 최대 frame buffer resolution을 나타내는 `format`이며 조정된 실제 count가 반환됩니다.

stream metadata parsing 전에 다른 format용 buffer를 준비하려면 먼저 OUTPUT width와 height를 원하는 coded resolution으로 설정해 decoder가 CAPTURE format을 구성하게 한 다음, CAPTURE G_FMT 결과를 저장해야 합니다. 이 저장한 format을 현재 단계의 CREATE_BUFS에 사용합니다.

할당을 마치면 CAPTURE queue에 `VIDIOC_STREAMON`을 호출해 frame decoding을 시작합니다.

CAPTURE buffer 준비
항목설명
REQBUFS.count0보다 큰 요청 수, 반환된 실제 수 확인
V4L2_CID_MIN_BUFFERS_FOR_CAPTUREdecode에 필요한 최소 CAPTURE buffer 수
추가 pipeline buffer최소 수에 원하는 pipeline depth를 더함
CREATE_BUFS.format새 buffer가 수용할 최대 frame buffer resolution
STREAMON(CAPTURE)할당 완료 뒤 frame decode 시작

할당 방식과 buffer 수 산정 규칙입니다.

선제적 대형 buffer 할당
OUTPUT width/height를 원하는 coded resolution으로 설정VIDIOC_G_FMT(CAPTURE) 결과 저장metadata parsing 진행저장한 format으로 CREATE_BUFS(CAPTURE)

metadata parsing 전에 미래 resolution을 수용하는 방법입니다.

10. Allocate ``CAPTURE`` buffers via :c:func:`VIDIOC_REQBUFS` on the
    ``CAPTURE`` queue.

    * **Required fields:**

      ``count``
          requested number of buffers to allocate; greater than zero.

      ``type``
          a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.

      ``memory``
          follows standard semantics.

    * **Returned fields:**

      ``count``
          actual number of buffers allocated.

    .. warning::

       The actual number of allocated buffers may differ from the ``count``
       given. The client must check the updated value of ``count`` after the
       call returns.

    .. note::

       To allocate more than the minimum number of buffers (for pipeline
       depth), the client may query the ``V4L2_CID_MIN_BUFFERS_FOR_CAPTURE``
       control to get the minimum number of buffers required, and pass the
       obtained value plus the number of additional buffers needed in the
       ``count`` field to :c:func:`VIDIOC_REQBUFS`.

    Alternatively, :c:func:`VIDIOC_CREATE_BUFS` on the ``CAPTURE`` queue can be
    used to have more control over buffer allocation. For example, by
    allocating buffers larger than the current ``CAPTURE`` format, future
    resolution changes can be accommodated.

    * **Required fields:**

      ``count``
          requested number of buffers to allocate; greater than zero.

      ``type``
          a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.

      ``memory``
          follows standard semantics.

      ``format``
          a format representing the maximum framebuffer resolution to be
          accommodated by newly allocated buffers.

    * **Returned fields:**

      ``count``
          adjusted to the number of allocated buffers.

    .. warning::

        The actual number of allocated buffers may differ from the ``count``
        given. The client must check the updated value of ``count`` after the
        call returns.

    .. note::

       To allocate buffers for a format different than parsed from the stream
       metadata, the client must proceed as follows, before the metadata
       parsing is initiated:

       * set width and height of the ``OUTPUT`` format to desired coded resolution to
         let the decoder configure the ``CAPTURE`` format appropriately,

       * query the ``CAPTURE`` format using :c:func:`VIDIOC_G_FMT` and save it
         until this step.

       The format obtained in the query may be then used with
       :c:func:`VIDIOC_CREATE_BUFS` in this step to allocate the buffers.

11. Call :c:func:`VIDIOC_STREAMON` on the ``CAPTURE`` queue to start decoding
    frames.

decode queue, timestamp와 reference memory

700-778

Capture Setup을 성공적으로 마치면 Decoding 상태에 도달합니다. client는 표준 의미에 따라 `VIDIOC_QBUF`와 `VIDIOC_DQBUF`로 두 queue 모두에 buffer를 넣고 빼며, OUTPUT 내용은 활성 coded pixel format과 codec별 extended control의 영향을 받습니다.

두 queue는 서로 독립적으로 동작하고 frame reordering 때문에 CAPTURE의 decoded frame 순서가 OUTPUT coded frame의 queue 순서와 다를 수 있습니다. client는 queue 사이의 직접적인 1:1 관계나 dequeue 가능 시점을 가정해서는 안 됩니다.

OUTPUT과 CAPTURE의 비동기 대응
항목설명
1 OUTPUT -> 0 CAPTUREencoded data가 없거나 metadata syntax만 포함
1 OUTPUT -> 여러 CAPTURE여러 frame 포함 또는 display reorder 해제
1 OUTPUT -> 지연된 CAPTURE후속 OUTPUT 처리 뒤 생성되거나 순서가 바뀜
추가 OUTPUT 없이 CAPTURE과거 OUTPUT 결과가 drain/EOS 중 뒤늦게 사용 가능

하나의 source buffer와 decoded frame 사이에 허용되는 관계입니다.

origin을 추적하려면 OUTPUT을 queue할 때 `struct v4l2_buffer.timestamp`를 설정할 수 있습니다. 그 OUTPUT에서 나온 CAPTURE buffer에는 dequeue 시 같은 timestamp가 복사됩니다.

하나의 OUTPUT이 여러 CAPTURE를 만들면 모두 같은 timestamp를 받고, 여러 OUTPUT이 하나의 CAPTURE를 만들면 가장 먼저 queue된 OUTPUT timestamp를 받습니다. decode order와 display order가 다르면 CAPTURE timestamp 순서도 OUTPUT timestamp 순서를 보존하지 않습니다.

reference frame으로 쓰이는 CAPTURE buffer의 backing memory는 dequeue 뒤에도 하드웨어가 읽을 수 있습니다. CAPTURE queue가 streaming인 동안 여기에 쓰면 decoded frame이 손상될 수 있습니다.

`V4L2_MEMORY_MMAP` 이외의 memory type에서는 streaming 동안 같은 CAPTURE buffer index를 항상 같은 backing memory와 함께 queue해야 합니다. 드라이버가 index로 frame을 식별하므로 reference memory를 다른 ID로 제출하면 사용 중인 메모리에 새 frame을 decode해 후속 frame을 손상할 수 있습니다.

timestamp 전달 규칙
QBUF(OUTPUT)에서 timestamp 지정decoder가 OUTPUT data 처리생성된 CAPTURE buffer에 동일 timestamp 복사DQBUF(CAPTURE)에서 origin 대응

source와 결과 buffer의 관계를 timestamp로 추적합니다.

Decoding
========

This state is reached after the `Capture Setup` sequence finishes successfully.
In this state, the client queues and dequeues buffers to both queues via
:c:func:`VIDIOC_QBUF` and :c:func:`VIDIOC_DQBUF`, following the standard
semantics.

The content of the source ``OUTPUT`` buffers depends on the active coded pixel
format and may be affected by codec-specific extended controls, as stated in
the documentation of each format.

Both queues operate independently, following the standard behavior of V4L2
buffer queues and memory-to-memory devices. In addition, the order of decoded
frames dequeued from the ``CAPTURE`` queue may differ from the order of queuing
coded frames to the ``OUTPUT`` queue, due to properties of the selected coded
format, e.g. frame reordering.

The client must not assume any direct relationship between ``CAPTURE``
and ``OUTPUT`` buffers and any specific timing of buffers becoming
available to dequeue. Specifically:

* a buffer queued to ``OUTPUT`` may result in no buffers being produced
  on ``CAPTURE`` (e.g. if it does not contain encoded data, or if only
  metadata syntax structures are present in it),

* a buffer queued to ``OUTPUT`` may result in more than one buffer produced
  on ``CAPTURE`` (if the encoded data contained more than one frame, or if
  returning a decoded frame allowed the decoder to return a frame that
  preceded it in decode, but succeeded it in the display order),

* a buffer queued to ``OUTPUT`` may result in a buffer being produced on
  ``CAPTURE`` later into decode process, and/or after processing further
  ``OUTPUT`` buffers, or be returned out of order, e.g. if display
  reordering is used,

* buffers may become available on the ``CAPTURE`` queue without additional
  buffers queued to ``OUTPUT`` (e.g. during drain or ``EOS``), because of the
  ``OUTPUT`` buffers queued in the past whose decoding results are only
  available at later time, due to specifics of the decoding process.

.. note::

   To allow matching decoded ``CAPTURE`` buffers with ``OUTPUT`` buffers they
   originated from, the client can set the ``timestamp`` field of the
   :c:type:`v4l2_buffer` struct when queuing an ``OUTPUT`` buffer. The
   ``CAPTURE`` buffer(s), which resulted from decoding that ``OUTPUT`` buffer
   will have their ``timestamp`` field set to the same value when dequeued.

   In addition to the straightforward case of one ``OUTPUT`` buffer producing
   one ``CAPTURE`` buffer, the following cases are defined:

   * one ``OUTPUT`` buffer generates multiple ``CAPTURE`` buffers: the same
     ``OUTPUT`` timestamp will be copied to multiple ``CAPTURE`` buffers.

   * multiple ``OUTPUT`` buffers generate one ``CAPTURE`` buffer: timestamp of
     the ``OUTPUT`` buffer queued first will be copied.

   * the decoding order differs from the display order (i.e. the ``CAPTURE``
     buffers are out-of-order compared to the ``OUTPUT`` buffers): ``CAPTURE``
     timestamps will not retain the order of ``OUTPUT`` timestamps.

.. note::

   The backing memory of ``CAPTURE`` buffers that are used as reference frames
   by the stream may be read by the hardware even after they are dequeued.
   Consequently, the client should avoid writing into this memory while the
   ``CAPTURE`` queue is streaming. Failure to observe this may result in
   corruption of decoded frames.

   Similarly, when using a memory type other than ``V4L2_MEMORY_MMAP``, the
   client should make sure that each ``CAPTURE`` buffer is always queued with
   the same backing memory for as long as the ``CAPTURE`` queue is streaming.
   The reason for this is that V4L2 buffer indices can be used by drivers to
   identify frames. Thus, if the backing memory of a reference frame is
   submitted under a different buffer ID, the driver may misidentify it and
   decode a new frame into it while it is still in use, resulting in corruption
   of the following frames.

특수 sequence와 decode 오류

779-811

decode 중 특별한 sequence가 시작되면 그 전에 처리된 모든 OUTPUT에서 유래한 CAPTURE buffer를 반환하고 마지막 buffer에 `V4L2_BUF_FLAG_LAST`를 설정합니다. client는 pending event를 확인해 SOURCE_CHANGE와 SRC_CH_RESOLUTION이면 Dynamic Resolution Change를, `V4L2_EVENT_EOS`이면 End of Stream을 수행해야 합니다. sequence들은 서로 섞여 발생할 수 있으므로 발생 순서대로 처리합니다.

decode 오류가 나면 실패 결과를 담은 CAPTURE buffer에 `V4L2_BUF_FLAG_ERROR`가 설정됩니다. decoder가 원인이 된 OUTPUT buffer를 정확히 식별할 수 있다면 그 buffer에도 같은 flag를 설정해 반환합니다.

decode를 계속할 수 없는 치명적 실패 뒤에는 해당 decoder file handle의 모든 후속 작업이 `-EIO`를 반환합니다. client는 handle을 닫고 새로 열거나, 두 queue를 STREAMOFF하고 모든 buffer를 해제한 다음 Initialization을 다시 수행해 instance를 재초기화할 수 있습니다.

Pending event 처리
항목설명
SOURCE_CHANGE + SRC_CH_RESOLUTIONDynamic Resolution Change
V4L2_EVENT_EOSEnd of Stream과 implicit Drain
CAPTURE ERROR flag해당 buffer의 decode 결과 실패
OUTPUT ERROR flagdecoder가 오류 유발 source를 정확히 식별
-EIO치명적 failure. handle 재생성 또는 완전 재초기화 필요

LAST buffer 뒤 client가 선택할 sequence입니다.

During the decoding, the decoder may initiate one of the special sequences, as
listed below. The sequences will result in the decoder returning all the
``CAPTURE`` buffers that originated from all the ``OUTPUT`` buffers processed
before the sequence started. Last of the buffers will have the
``V4L2_BUF_FLAG_LAST`` flag set. To determine the sequence to follow, the client
must check if there is any pending event and:

* if a ``V4L2_EVENT_SOURCE_CHANGE`` event with ``changes`` set to
  ``V4L2_EVENT_SRC_CH_RESOLUTION`` is pending, the `Dynamic Resolution
  Change` sequence needs to be followed,

* if a ``V4L2_EVENT_EOS`` event is pending, the `End of Stream` sequence needs
  to be followed.

Some of the sequences can be intermixed with each other and need to be handled
as they happen. The exact operation is documented for each sequence.

Should a decoding error occur, it will be reported to the client with the level
of details depending on the decoder capabilities. Specifically:

* the CAPTURE buffer that contains the results of the failed decode operation
  will be returned with the V4L2_BUF_FLAG_ERROR flag set,

* if the decoder is able to precisely report the OUTPUT buffer that triggered
  the error, such buffer will be returned with the V4L2_BUF_FLAG_ERROR flag
  set.

In case of a fatal failure that does not allow the decoding to continue, any
further operations on corresponding decoder file handle will return the -EIO
error code. The client may close the file handle and open a new one, or
alternatively reinitialize the instance by stopping streaming on both queues,
releasing all buffers and performing the Initialization sequence again.

Seek와 resume point

812-912

Seek는 coded data source인 `OUTPUT` queue가 제어합니다. CAPTURE에는 특별한 작업이 필수는 아니지만 독립적인 정상 decoder 동작의 영향을 받을 수 있습니다.

`VIDIOC_STREAMOFF(OUTPUT)`으로 seek를 시작하면 pending OUTPUT buffer가 모두 버려지고 표준 의미에 따라 client에 반환된 것으로 취급합니다. 이어 `VIDIOC_STREAMON(OUTPUT)`을 호출하면 새 source bytestream buffer를 받을 준비가 됩니다.

그 뒤 적절한 resume point를 찾을 때까지 seek 이후 coded data를 OUTPUT에 queue합니다. 반드시 SPS나 keyframe에서 정확히 시작할 필요는 없고, 적절한 지점을 찾을 때까지 buffer를 처리해 반환합니다. 이 탐색 중에는 CAPTURE에 decoded frame을 만들지 않아야 합니다.

일부 하드웨어는 resume point가 아닌 곳으로 seek할 때 불특정 수의 손상 frame을 CAPTURE에 낼 수 있습니다. 드라이버는 crash나 치명적 decode 오류가 일어나지 않도록 하드웨어별 처리와 workaround를 구현해야 합니다.

H.264/HEVC에서는 client가 SPS/PPS 변경을 건너뛰어 seek해서는 안 됩니다. target이 keyframe이어도 decoder에 남은 낡은 SPS/PPS 때문에 결과가 정의되지 않습니다. decoder는 crash 없이 처리해야 하지만 의미 있는 출력은 보장되지 않으며, 하드웨어가 손상을 감지하면 해당 CAPTURE buffer에 `V4L2_BUF_FLAG_ERROR`를 설정합니다.

resume point를 찾으면 decoder가 새 decoded CAPTURE buffer를 반환하기 시작합니다. target의 parameter가 이전 구간과 다르면 Dynamic Resolution Change가 일어날 수 있으며 일반 절차대로 처리해야 합니다.

CAPTURE는 OUTPUT과 독립적이므로 seek 전 OUTPUT에서 유래한 decoded buffer가 seek 뒤에도 남아 반환될 수 있고, STREAMOFF로 버린 OUTPUT은 대응 CAPTURE를 만들지 않을 수 있습니다. `QBUF(A), QBUF(B), STREAMOFF(), STREAMON(), QBUF(G), QBUF(H)` 뒤 CAPTURE 결과는 `{A', B', G', H'}`, `{A', G', H'}`, `{G', H'}` 모두 허용됩니다.

seek 이후 첫 frame은 timestamp로 OUTPUT과 CAPTURE를 맞추거나 STOP/START로 decoder를 drain해 식별할 수 있습니다. 즉시 seek가 필요하면 CAPTURE streaming도 재시작해 decode됐지만 아직 dequeue하지 않은 buffer를 버릴 수 있습니다.

Seek sequence
STREAMOFF(OUTPUT)으로 pending source 폐기STREAMON(OUTPUT)으로 새 source 허용seek target 이후 coded buffer queueresume point를 찾을 때까지 처리하되 CAPTURE frame 미생성resume point 뒤 decoded CAPTURE frame 반환필요하면 Dynamic Resolution Change 처리

OUTPUT을 재시작하고 새 resume point를 찾는 절차입니다.

Seek
====

Seek is controlled by the ``OUTPUT`` queue, as it is the source of coded data.
The seek does not require any specific operation on the ``CAPTURE`` queue, but
it may be affected as per normal decoder operation.

1. Stop the ``OUTPUT`` queue to begin the seek sequence via
   :c:func:`VIDIOC_STREAMOFF`.

   * **Required fields:**

     ``type``
         a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.

   * The decoder will drop all the pending ``OUTPUT`` buffers and they must be
     treated as returned to the client (following standard semantics).

2. Restart the ``OUTPUT`` queue via :c:func:`VIDIOC_STREAMON`.

   * **Required fields:**

     ``type``
         a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.

   * The decoder will start accepting new source bytestream buffers after the
     call returns.

3. Start queuing buffers containing coded data after the seek to the ``OUTPUT``
   queue until a suitable resume point is found.

   .. note::

      There is no requirement to begin queuing coded data starting exactly
      from a resume point (e.g. SPS or a keyframe). Any queued ``OUTPUT``
      buffers will be processed and returned to the client until a suitable
      resume point is found.  While looking for a resume point, the decoder
      should not produce any decoded frames into ``CAPTURE`` buffers.

      Some hardware is known to mishandle seeks to a non-resume point. Such an
      operation may result in an unspecified number of corrupted decoded frames
      being made available on the ``CAPTURE`` queue. Drivers must ensure that
      no fatal decoding errors or crashes occur, and implement any necessary
      handling and workarounds for hardware issues related to seek operations.

   .. warning::

      In case of the H.264/HEVC codec, the client must take care not to seek
      over a change of SPS/PPS. Even though the target frame could be a
      keyframe, the stale SPS/PPS inside decoder state would lead to undefined
      results when decoding. Although the decoder must handle that case without
      a crash or a fatal decode error, the client must not expect a sensible
      decode output.

      If the hardware can detect such corrupted decoded frames, then
      corresponding buffers will be returned to the client with the
      V4L2_BUF_FLAG_ERROR set. See the `Decoding` section for further
      description of decode error reporting.

4. After a resume point is found, the decoder will start returning ``CAPTURE``
   buffers containing decoded frames.

.. important::

   A seek may result in the `Dynamic Resolution Change` sequence being
   initiated, due to the seek target having decoding parameters different from
   the part of the stream decoded before the seek. The sequence must be handled
   as per normal decoder operation.

.. warning::

   It is not specified when the ``CAPTURE`` queue starts producing buffers
   containing decoded data from the ``OUTPUT`` buffers queued after the seek,
   as it operates independently from the ``OUTPUT`` queue.

   The decoder may return a number of remaining ``CAPTURE`` buffers containing
   decoded frames originating from the ``OUTPUT`` buffers queued before the
   seek sequence is performed.

   The ``VIDIOC_STREAMOFF`` operation discards any remaining queued
   ``OUTPUT`` buffers, which means that not all of the ``OUTPUT`` buffers
   queued before the seek sequence may have matching ``CAPTURE`` buffers
   produced.  For example, given the sequence of operations on the
   ``OUTPUT`` queue:

     QBUF(A), QBUF(B), STREAMOFF(), STREAMON(), QBUF(G), QBUF(H),

   any of the following results on the ``CAPTURE`` queue is allowed:

     {A', B', G', H'}, {A', G', H'}, {G', H'}.

   To determine the CAPTURE buffer containing the first decoded frame after the
   seek, the client may observe the timestamps to match the CAPTURE and OUTPUT
   buffers or use V4L2_DEC_CMD_STOP and V4L2_DEC_CMD_START to drain the
   decoder.

.. note::

   To achieve instantaneous seek, the client may restart streaming on the
   ``CAPTURE`` queue too to discard decoded, but not yet dequeued buffers.

동적 해상도 변경

913-995

bytestream에 resolution metadata가 있는 stream은 decode 도중 다른 해상도로 전환해야 할 수 있습니다. 이를 감지할 수 있는 decoder는 `VIDIOC_ENUM_FMT`에서 coded format에 `V4L2_FMT_FLAG_DYN_RESOLUTION`을 설정합니다.

이 sequence는 coded resolution, visible resolution selection rectangle, decode에 필요한 최소 buffer 수, bitstream bit-depth 가운데 하나 이상이 이전 확정값과 다른 coded frame을 발견할 때 시작됩니다.

decoder는 `changes = V4L2_EVENT_SRC_CH_RESOLUTION`인 `V4L2_EVENT_SOURCE_CHANGE`를 보냅니다. event가 queue된 뒤 client가 조회하는 queue format, selection rectangle, control은 변경 이후 stream에 적용되는 값을 반환합니다.

그 다음 decoder는 변경 지점 이전의 남은 buffer를 모두 처리하고 decode합니다. 마지막 이전 frame은 `V4L2_BUF_FLAG_LAST`로 표시해야 합니다. 이 buffer는 `bytesused = 0`인 빈 buffer일 수 있으며 decoded frame이 없으므로 client가 무시해야 합니다. LAST 이후 CAPTURE DQBUF는 `-EPIPE`를 반환합니다.

client는 source change event를 dequeue한 뒤 Capture Setup을 다시 수행합니다. source change는 명시적 Drain과 유사한 implicit drain을 일으켜 완료 뒤 decoder를 정지시키므로, CAPTURE에 STREAMOFF/STREAMON을 연속 호출하거나 `V4L2_DEC_CMD_START`를 호출해 decode를 재개해야 합니다.

resolution change 전체 동안 OUTPUT은 streaming 상태를 유지해야 합니다. OUTPUT STREAMOFF는 sequence를 중단하고 seek를 시작합니다. 성능과 단순성을 위해 client는 재구성 중에도 OUTPUT buffer를 계속 queue/dequeue하는 것이 좋습니다.

해상도 변경 감지 항목
항목설명
Coded resolutionOUTPUT width와 height
Visible resolutionselection rectangle
Minimum buffersdecode에 필요한 최소 CAPTURE buffer 수
Bit-depthbitstream의 sample bit-depth

기존 확정값과 달라질 때 source change가 발생하는 parameter입니다.

Dynamic Resolution Change
새 parameter를 가진 coded frame 감지SOURCE_CHANGE + SRC_CH_RESOLUTION event queue변경 전 frame을 LAST까지 decodeclient가 event dequeueCapture Setup으로 새 format과 buffer 구성CAPTURE 재시작 또는 DEC_CMD_START

event부터 CAPTURE 재구성과 decode 재개까지입니다.

Dynamic Resolution Change
=========================

Streams that include resolution metadata in the bytestream may require switching
to a different resolution during the decoding.

.. note::

   Not all decoders can detect resolution changes. Those that do set the
   ``V4L2_FMT_FLAG_DYN_RESOLUTION`` flag for the coded format when
   :c:func:`VIDIOC_ENUM_FMT` is called.

The sequence starts when the decoder detects a coded frame with one or more of
the following parameters different from those previously established (and
reflected by corresponding queries):

* coded resolution (``OUTPUT`` width and height),

* visible resolution (selection rectangles),

* the minimum number of buffers needed for decoding,

* bit-depth of the bitstream has been changed.

Whenever that happens, the decoder must proceed as follows:

1.  After encountering a resolution change in the stream, the decoder sends a
    ``V4L2_EVENT_SOURCE_CHANGE`` event with ``changes`` set to
    ``V4L2_EVENT_SRC_CH_RESOLUTION``.

    .. important::

       Any client query issued after the decoder queues the event will return
       values applying to the stream after the resolution change, including
       queue formats, selection rectangles and controls.

2.  The decoder will then process and decode all remaining buffers from before
    the resolution change point.

    * The last buffer from before the change must be marked with the
      ``V4L2_BUF_FLAG_LAST`` flag, similarly to the `Drain` sequence above.

    .. warning::

       The last buffer may be empty (with :c:type:`v4l2_buffer` ``bytesused``
       = 0) and in that case it must be ignored by the client, as it does not
       contain a decoded frame.

    .. note::

       Any attempt to dequeue more ``CAPTURE`` buffers beyond the buffer marked
       with ``V4L2_BUF_FLAG_LAST`` will result in a -EPIPE error from
       :c:func:`VIDIOC_DQBUF`.

The client must continue the sequence as described below to continue the
decoding process.

1.  Dequeue the source change event.

    .. important::

       A source change triggers an implicit decoder drain, similar to the
       explicit `Drain` sequence. The decoder is stopped after it completes.
       The decoding process must be resumed with either a pair of calls to
       :c:func:`VIDIOC_STREAMOFF` and :c:func:`VIDIOC_STREAMON` on the
       ``CAPTURE`` queue, or a call to :c:func:`VIDIOC_DECODER_CMD` with the
       ``V4L2_DEC_CMD_START`` command.

2.  Continue with the `Capture Setup` sequence.

.. note::

   During the resolution change sequence, the ``OUTPUT`` queue must remain
   streaming. Calling :c:func:`VIDIOC_STREAMOFF` on the ``OUTPUT`` queue would
   abort the sequence and initiate a seek.

   In principle, the ``OUTPUT`` queue operates separately from the ``CAPTURE``
   queue and this remains true for the duration of the entire resolution change
   sequence as well.

   The client should, for best performance and simplicity, keep queuing/dequeuing
   buffers to/from the ``OUTPUT`` queue even while processing this sequence.

Drain과 decoder 정지

996-1090

Drain은 이미 queue한 모든 OUTPUT을 처리하고 관련 CAPTURE를 전부 client에 전달하는 절차입니다. 완료되면 시작 전에 넣은 모든 OUTPUT의 decoded frame을 받은 상태가 됩니다.

`VIDIOC_DECODER_CMD`에 `cmd = V4L2_DEC_CMD_STOP`, `flags = 0`, `pts = 0`을 주어 시작합니다. OUTPUT과 CAPTURE가 모두 streaming일 때만 실제 drain이 시작됩니다. 호환성 때문에 queue가 정지 상태여도 ioctl 자체는 실패하지 않지만 이후 drain 단계는 적용되지 않습니다.

STOP 전에 queue한 OUTPUT은 정상 처리합니다. client는 두 queue를 독립적으로 계속 다뤄야 하며, 중간에 Dynamic Resolution Change가 발생하면 먼저 처리합니다. CAPTURE는 `V4L2_BUF_FLAG_LAST`가 붙은 buffer까지 queue/dequeue하고, 빈 LAST는 무시합니다. LAST 이후 DQBUF는 `-EPIPE`입니다.

STOP 전에 넣은 OUTPUT도 모두 dequeue해야 합니다. 구형 호환성을 위해 마지막 frame이 준비되면 `V4L2_EVENT_EOS`도 발생할 수 있으나 이 동작은 deprecated이므로 의존하지 말고 `V4L2_BUF_FLAG_LAST`를 사용해야 합니다.

기존 OUTPUT과 마지막 CAPTURE를 모두 dequeue하면 decoder는 멈추며 새 OUTPUT을 받아도 처리하지 않습니다. `V4L2_DEC_CMD_START`는 drain 전 상태를 유지한 채 정상 재개합니다. CAPTURE STREAMOFF/STREAMON도 재개하지만 queue에 남은 CAPTURE를 client에 반환합니다. OUTPUT STREAMOFF/STREAMON은 pending source를 반환하고 Seek를 시작합니다.

drain을 시작하면 어느 queue든 STREAMOFF해 중단하지 않는 한 끝까지 진행해야 합니다. 진행 중 다시 START나 STOP을 호출할 수 없으며 시도하면 `-EBUSY`가 반환됩니다. decoder command 지원 여부는 선택적으로 `VIDIOC_TRY_DECODER_CMD`로 조회할 수 있습니다.

Drain 시작 필드
항목설명
cmdV4L2_DEC_CMD_STOP
flags0
pts0
전제OUTPUT과 CAPTURE 모두 streaming

V4L2_DEC_CMD_STOP 요청에 필요한 값입니다.

Drain 완료 조건
DECODER_CMD(STOP)기존 OUTPUT 정상 decode중간 special sequence 우선 처리CAPTURE LAST buffer dequeueSTOP 전 OUTPUT 모두 dequeuedecoder Stopped

STOP 이전 데이터가 모두 client로 돌아올 때까지의 처리입니다.

Drain 뒤 재개 방식
항목설명
V4L2_DEC_CMD_STARTdecoder state를 유지하고 정상 재개
CAPTURE STREAMOFF/ON정상 재개, 남은 CAPTURE buffer 반환
OUTPUT STREAMOFF/ONpending source 반환 후 Seek 시작

선택한 queue 동작에 따라 state 보존과 seek 여부가 달라집니다.

Drain
=====

To ensure that all queued ``OUTPUT`` buffers have been processed and related
``CAPTURE`` buffers are given to the client, the client must follow the drain
sequence described below. After the drain sequence ends, the client has
received all decoded frames for all ``OUTPUT`` buffers queued before the
sequence was started.

1. Begin drain by issuing :c:func:`VIDIOC_DECODER_CMD`.

   * **Required fields:**

     ``cmd``
         set to ``V4L2_DEC_CMD_STOP``.

     ``flags``
         set to 0.

     ``pts``
         set to 0.

   .. warning::

      The sequence can be only initiated if both ``OUTPUT`` and ``CAPTURE``
      queues are streaming. For compatibility reasons, the call to
      :c:func:`VIDIOC_DECODER_CMD` will not fail even if any of the queues is
      not streaming, but at the same time it will not initiate the `Drain`
      sequence and so the steps described below would not be applicable.

2. Any ``OUTPUT`` buffers queued by the client before the
   :c:func:`VIDIOC_DECODER_CMD` was issued will be processed and decoded as
   normal. The client must continue to handle both queues independently,
   similarly to normal decode operation. This includes:

   * handling any operations triggered as a result of processing those buffers,
     such as the `Dynamic Resolution Change` sequence, before continuing with
     the drain sequence,

   * queuing and dequeuing ``CAPTURE`` buffers, until a buffer marked with the
     ``V4L2_BUF_FLAG_LAST`` flag is dequeued,

     .. warning::

        The last buffer may be empty (with :c:type:`v4l2_buffer`
        ``bytesused`` = 0) and in that case it must be ignored by the client,
        as it does not contain a decoded frame.

     .. note::

        Any attempt to dequeue more ``CAPTURE`` buffers beyond the buffer
        marked with ``V4L2_BUF_FLAG_LAST`` will result in a -EPIPE error from
        :c:func:`VIDIOC_DQBUF`.

   * dequeuing processed ``OUTPUT`` buffers, until all the buffers queued
     before the ``V4L2_DEC_CMD_STOP`` command are dequeued,

   * dequeuing the ``V4L2_EVENT_EOS`` event, if the client subscribed to it.

   .. note::

      For backwards compatibility, the decoder will signal a ``V4L2_EVENT_EOS``
      event when the last frame has been decoded and all frames are ready to be
      dequeued. It is a deprecated behavior and the client must not rely on it.
      The ``V4L2_BUF_FLAG_LAST`` buffer flag should be used instead.

3. Once all the ``OUTPUT`` buffers queued before the ``V4L2_DEC_CMD_STOP`` call
   are dequeued and the last ``CAPTURE`` buffer is dequeued, the decoder is
   stopped and it will accept, but not process, any newly queued ``OUTPUT``
   buffers until the client issues any of the following operations:

   * ``V4L2_DEC_CMD_START`` - the decoder will not be reset and will resume
     operation normally, with all the state from before the drain,

   * a pair of :c:func:`VIDIOC_STREAMOFF` and :c:func:`VIDIOC_STREAMON` on the
     ``CAPTURE`` queue - the decoder will resume the operation normally,
     however any ``CAPTURE`` buffers still in the queue will be returned to the
     client,

   * a pair of :c:func:`VIDIOC_STREAMOFF` and :c:func:`VIDIOC_STREAMON` on the
     ``OUTPUT`` queue - any pending source buffers will be returned to the
     client and the `Seek` sequence will be triggered.

.. note::

   Once the drain sequence is initiated, the client needs to drive it to
   completion, as described by the steps above, unless it aborts the process by
   issuing :c:func:`VIDIOC_STREAMOFF` on any of the ``OUTPUT`` or ``CAPTURE``
   queues.  The client is not allowed to issue ``V4L2_DEC_CMD_START`` or
   ``V4L2_DEC_CMD_STOP`` again while the drain sequence is in progress and they
   will fail with -EBUSY error code if attempted.

   Although not mandatory, the availability of decoder commands may be queried
   using :c:func:`VIDIOC_TRY_DECODER_CMD`.

End of Stream과 format commit point

1091-1127

decoder가 stream 내부의 end-of-stream 표시를 만나면 client의 초기 `VIDIOC_DECODER_CMD` 호출을 생략한 채 Drain sequence를 시작합니다. client는 나머지 drain 절차를 그대로 처리해야 합니다.

format 설정과 buffer 할당은 decoder 동작을 확정하는 commit point입니다. OUTPUT format을 설정하면 CAPTURE가 광고하는 format 집합과 현재 CAPTURE format이 바뀔 수 있으므로 이전 설정 보존을 기대해서는 안 됩니다. CAPTURE ENUM_FMT는 항상 현재 OUTPUT format이 지원하는 format만 반환합니다.

CAPTURE format 설정은 OUTPUT format 목록을 바꾸지 않습니다. 현재 OUTPUT과 호환되지 않는 CAPTURE format을 요청하면 decoder가 지원 format으로 조정합니다. OUTPUT ENUM_FMT는 CAPTURE와 무관하게 전체 coded format을 반환합니다. 어느 queue든 buffer가 할당된 동안 OUTPUT format을 바꿀 수 없으며 driver는 `-EBUSY`를 반환합니다. 따라서 format 설정과 할당은 언제나 master인 OUTPUT queue에서 시작해야 합니다.

Format commit 규칙
항목설명
OUTPUT S_FMTCAPTURE 지원 목록과 현재 CAPTURE format을 바꿀 수 있음
CAPTURE ENUM_FMT현재 OUTPUT format이 지원하는 항목만 반환
CAPTURE S_FMTOUTPUT 목록은 불변, 비호환 요청은 지원 format으로 조정
OUTPUT ENUM_FMT현재 CAPTURE와 무관한 전체 coded format 반환
Buffer 할당 중 OUTPUT S_FMT허용되지 않으며 -EBUSY

OUTPUT이 CAPTURE 지원 집합을 지배하는 다섯 가지 규칙입니다.

Format과 buffer commit 순서
OUTPUT coded format 설정현재 stream에 맞는 CAPTURE raw format 열거CAPTURE format과 selection 설정OUTPUT/CAPTURE buffer 할당할당 중에는 OUTPUT format 변경 금지

master queue인 OUTPUT에서 협상을 시작해야 합니다.

End of Stream
=============

If the decoder encounters an end of stream marking in the stream, the decoder
will initiate the `Drain` sequence, which the client must handle as described
above, skipping the initial :c:func:`VIDIOC_DECODER_CMD`.

Commit Points
=============

Setting formats and allocating buffers trigger changes in the behavior of the
decoder.

1. Setting the format on the ``OUTPUT`` queue may change the set of formats
   supported/advertised on the ``CAPTURE`` queue. In particular, it also means
   that the ``CAPTURE`` format may be reset and the client must not rely on the
   previously set format being preserved.

2. Enumerating formats on the ``CAPTURE`` queue always returns only formats
   supported for the current ``OUTPUT`` format.

3. Setting the format on the ``CAPTURE`` queue does not change the list of
   formats available on the ``OUTPUT`` queue. An attempt to set a ``CAPTURE``
   format that is not supported for the currently selected ``OUTPUT`` format
   will result in the decoder adjusting the requested ``CAPTURE`` format to a
   supported one.

4. Enumerating formats on the ``OUTPUT`` queue always returns the full set of
   supported coded formats, irrespectively of the current ``CAPTURE`` format.

5. While buffers are allocated on any of the ``OUTPUT`` or ``CAPTURE`` queues,
   the client must not change the format on the ``OUTPUT`` queue. Drivers will
   return the -EBUSY error code for any such format change attempt.

To summarize, setting formats and allocation must always start with the
``OUTPUT`` queue and the ``OUTPUT`` queue is the master that governs the
set of supported formats for the ``CAPTURE`` queue.