Lines Matching +full:simple +full:- +full:framebuffer
1 .. SPDX-License-Identifier: GPL-2.0
8 defined radio receiver. In addition a simple framebuffer device is available for
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
43 ----------------------
46 device with webcam, TV, S-Video and HDMI inputs, a video output device with
47 S-Video and HDMI outputs, one vbi capture device, one vbi output device, one
53 - n_devs:
58 - node_types:
64 - bit 0: Video Capture node
65 - bit 2-3: VBI Capture node: 0 = none, 1 = raw vbi, 2 = sliced vbi, 3 = both
66 - bit 4: Radio Receiver node
67 - bit 5: Software Defined Radio Receiver node
68 - bit 8: Video Output node
69 - bit 10-11: VBI Output node: 0 = none, 1 = raw vbi, 2 = sliced vbi, 3 = both
70 - bit 12: Radio Transmitter node
71 - bit 16: Framebuffer for testing overlays
77 .. code-block:: none
81 - num_inputs:
87 - input_types:
92 pair gives the type and bits 0-1 map to input 0, bits 2-3 map to input 1,
93 30-31 map to input 15. Each pair of bits has the following meaning:
95 - 00: this is a webcam input
96 - 01: this is a TV tuner input
97 - 10: this is an S-Video input
98 - 11: this is an HDMI input
101 tuner, inputs 1-3 are S-Video inputs and inputs 4-7 are HDMI inputs you
104 .. code-block:: none
108 - num_outputs:
114 - output_types:
122 - 0: this is an S-Video output
123 - 1: this is an HDMI output
125 So to create a video output device with 8 outputs where outputs 0-3 are
126 S-Video outputs and outputs 4-7 are HDMI outputs you would use the
129 .. code-block:: none
133 - vid_cap_nr:
136 The default is -1 which will just take the first free number. This allows
139 .. code-block:: none
148 - vid_out_nr:
151 The default is -1 which will just take the first free number.
153 - vbi_cap_nr:
156 The default is -1 which will just take the first free number.
158 - vbi_out_nr:
161 The default is -1 which will just take the first free number.
163 - radio_rx_nr:
166 The default is -1 which will just take the first free number.
168 - radio_tx_nr:
171 device. The default is -1 which will just take the first free number.
173 - sdr_cap_nr:
176 The default is -1 which will just take the first free number.
178 - ccs_cap_mode:
186 The value is either -1 (controlled by the user) or a set of three bits,
189 - bit 0:
193 - bit 1:
198 - bit 2:
203 very simple and low-quality. Simplicity and speed were
210 - ccs_out_mode:
218 The value is either -1 (controlled by the user) or a set of three bits,
221 - bit 0:
226 - bit 1:
231 - bit 2:
236 very simple and low-quality. Simplicity and speed were
239 - multiplanar:
241 select whether each device instance supports multi-planar formats,
242 and thus the V4L2 multi-planar API. By default device instances are
243 single-planar.
247 - 1: this is a single-planar instance.
248 - 2: this is a multi-planar instance.
250 - vivid_debug:
254 - no_error_inj:
257 needed in order to run a tool like v4l2-compliance. Tools like that
260 all tests that v4l2-compliance is doing will fail afterwards.
268 - allocators:
273 - 0: vmalloc
274 - 1: dma-contig
283 -------------
288 four inputs are configured: a webcam, a TV tuner, an S-Video and an HDMI
295 but the long-term behavior is exactly following the framerate. So a
314 TV and S-Video Inputs
317 The only difference between the TV and S-Video input is that the TV has a
320 These inputs support audio inputs as well: one TV and one Line-In. They
340 The initially selected colorspace when you switch to the TV or S-Video input
341 will be SMPTE-170M.
349 The TV 'tuner' supports a frequency range of 44-958 MHz. Channels are available
351 will be in color for the +/- 0.25 MHz around it, and in grayscale for
352 +/- 1 MHz around the channel. Beyond that it is just noise. The VIDIOC_G_TUNER
353 ioctl will return 100% signal strength for +/- 0.25 MHz and 50% for +/- 1 MHz.
357 The audio subchannels that are returned are MONO for the +/- 1 MHz range around
358 a valid channel frequency. When the frequency is within +/- 0.25 MHz of the
373 The HDMI inputs supports all CEA-861 and DMT timings, both progressive and
381 less than or equal to 720x576 the colorspace is set to SMPTE-170M, for
382 others it is set to REC-709 (CEA-861 timings) or sRGB (VESA DMT timings).
393 For HDMI inputs it is possible to set the EDID. By default a simple EDID
405 ------------
409 information), but by default two outputs are configured: an S-Video and an
416 S-Video Output
419 This output supports audio outputs as well: "Line-Out 1" and "Line-Out 2".
420 The S-Video output supports all TV standards.
424 The initially selected colorspace when you switch to the TV or S-Video input
425 will be SMPTE-170M.
431 The HDMI output supports all CEA-861 and DMT timings, both progressive and
437 less than or equal to 720x576 the colorspace is set to SMPTE-170M, for
438 others it is set to REC-709 (CEA-861 timings) or sRGB (VESA DMT timings).
451 -----------
461 Aspect Ratio control setting and teletext pages 100-159, one page per frame.
463 The VBI device will only work for the S-Video and TV inputs, it will give
468 ----------
477 The VBI device will only work for the S-Video output, it will give
482 --------------
487 - FM: 64 MHz - 108 MHz
488 - AM: 520 kHz - 1710 kHz
489 - SW: 2300 kHz - 26.1 MHz
493 frequency until it becomes 0% at +/- 50 kHz (FM) or 5 kHz (AM/SW) from the
498 modes. In the 'Controls' mode the RDS information is stored in read-only
503 The RDS signal is 'detected' for +/- 12.5 kHz around the channel frequency,
506 blocks if you are +/- 12.5 kHz from the channel frequency. All four errors
518 -----------------
523 - FM: 64 MHz - 108 MHz
524 - AM: 520 kHz - 1710 kHz
525 - SW: 2300 kHz - 26.1 MHz
536 -------------------------------
540 - 300 kHz
541 - 900 kHz - 2800 kHz
542 - 3200 kHz
544 The RF tuner supports 50 MHz - 2000 MHz.
546 The generated data contains the In-phase and Quadrature components of a
551 --------
557 User Controls - Test Controls
564 Both menu controls also have a non-zero minimum control value. These features
569 User Controls - Video Capture
595 User Controls - Audio
617 - Test Pattern:
624 - OSD Text Mode:
630 - Horizontal Movement:
635 - Vertical Movement:
639 - Show Border:
641 show a two-pixel wide border at the edge of the actual image,
644 - Show Square:
651 - Insert SAV Code in Image:
657 - Insert EAV Code in Image:
667 - Sensor Flipped Horizontally:
673 - Sensor Flipped Vertically:
679 - Standard Aspect Ratio:
682 S-Video input should be 4x3, 16x9 or anamorphic widescreen. This may
685 - DV Timings Aspect Ratio:
691 - Timestamp Source:
695 - Colorspace:
707 - Transfer Function:
719 - Y'CbCr Encoding:
728 - Quantization:
736 - Limited RGB Range (16-235):
744 - Apply Alpha To Red Only:
749 - Enable Capture Cropping:
752 the ccs_cap_mode module option is set to the default value of -1 and if
755 - Enable Capture Composing:
759 -1 and if the no_error_inj module option is set to 0 (the default).
761 - Enable Capture Scaler:
765 module option is set to the default value of -1 and if the no_error_inj
768 - Maximum EDID Blocks:
775 - Fill Percentage of Frame:
789 - Enable Output Cropping:
792 the ccs_out_mode module option is set to the default value of -1 and if
795 - Enable Output Composing:
799 -1 and if the no_error_inj module option is set to 0 (the default).
801 - Enable Output Scaler:
805 module option is set to the default value of -1 and if the no_error_inj
814 - Standard Signal Mode:
822 - Standard:
833 - DV Timings Signal Mode:
842 - DV Timings:
856 - Wrap Sequence Number:
861 - Wrap Timestamp:
866 - Percentage of Dropped Buffers:
871 - Disconnect:
877 - Inject V4L2_BUF_FLAG_ERROR:
883 - Inject VIDIOC_REQBUFS Error:
887 queue_setup() op will return -EINVAL.
889 - Inject VIDIOC_QBUF Error:
893 precise: the videobuf2 buf_prepare() op will return -EINVAL.
895 - Inject VIDIOC_STREAMON Error:
899 start_streaming() op will return -EINVAL.
901 - Inject Fatal Streaming Error:
912 - Interlaced VBI Format:
921 - Rx RGB Quantization Range:
924 input. This combines with the Vivid 'Limited RGB Range (16-235)'
928 range and selecting the opposite in the 'Limited RGB Range (16-235)'
932 - Tx RGB Quantization Range:
938 - Transmit Mode:
940 sets the transmit mode of the HDMI output to HDMI or DVI-D. This
944 - Display Present:
953 - RDS Reception:
957 - RDS Program Type:
960 - RDS PS Name:
963 - RDS Radio Text:
966 - RDS Traffic Announcement:
969 - RDS Traffic Program:
972 - RDS Music:
974 these are all read-only controls. If RDS Rx I/O Mode is set to
983 - Radio HW Seek Mode:
987 range or wrap-around or if it is selectable by the user.
989 - Radio Programmable HW Seek:
995 - Generate RBDS Instead of RDS:
998 RDS) data instead of RDS (European-style RDS). This affects only the
1001 - RDS Rx I/O Mode:
1011 - RDS Program ID:
1014 - RDS Program Type:
1017 - RDS PS Name:
1020 - RDS Radio Text:
1023 - RDS Stereo:
1026 - RDS Artificial Head:
1029 - RDS Compressed:
1032 - RDS Dynamic PTY:
1035 - RDS Traffic Announcement:
1038 - RDS Traffic Program:
1041 - RDS Music:
1046 - RDS Tx I/O Mode:
1054 --------------------------
1059 and VBI looping is only supported between S-Video and HDMI inputs and outputs.
1060 VBI is only valid for S-Video as it makes no sense for HDMI.
1076 Once enabled any video S-Video or HDMI input will show a static test pattern
1080 - the input type matches the output type. So the HDMI input cannot receive
1081 video from the S-Video output.
1083 - the video resolution of the video input must match that of the video output.
1084 So it is not possible to loop a 50 Hz (720x576) S-Video output to a 60 Hz
1085 (720x480) S-Video input, or a 720p60 HDMI output to a 1080p30 input.
1087 - the pixel formats must be identical on both sides. Otherwise the driver would
1090 - the field settings must be identical on both sides. Same reason as above:
1099 - field settings V4L2_FIELD_SEQ_TB/BT are not supported. While it is possible to
1104 - on the input side the "Standard Signal Mode" for the S-Video input or the
1136 ----------------------------
1147 only applies to the TV/S-Video/HDMI inputs and outputs. The reason is that
1162 The scaler is a simple scaler that uses the Coarse Bresenham algorithm. It's
1170 -------
1182 the driver instances are single-planar. This can be changed by setting the
1187 will have a plane that has a non-zero data_offset of 128 bytes. It is rare for
1188 data_offset to be non-zero, so this is a useful feature for testing applications.
1194 ---------------
1200 option the vivid driver will create a simple framebuffer device that can be
1215 In addition, the pixelformat of the capture format and that of the framebuffer
1220 instances: the first with a framebuffer enabled. You configure the capture
1221 overlay of the second instance to use the framebuffer of the first, then
1224 to see the blended framebuffer overlay that's being written to by the second
1227 .. code-block:: none
1230 $ v4l2-ctl -d1 --find-fb
1231 /dev/fb1 is the framebuffer associated with base address 0x12800000
1232 $ sudo v4l2-ctl -d2 --set-fbuf fb=1
1233 $ v4l2-ctl -d1 --set-fbuf fb=1
1234 $ v4l2-ctl -d0 --set-fmt-video=pixelformat='AR15'
1235 $ v4l2-ctl -d1 --set-fmt-video-out=pixelformat='AR15'
1236 $ v4l2-ctl -d2 --set-fmt-video=pixelformat='AR15'
1237 $ v4l2-ctl -d0 -i2
1238 $ v4l2-ctl -d2 -i2
1239 $ v4l2-ctl -d2 -c horizontal_movement=4
1240 $ v4l2-ctl -d1 --overlay=1
1241 $ v4l2-ctl -d1 -c loop_video=1
1242 $ v4l2-ctl -d2 --stream-mmap --overlay=1
1246 .. code-block:: none
1248 $ v4l2-ctl -d1 --stream-out-mmap
1252 .. code-block:: none
1262 --------------
1270 - bitmap clipping,
1271 - list clipping (up to 16 rectangles)
1272 - chromakey
1273 - source chromakey
1274 - global alpha
1275 - local alpha
1276 - local inverse alpha
1279 pixelformat of the capture format and that of the framebuffer must be the
1283 framebuffer by setting flag 0x10000 in the node_types module option. The
1284 created framebuffer has a size of 720x576 and supports ARGB 1:5:5:5 and
1295 ----------------------------------
1314 ------------------------
1318 - Add a virtual alsa driver to test audio
1319 - Add virtual sub-devices and media controller support
1320 - Some support for testing compressed video
1321 - Add support to loop raw VBI output to raw VBI input
1322 - Add support to loop teletext sliced VBI output to VBI input
1323 - Fix sequence/field numbering when looping of video with alternate fields
1324 - Add support for V4L2_CID_BG_COLOR for video outputs
1325 - Add ARGB888 overlay support: better testing of the alpha channel
1326 - Improve pixel aspect support in the tpg code by passing a real v4l2_fract
1327 - Use per-queue locks and/or per-device locks to improve throughput
1328 - Add support to loop from a specific output to a specific input across
1330 - The SDR radio should use the same 'frequencies' for stations as the normal
1333 - Make a thread for the RDS generation, that would help in particular for the
1334 "Controls" RDS Rx I/O Mode as the read-only RDS controls could be updated
1335 in real-time.
1336 - Changing the EDID should cause hotplug detect emulation to happen.