Lines Matching +full:scaled +full:- +full:output +full:- +full:hz
1 .. SPDX-License-Identifier: GPL-2.0
7 output, vbi capture and output, metadata capture and output, radio receivers and
9 simple framebuffer device is available for testing capture and output overlays.
13 Each input can be a webcam, TV capture device, S-Video capture device or an HDMI
14 capture device. Each output can be an S-Video output device or an HDMI output
23 - Support for read()/write(), MMAP, USERPTR and DMABUF streaming I/O.
24 - A large list of test patterns and variations thereof
25 - Working brightness, contrast, saturation and hue controls
26 - Support for the alpha color component
27 - Full colorspace support, including limited/full RGB range
28 - All possible control types are present
29 - Support for various pixel aspect ratios and video aspect ratios
30 - Error injection to test what happens if errors occur
31 - Supports crop/compose/scale in any combination for both input and output
32 - Can emulate up to 4K resolutions
33 - All Field settings are supported for testing interlaced capturing
34 - Supports all standard YUV and RGB formats, including two multiplanar YUV formats
35 - Raw and Sliced VBI capture and output support
36 - Radio receiver and transmitter support, including RDS support
37 - Software defined radio (SDR) support
38 - Capture and output overlay support
39 - Metadata capture and output support
40 - Touch capture support
45 ----------------------
48 device with webcam, TV, S-Video and HDMI inputs, a video output device with
49 S-Video and HDMI outputs, one vbi capture device, one vbi output device, one
55 - n_devs:
60 - node_types:
66 - bit 0: Video Capture node
67 - bit 2-3: VBI Capture node: 0 = none, 1 = raw vbi, 2 = sliced vbi, 3 = both
68 - bit 4: Radio Receiver node
69 - bit 5: Software Defined Radio Receiver node
70 - bit 8: Video Output node
71 - bit 10-11: VBI Output node: 0 = none, 1 = raw vbi, 2 = sliced vbi, 3 = both
72 - bit 12: Radio Transmitter node
73 - bit 16: Framebuffer for testing overlays
74 - bit 17: Metadata Capture node
75 - bit 18: Metadata Output node
76 - bit 19: Touch Capture node
79 device, the second two with just one video output device you would pass
82 .. code-block:: none
86 - num_inputs:
92 - input_types:
97 pair gives the type and bits 0-1 map to input 0, bits 2-3 map to input 1,
98 30-31 map to input 15. Each pair of bits has the following meaning:
100 - 00: this is a webcam input
101 - 01: this is a TV tuner input
102 - 10: this is an S-Video input
103 - 11: this is an HDMI input
106 tuner, inputs 1-3 are S-Video inputs and inputs 4-7 are HDMI inputs you
109 .. code-block:: none
113 - num_outputs:
116 are created for each video output device. At most 16 outputs can be
119 - output_types:
121 the output types for each instance, the default is 0x02. This defines
122 what the type of each output is when the outputs are created for each
124 gives the type and bit 0 maps to output 0, bit 1 maps to output 1, bit
125 15 maps to output 15. The meaning of each bit is as follows:
127 - 0: this is an S-Video output
128 - 1: this is an HDMI output
130 So to create a video output device with 8 outputs where outputs 0-3 are
131 S-Video outputs and outputs 4-7 are HDMI outputs you would use the
134 .. code-block:: none
138 - vid_cap_nr:
141 The default is -1 which will just take the first free number. This allows
144 .. code-block:: none
153 - vid_out_nr:
155 give the desired videoX start number for each video output device.
156 The default is -1 which will just take the first free number.
158 - vbi_cap_nr:
161 The default is -1 which will just take the first free number.
163 - vbi_out_nr:
165 give the desired vbiX start number for each vbi output device.
166 The default is -1 which will just take the first free number.
168 - radio_rx_nr:
171 The default is -1 which will just take the first free number.
173 - radio_tx_nr:
176 device. The default is -1 which will just take the first free number.
178 - sdr_cap_nr:
181 The default is -1 which will just take the first free number.
183 - meta_cap_nr:
186 The default is -1 which will just take the first free number.
188 - meta_out_nr:
190 give the desired videoX start number for each metadata output device.
191 The default is -1 which will just take the first free number.
193 - touch_cap_nr:
195 give the desired v4l-touchX start number for each touch capture device.
196 The default is -1 which will just take the first free number.
198 - ccs_cap_mode:
206 The value is either -1 (controlled by the user) or a set of three bits,
209 - bit 0:
213 - bit 1:
218 - bit 2:
223 very simple and low-quality. Simplicity and speed were
230 - ccs_out_mode:
232 specify the allowed video output crop/compose/scaling combination
233 for each driver instance. Video output devices can have any combination
238 The value is either -1 (controlled by the user) or a set of three bits,
241 - bit 0:
246 - bit 1:
251 - bit 2:
256 very simple and low-quality. Simplicity and speed were
259 - multiplanar:
261 select whether each device instance supports multi-planar formats,
262 and thus the V4L2 multi-planar API. By default device instances are
263 single-planar.
267 - 1: this is a single-planar instance.
268 - 2: this is a multi-planar instance.
270 - vivid_debug:
274 - no_error_inj:
277 needed in order to run a tool like v4l2-compliance. Tools like that
280 all tests that v4l2-compliance is doing will fail afterwards.
288 - allocators:
293 - 0: vmalloc
294 - 1: dma-contig
296 - cache_hints:
298 specifies if the device should set queues' user-space cache and memory
302 - 0: forbid hints
303 - 1: allow hints
312 -------------
317 four inputs are configured: a webcam, a TV tuner, an S-Video and an HDMI
322 available. The jitter will be around 1 jiffie (that depends on the HZ
324 but the long-term behavior is exactly following the framerate. So a
325 framerate of 59.94 Hz is really different from 60 Hz. If the framerate
326 exceeds your kernel's HZ value, then you will get dropped frames, but the
343 TV and S-Video Inputs
346 The only difference between the TV and S-Video input is that the TV has a
349 These inputs support audio inputs as well: one TV and one Line-In. They
358 visible. For 50 Hz standards the top field is the oldest and the bottom field
359 is the newest in time. For 60 Hz standards that is reversed: the bottom field
363 contain the top field for 50 Hz standards and the bottom field for 60 Hz
369 The initially selected colorspace when you switch to the TV or S-Video input
370 will be SMPTE-170M.
376 video that will need to be scaled accordingly.
378 The TV 'tuner' supports a frequency range of 44-958 MHz. Channels are available
380 will be in color for the +/- 0.25 MHz around it, and in grayscale for
381 +/- 1 MHz around the channel. Beyond that it is just noise. The VIDIOC_G_TUNER
382 ioctl will return 100% signal strength for +/- 0.25 MHz and 50% for +/- 1 MHz.
386 The audio subchannels that are returned are MONO for the +/- 1 MHz range around
387 a valid channel frequency. When the frequency is within +/- 0.25 MHz of the
402 The HDMI inputs supports all CEA-861 and DMT timings, both progressive and
410 less than or equal to 720x576 the colorspace is set to SMPTE-170M, for
411 others it is set to REC-709 (CEA-861 timings) or sRGB (VESA DMT timings).
433 Video Output
434 ------------
436 The video output device can be configured by using the module options
438 information), but by default two outputs are configured: an S-Video and an
439 HDMI input, one output for each output type. Those are described in more detail
445 S-Video Output argument
448 This output supports audio outputs as well: "Line-Out 1" and "Line-Out 2".
449 The S-Video output supports all TV standards.
451 This output supports all combinations of the field setting.
453 The initially selected colorspace when you switch to the TV or S-Video input
454 will be SMPTE-170M.
457 HDMI Output argument
460 The HDMI output supports all CEA-861 and DMT timings, both progressive and
464 The initially selected colorspace when you switch to the HDMI output or
466 less than or equal to 720x576 the colorspace is set to SMPTE-170M, for
467 others it is set to REC-709 (CEA-861 timings) or sRGB (VESA DMT timings).
473 An HDMI output has a valid EDID which can be obtained through VIDIOC_G_EDID.
480 -----------
485 cases the driver will generate valid VBI data: for 60 Hz standards it will
488 The XDS stream will give the current time once a minute. For 50 Hz standards
490 Aspect Ratio control setting and teletext pages 100-159, one page per frame.
492 The VBI device will only work for the S-Video and TV inputs, it will give
496 VBI Output
497 ----------
499 There are three types of VBI output devices: those that only support raw
503 The sliced VBI output supports the Wide Screen Signal and the teletext signal
504 for 50 Hz standards and Closed Captioning + XDS for 60 Hz standards.
506 The VBI device will only work for the S-Video output, it will give
507 back an error if the current output is HDMI.
511 --------------
516 - FM: 64 MHz - 108 MHz
517 - AM: 520 kHz - 1710 kHz
518 - SW: 2300 kHz - 26.1 MHz
522 frequency until it becomes 0% at +/- 50 kHz (FM) or 5 kHz (AM/SW) from the
527 modes. In the 'Controls' mode the RDS information is stored in read-only
532 The RDS signal is 'detected' for +/- 12.5 kHz around the channel frequency,
535 blocks if you are +/- 12.5 kHz from the channel frequency. All four errors
547 -----------------
552 - FM: 64 MHz - 108 MHz
553 - AM: 520 kHz - 1710 kHz
554 - SW: 2300 kHz - 26.1 MHz
565 -------------------------------
569 - 300 kHz
570 - 900 kHz - 2800 kHz
571 - 3200 kHz
573 The RF tuner supports 50 MHz - 2000 MHz.
575 The generated data contains the In-phase and Quadrature components of a
580 ----------------
589 Metadata Output
590 ---------------
592 The Metadata output can be used to set brightness, contrast, saturation and hue.
594 The Metadata device will only work for the Webcam output, it will give
599 -------------
607 --------
613 User Controls - Test Controls
620 Both menu controls also have a non-zero minimum control value. These features
625 User Controls - Video Capture
651 User Controls - Audio
654 The following controls are specific to video capture and output and radio
673 - Test Pattern:
680 - OSD Text Mode:
686 - Horizontal Movement:
691 - Vertical Movement:
695 - Show Border:
697 show a two-pixel wide border at the edge of the actual image,
700 - Show Square:
707 - Insert SAV Code in Image:
713 - Insert EAV Code in Image:
723 - Sensor Flipped Horizontally:
729 - Sensor Flipped Vertically:
735 - Standard Aspect Ratio:
738 S-Video input should be 4x3, 16x9 or anamorphic widescreen. This may
741 - DV Timings Aspect Ratio:
747 - Timestamp Source:
751 - Colorspace:
763 - Transfer Function:
775 - Y'CbCr Encoding:
784 - Quantization:
792 - Limited RGB Range (16-235):
800 - Apply Alpha To Red Only:
805 - Enable Capture Cropping:
808 the ccs_cap_mode module option is set to the default value of -1 and if
811 - Enable Capture Composing:
815 -1 and if the no_error_inj module option is set to 0 (the default).
817 - Enable Capture Scaler:
821 module option is set to the default value of -1 and if the no_error_inj
824 - Maximum EDID Blocks:
831 - Fill Percentage of Frame:
840 Output Feature Selection Controls
843 These controls are all specific to video output.
845 - Enable Output Cropping:
848 the ccs_out_mode module option is set to the default value of -1 and if
851 - Enable Output Composing:
855 -1 and if the no_error_inj module option is set to 0 (the default).
857 - Enable Output Scaler:
861 module option is set to the default value of -1 and if the no_error_inj
870 - Standard Signal Mode:
878 - Standard:
889 - DV Timings Signal Mode:
898 - DV Timings:
909 capture and output streams and for the SDR capture device except for the
912 - Wrap Sequence Number:
917 - Wrap Timestamp:
922 - Percentage of Dropped Buffers:
927 - Disconnect:
933 - Inject V4L2_BUF_FLAG_ERROR:
939 - Inject VIDIOC_REQBUFS Error:
943 queue_setup() op will return -EINVAL.
945 - Inject VIDIOC_QBUF Error:
949 precise: the videobuf2 buf_prepare() op will return -EINVAL.
951 - Inject VIDIOC_STREAMON Error:
955 start_streaming() op will return -EINVAL.
957 - Inject Fatal Streaming Error:
968 - Interlaced VBI Format:
977 - Rx RGB Quantization Range:
980 input. This combines with the Vivid 'Limited RGB Range (16-235)'
984 range and selecting the opposite in the 'Limited RGB Range (16-235)'
988 - Tx RGB Quantization Range:
991 output. It is currently not used for anything in vivid, but most HDMI
994 - Transmit Mode:
996 sets the transmit mode of the HDMI output to HDMI or DVI-D. This
1000 - Display Present:
1002 sets the presence of a "display" on the HDMI output. This affects
1009 - RDS Reception:
1013 - RDS Program Type:
1016 - RDS PS Name:
1019 - RDS Radio Text:
1022 - RDS Traffic Announcement:
1025 - RDS Traffic Program:
1028 - RDS Music:
1030 these are all read-only controls. If RDS Rx I/O Mode is set to
1039 - Radio HW Seek Mode:
1043 range or wrap-around or if it is selectable by the user.
1045 - Radio Programmable HW Seek:
1051 - Generate RBDS Instead of RDS:
1054 RDS) data instead of RDS (European-style RDS). This affects only the
1057 - RDS Rx I/O Mode:
1067 - RDS Program ID:
1070 - RDS Program Type:
1073 - RDS PS Name:
1076 - RDS Radio Text:
1079 - RDS Stereo:
1082 - RDS Artificial Head:
1085 - RDS Compressed:
1088 - RDS Dynamic PTY:
1091 - RDS Traffic Announcement:
1094 - RDS Traffic Program:
1097 - RDS Music:
1102 - RDS Tx I/O Mode:
1111 - Generate PTS
1115 - Generate SCR
1120 --------------------------
1122 The vivid driver supports looping of video output to video input, VBI output
1123 to VBI input and RDS output to RDS input. For video/VBI looping this emulates
1124 as if a cable was hooked up between the output and input connector. So video
1125 and VBI looping is only supported between S-Video and HDMI inputs and outputs.
1126 VBI is only valid for S-Video as it makes no sense for HDMI.
1142 Once enabled any video S-Video or HDMI input will show a static test pattern
1143 until the video output has started. At that time the video output will be
1146 - the input type matches the output type. So the HDMI input cannot receive
1147 video from the S-Video output.
1149 - the video resolution of the video input must match that of the video output.
1150 So it is not possible to loop a 50 Hz (720x576) S-Video output to a 60 Hz
1151 (720x480) S-Video input, or a 720p60 HDMI output to a 1080p30 input.
1153 - the pixel formats must be identical on both sides. Otherwise the driver would
1156 - the field settings must be identical on both sides. Same reason as above:
1159 Bottom' when the output video is set to 'Field Alternate'. This combination,
1165 - field settings V4L2_FIELD_SEQ_TB/BT are not supported. While it is possible to
1170 - on the input side the "Standard Signal Mode" for the S-Video input or the
1181 output must be configured for sliced VBI. The VBI capture side can be configured
1182 for either raw or sliced VBI. Note that at the moment only CC/XDS (60 Hz formats)
1183 and WSS (50 Hz formats) VBI data is looped. Teletext VBI data is not looped.
1202 ----------------------------
1213 only applies to the TV/S-Video/HDMI inputs and outputs. The reason is that
1236 -------
1248 the driver instances are single-planar. This can be changed by setting the
1253 will have a plane that has a non-zero data_offset of 128 bytes. It is rare for
1254 data_offset to be non-zero, so this is a useful feature for testing applications.
1256 Video output will also honor any data_offset that the application set.
1260 ---------------
1289 the output overlay for the video output, turn on video looping and capture
1293 .. code-block:: none
1296 $ v4l2-ctl -d1 --find-fb
1298 $ sudo v4l2-ctl -d2 --set-fbuf fb=1
1299 $ v4l2-ctl -d1 --set-fbuf fb=1
1300 $ v4l2-ctl -d0 --set-fmt-video=pixelformat='AR15'
1301 $ v4l2-ctl -d1 --set-fmt-video-out=pixelformat='AR15'
1302 $ v4l2-ctl -d2 --set-fmt-video=pixelformat='AR15'
1303 $ v4l2-ctl -d0 -i2
1304 $ v4l2-ctl -d2 -i2
1305 $ v4l2-ctl -d2 -c horizontal_movement=4
1306 $ v4l2-ctl -d1 --overlay=1
1307 $ v4l2-ctl -d1 -c loop_video=1
1308 $ v4l2-ctl -d2 --stream-mmap --overlay=1
1312 .. code-block:: none
1314 $ v4l2-ctl -d1 --stream-out-mmap
1318 .. code-block:: none
1327 Output Overlay
1328 --------------
1330 Note: output overlays are primarily implemented in order to test the existing
1331 V4L2 output overlay API. Whether this API should be used for new drivers is
1334 This driver has support for an output overlay and is capable of:
1336 - bitmap clipping,
1337 - list clipping (up to 16 rectangles)
1338 - chromakey
1339 - source chromakey
1340 - global alpha
1341 - local alpha
1342 - local inverse alpha
1344 Output overlays are not supported for multiplanar formats. In addition, the
1348 Output overlays only work if the driver has been configured to create a
1361 ----------------------------------
1365 has that number of inputs. Each HDMI output will also create a
1368 this is the equivalent of hooking up each output device to an input port of
1369 the TV. Any remaining output devices remain unconnected.
1371 The EDID that each output reads reports a unique CEC physical address that is
1373 receiver has physical address A.B.0.0, then each output will see an EDID
1380 ------------------------
1384 - Add a virtual alsa driver to test audio
1385 - Add virtual sub-devices and media controller support
1386 - Some support for testing compressed video
1387 - Add support to loop raw VBI output to raw VBI input
1388 - Add support to loop teletext sliced VBI output to VBI input
1389 - Fix sequence/field numbering when looping of video with alternate fields
1390 - Add support for V4L2_CID_BG_COLOR for video outputs
1391 - Add ARGB888 overlay support: better testing of the alpha channel
1392 - Improve pixel aspect support in the tpg code by passing a real v4l2_fract
1393 - Use per-queue locks and/or per-device locks to improve throughput
1394 - Add support to loop from a specific output to a specific input across
1396 - The SDR radio should use the same 'frequencies' for stations as the normal
1399 - Make a thread for the RDS generation, that would help in particular for the
1400 "Controls" RDS Rx I/O Mode as the read-only RDS controls could be updated
1401 in real-time.
1402 - Changing the EDID should cause hotplug detect emulation to happen.