Lines Matching full:and
7 output, vbi capture and output, metadata capture and output, radio receivers and
8 transmitters, touch capture and a software defined radio receiver. In addition a
9 simple framebuffer device is available for testing capture and output overlays.
11 Up to 64 vivid instances can be created, each with up to 16 inputs and 16 outputs.
17 These inputs and outputs act exactly as a real hardware device would behave. This
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
29 - Support for various pixel aspect ratios and video aspect ratios
31 - Supports crop/compose/scale in any combination for both input and output
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
38 - Capture and output overlay support
39 - Metadata capture and output support
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
50 radio receiver device, one radio transmitter device and one SDR device.
52 The number of instances, devices, video inputs and outputs and their types are
90 and there must be at least one.
97 pair gives the type and bits 0-1 map to input 0, bits 2-3 map to input 1,
106 tuner, inputs 1-3 are S-Video inputs and inputs 4-7 are HDMI inputs you
117 created, and there must be at least one.
124 gives the type and bit 0 maps to output 0, bit 1 maps to output 1, bit
131 S-Video outputs and outputs 4-7 are HDMI outputs you would use the
202 of cropping, composing and scaling capabilities and this will tell the
223 very simple and low-quality. Simplicity and speed were
227 discrete framesizes and that is incompatible with cropping, composing
234 of cropping, composing and scaling capabilities and this will tell the
256 very simple and low-quality. Simplicity and speed were
262 and thus the V4L2 multi-planar API. By default device instances are
279 emulates a USB disconnect, making the device inaccessible and so
284 controls that select crop, compose and scale behavior are also
285 removed. Unless overridden by ccs_cap_mode and/or ccs_out_mode the
286 will default to enabling crop, compose and scaling.
298 specifies if the device should set queues' user-space cache and memory
306 the driver behavior and test your application with all sorts of permutations.
315 can be configured by using the module options num_inputs, input_types and
317 four inputs are configured: a webcam, a TV tuner, an S-Video and an HDMI
334 The webcam input supports three framesizes: 320x180, 640x360 and 1280x720. It
335 supports frames per second settings of 10, 15, 25, 30, 50 and 60 fps. Which ones
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
351 controls 'Standard Signal Mode' and 'Standard' determine what
358 visible. For 50 Hz standards the top field is the oldest and the bottom field
360 is the oldest and the top field is the newest in time.
363 contain the top field for 50 Hz standards and the bottom field for 60 Hz
374 Choices are '4x3', '16x9' which will give letterboxed widescreen video and
380 will be in color for the +/- 0.25 MHz around it, and in grayscale for
382 ioctl will return 100% signal strength for +/- 0.25 MHz and 50% for +/- 1 MHz.
402 The HDMI inputs supports all CEA-861 and DMT timings, both progressive and
403 interlaced, for pixelclock frequencies between 25 and 600 MHz. The field
405 field order is always top field first, and when you start capturing an
415 standard, and for all others a 1:1 pixel aspect ratio is returned.
437 num_outputs, output_types and ccs_out_mode (see section 1 for more detailed
438 information), but by default two outputs are configured: an S-Video and an
448 This output supports audio outputs as well: "Line-Out 1" and "Line-Out 2".
460 The HDMI output supports all CEA-861 and DMT timings, both progressive and
461 interlaced, for pixelclock frequencies between 25 and 600 MHz. The field
471 standard, and for all others a 1:1 pixel aspect ratio is returned.
483 (undecoded) VBI, those that only support sliced (decoded) VBI and those that
486 generate Closed Caption and XDS data. The closed caption stream will
487 alternate between "Hello world!" and "Closed captions test" every second.
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
500 (undecoded) VBI, those that only support sliced (decoded) VBI and those that
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.
520 Valid channels are emulated every 1 MHz for FM and every 100 kHz for AM and SW.
526 The FM receiver supports RDS as well, both using 'Block I/O' and 'Controls'
533 and the further the frequency is away from the valid frequency the more RDS
537 'ERROR', blocks marked 'INVALID' and dropped blocks.
540 0B group, and also radio text and the current time.
558 The FM transmitter supports RDS as well, both using 'Block I/O' and 'Controls'
560 using controls, and in 'Block I/O' mode the blocks are passed to the driver
575 The generated data contains the In-phase and Quadrature components of a
582 The Metadata capture generates UVC format metadata. The PTS and SCR are
592 The Metadata output can be used to set brightness, contrast, saturation and hue.
603 a large area being pressed on a touchpad), and simulating 16 simultaneous
610 each control and which devices support them.
616 The Button, Boolean, Integer 32 Bits, Integer 64 Bits, Menu, String, Bitmask and
618 control and the Integer Menu control both have 'holes' in their menu list,
630 The Brightness, Contrast, Saturation and Hue controls actually work and are
634 brightness range (minimum and maximum control values). Switching inputs will
638 The 'Gain, Automatic' and Gain controls can be used to test volatile controls:
639 if 'Gain, Automatic' is set, then the Gain control is volatile and changes
643 The 'Horizontal Flip' and 'Vertical Flip' controls can be used to flip the
654 The following controls are specific to video capture and output and radio
655 receivers and transmitters.
657 The 'Volume' and 'Mute' audio controls are typical for such devices to
658 control the volume and mute the audio. They don't actually do anything in
683 test pattern should be shown, and if so, whether only counters should
689 move to the left or right and at what speed.
703 displayed with the correct pixel and image aspect ratio corrections,
704 then the width and height of the square on the monitor should be
725 control and then move the image to the left hand side of the screen.
729 now fail and either loose sync or these video lines will shift.
739 the image is flipped horizontally and the
745 the image is flipped vertically and the
758 input should be the same as the source width and height ratio, or if
771 should really have 75% signal intensity and should not be affected
783 should really have 75% signal intensity and should not be affected
810 Quantization Range' control and can be used to test what happens if
822 the ccs_cap_mode module option is set to the default value of -1 and if
829 -1 and if the no_error_inj module option is set to 0 (the default).
834 and downscaling). This control is only present if the ccs_cap_mode
835 module option is set to the default value of -1 and if the no_error_inj
862 the ccs_out_mode module option is set to the default value of -1 and if
869 -1 and if the no_error_inj module option is set to 0 (the default).
874 and downscaling). This control is only present if the ccs_out_mode
875 module option is set to the default value of -1 and if the no_error_inj
882 The following two controls are only valid for video and vbi capture.
922 is set to 0 (the default). These controls are valid for video and vbi
923 capture and output streams and for the SDR capture device except for the
995 control and can be used to test what happens if a source provides
998 range and selecting the opposite in the 'Limited RGB Range (16-235)'
1017 the tx_edid_present, tx_hotplug and tx_rxsense controls.
1061 if set, then the user can provide the lower and
1069 PICODE and PTY codes.
1133 Video, VBI and RDS Looping
1137 to VBI input and RDS output to RDS input. For video/VBI looping this emulates
1138 as if a cable was hooked up between the output and input connector. So video
1139 and VBI looping is only supported between S-Video and HDMI inputs and outputs.
1150 Video and Sliced VBI looping
1155 capture and VBI capture devices. When checked the video looping will be enabled.
1168 have to do pixel format conversion as well, and that's taking things too far.
1176 sequence and field counting in struct v4l2_buffer on the capture side may not
1194 For VBI looping to work all of the above must be valid and in addition the vbi
1197 and WSS (50 Hz formats) VBI data is looped. Teletext VBI data is not looped.
1206 However, it will also look at the frequency set by the radio transmitter and
1211 frequencies of the radio receiver and transmitter are not identical, so
1218 This driver supports cropping, composing and scaling in any combination. Normally
1221 ccs_cap_mode and ccs_out_mode module options. See section 1 on the details of
1227 only applies to the TV/S-Video/HDMI inputs and outputs. The reason is that
1230 And that does not combine with cropping, composing or scaling. This is
1233 The minimum and maximum resolutions that the scaler can achieve are 16x16 and
1236 320x180 and the maximum is 5120x2880. You can play around with this using the
1237 qv4l2 test tool and you will see these dependencies.
1243 designed for speed and simplicity, not quality.
1245 If the combination of crop, compose and scaling allows it, then it is possible
1246 to change crop and compose rectangles on the fly.
1252 The driver supports all the regular packed and planar 4:4:4, 4:2:2 and 4:2:0
1253 YUYV formats, 8, 16, 24 and 32 RGB packed formats and various multiplanar
1258 is set, then the alpha component is only used for the color red and set to
1266 single planar format (YUYV) and the multiplanar NV16M and NV61M formats the
1278 anymore, and neither are they generally needed anymore since modern hardware
1285 and list clipping (up to 16 rectangles) capabilities. Overlays are not
1287 setting: if it is set to FIELD_TOP or FIELD_BOTTOM and the capture setting is
1292 filling the overlay directly. And if you are not capturing, then no buffers
1295 In addition, the pixelformat of the capture format and that of the framebuffer
1303 the output overlay for the video output, turn on video looping and capture
1324 And from another console:
1330 And yet another console:
1336 and start streaming.
1348 This driver has support for an output overlay and is capable of:
1359 pixelformat of the capture format and that of the framebuffer must be the
1364 created framebuffer has a size of 720x576 and supports ARGB 1:5:5:5 and
1368 processing capabilities you need to turn on video looping and see the results
1390 that is disabled and reports an invalid physical address.
1396 Just as a reminder and in no particular order:
1399 - Add virtual sub-devices and media controller support
1407 - Use per-queue locks and/or per-device locks to improve throughput
1411 radio receiver, and give back noise if the frequency doesn't match up with