Searched full:video (Results 1 – 25 of 517) sorted by relevance
12345678910>>...21
| /Documentation/media/uapi/dvb/ |
| D | video_function_calls.rst | 13 Video Function Calls
19 video-fopen
20 video-fclose
21 video-fwrite
22 video-stop
23 video-play
24 video-freeze
25 video-continue
26 video-select-source
27 video-set-blank
[all …]
|
| D | video_types.rst | 13 Video Data Types
37 about the display format of the current video stream.
45 In case the display format of the video stream and of the display
67 The video stream source is set through the VIDEO_SELECT_SOURCE call
82 frontend or the DVR device) as the source of the video stream. If
93 representing the state of video playback.
99 VIDEO_STOPPED, /* Video is stopped */
100 VIDEO_PLAYING, /* Video is currently playing */
101 VIDEO_FREEZED /* Video is freezed */
161 The following is the structure of a video event as it is returned by the
[all …]
|
| D | video.rst | 13 Digital TV Video Device
16 The Digital TV video device controls the MPEG2 video decoder of the Digital
19 **linux/dvb/video.h** in your application.
21 Note that the Digital TV video device only controls decoding of the MPEG video
24 **/dev/video**, which allows scaling and defining output windows.
27 omission of the audio and video device as well as the video4linux
|
| /Documentation/devicetree/bindings/media/xilinx/ |
| D | video.txt | 1 DT bindings for Xilinx video IP cores
4 Xilinx video IP cores process video streams by acting as video sinks and/or
6 creating a video pipeline.
8 Each video IP core is represented by an AMBA bus child node in the device
10 cores are represented as defined in ../video-interfaces.txt.
13 tree using bindings documented in ./xlnx,video.txt.
18 The following properties are common to all Xilinx video IP cores.
20 - xlnx,video-format: This property represents a video format transmitted on an
21 AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream
22 Video IP and System Design Guide" [UG934]. How the format relates to the IP
[all …]
|
| D | xlnx,v-tpg.txt | 1 Xilinx Video Test Pattern Generator (TPG)
16 - clocks: Reference to the video core clock.
18 - xlnx,video-format, xlnx,video-width: Video format and width, as defined in
19 video.txt.
21 - port: Video port, using the DT bindings defined in ../video-interfaces.txt.
26 - xlnx,vtc: A phandle referencing the Video Timing Controller that generates
27 video timings for the TPG test patterns.
31 video timings.
53 xlnx,video-format = <XVIP_VF_YUV_422>;
54 xlnx,video-width = <8>;
[all …]
|
| D | xlnx,video.txt | 1 Xilinx Video IP Pipeline (VIPP)
7 Xilinx video IP pipeline processes video streams through one or more Xilinx
8 video IP cores. Each video IP core is represented as documented in video.txt
11 mappings between DMAs and the video IP cores.
15 - compatible: Must be "xlnx,video".
22 - ports: Video port, using the DT bindings defined in ../video-interfaces.txt.
32 compatible = "xlnx,video";
|
| /Documentation/devicetree/bindings/media/ |
| D | qcom,venus.txt | 1 * Qualcomm Venus video encoder/decoder accelerators
27 - "core" Core video accelerator clock
28 - "iface" Video accelerator AHB clock
29 - "bus" Video accelerator AXI clock
34 - "core" Core video accelerator clock
35 - "iface" Video accelerator AHB clock
36 - "bus" Video accelerator AXI clock
37 - "mbus" Video MAXI clock
55 The Venus video-codec node must contain two subnodes representing
56 video-decoder and video-encoder, and one optional firmware subnode.
[all …]
|
| D | cedrus.txt | 2 Video Engine (VE) in Allwinner literature.
9 - "allwinner,sun4i-a10-video-engine"
10 - "allwinner,sun5i-a13-video-engine"
11 - "allwinner,sun7i-a20-video-engine"
12 - "allwinner,sun8i-a33-video-engine"
13 - "allwinner,sun8i-h3-video-engine"
14 - "allwinner,sun50i-a64-video-engine"
15 - "allwinner,sun50i-h5-video-engine"
16 - "allwinner,sun50i-h6-video-engine"
46 video-codec@1c0e000 {
[all …]
|
| D | aspeed-video.txt | 1 * Device tree bindings for Aspeed Video Engine
3 The Video Engine (VE) embedded in the Aspeed AST2400 and AST2500 SOCs can
4 capture and compress video data from digital or analog sources.
7 - compatible: "aspeed,ast2400-video-engine" or
8 "aspeed,ast2500-video-engine"
24 video-engine@1e700000 {
25 compatible = "aspeed,ast2500-video-engine";
|
| /Documentation/media/uapi/mediactl/ |
| D | media-types.rst | 41 .. _MEDIA-ENT-F-PROC-VIDEO-COMPOSER:
42 .. _MEDIA-ENT-F-PROC-VIDEO-PIXEL-FORMATTER:
43 .. _MEDIA-ENT-F-PROC-VIDEO-PIXEL-ENC-CONV:
44 .. _MEDIA-ENT-F-PROC-VIDEO-LUT:
45 .. _MEDIA-ENT-F-PROC-VIDEO-SCALER:
46 .. _MEDIA-ENT-F-PROC-VIDEO-STATISTICS:
47 .. _MEDIA-ENT-F-PROC-VIDEO-ENCODER:
48 .. _MEDIA-ENT-F-PROC-VIDEO-DECODER:
95 - Connector for a S-Video signal.
101 - Camera video sensor entity.
[all …]
|
| /Documentation/gpu/ |
| D | meson.rst | 2 drm/meson AmLogic Meson Video Processing Unit
6 :doc: Video Processing Unit
8 Video Processing Unit
16 DMC|---------------VPU (Video Processing Unit)----------------|------HHI------|
19 D | vd2 | VIU | | Video Post | | Video Encoders |<---|-----VCLK |
27 Video Input Unit
31 :doc: Video Input Unit
33 Video Post Processing
37 :doc: Video Post Processing
39 Video Encoder
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | dv-timings.rst | 13 Digital Video (DV) Timings
16 The video standards discussed so far have been dealing with Analog TV
17 and the corresponding video timings. Today there are many more different
19 DVI connectors etc., that carry video signals and there is a need to
20 extend the API to select the video timings for these interfaces. Since
23 set/get video timings at the input and output.
25 These ioctls deal with the detailed digital video timings that define
26 each video format. This includes parameters such as the active video
40 the DV timings as seen by the video receiver applications use the
45 video ioctls can be used with the given input or output.
|
| D | vidioc-g-fbuf.rst | 47 :ref:`Video Overlay <overlay>` or :ref:`Video Output Overlay <osd>`
54 destructive overlay copies captured video images into the video memory
55 of a graphics card. A non-destructive overlay blends video images into a
56 VGA signal or graphics into a video signal. *Video Output Overlays* are
64 To set the parameters for a *Video Output Overlay*, applications must
73 To set the parameters for a *non-destructive Video Overlay*,
79 For a *destructive Video Overlay* applications must additionally provide
83 destructive video overlay.
115 - This field is irrelevant to *non-destructive Video Overlays*. For
116 *destructive Video Overlays* applications must provide a base
[all …]
|
| D | video.rst | 13 Video Inputs and Outputs
16 Video inputs and outputs are physical connectors of a device. These can
18 Video, S-Video and RGB connectors. Camera sensors are also considered to
19 be a video input. Video and VBI capture devices have inputs. Video and
21 no video inputs or outputs.
29 status information applicable when the current video input is queried.
33 the current video input or output. To select a different input or output
39 Example: Information about the current video input
63 Example: Switching to the first video input
|
| D | dev-capture.rst | 13 Video Capture Interface
16 Video capture devices sample an analog video signal and store the
21 Conventionally V4L2 video capture devices are accessed through character
22 device special files named ``/dev/video`` and ``/dev/video0`` to
24 ``/dev/video`` is typically a symbolic link to the preferred video
27 .. note:: The same device file names are used for video output devices.
33 Devices supporting the video capture interface set the
38 functions they may also support the :ref:`video overlay <overlay>`
48 Video capture devices shall support :ref:`audio input <audio>`,
52 :ref:`video input <video>` ioctls must be supported by all video
[all …]
|
| D | dev-output.rst | 13 Video Output Interface
16 Video output devices encode stills or image sequences as analog video
20 Conventionally V4L2 video output devices are accessed through character
21 device special files named ``/dev/video`` and ``/dev/video0`` to
23 ``/dev/video`` is typically a symbolic link to the preferred video
26 .. note:: The same device file names are used also for video capture devices.
32 Devices supporting the video output interface set the
46 Video output devices shall support :ref:`audio output <audio>`,
50 :ref:`video output <video>` ioctls must be supported by all video
58 former select an area of the video picture where the image will appear,
[all …]
|
| D | tuner.rst | 20 Video input devices can have one or more tuners demodulating a RF
21 signal. Each tuner is associated with one or more video inputs,
28 Radio input devices have exactly one tuner with index zero, no video
36 current video or radio input is queried.
42 determined by the current video input. Drivers must support both ioctls
51 Video output devices can have one or more modulators, that modulate a
52 video signal for radiation or connection to the antenna input of a TV
53 set or video recorder. Each modulator is associated with one or more
54 video outputs, depending on the number of RF connectors on the
62 video outputs.
[all …]
|
| D | dev-osd.rst | 13 Video Output Overlay Interface
18 Some video output devices can overlay a framebuffer image onto the
19 outgoing video signal. Applications can set up such an overlay using
21 :ref:`Video Overlay <overlay>` interface.
24 as the :ref:`Video Output <capture>` function.
28 The default function of such a ``/dev/video`` device is video
36 Devices supporting the *Video Output Overlay* interface set the
45 Contrary to the *Video Overlay* interface the framebuffer is normally
58 The width and height of the framebuffer depends on the current video
59 standard. A V4L2 driver may reject attempts to change the video standard
[all …]
|
| D | standard.rst | 13 Video Standards
16 Video devices typically support one or more different video standards or
17 variations of standards. Each video input and output may support another
24 V4L2 defines one bit for each analog video standard currently in use
26 hybrid standards to watch NTSC video tapes on PAL TVs and vice versa.
45 To query and select the standard used by the current video input or
55 index into the standard enumeration. Drivers must implement all video
56 standard ioctls when the device has one or more video inputs or outputs.
59 video standards makes little sense. More generally for any capture or
63 video standard, or
[all …]
|
| /Documentation/fb/ |
| D | uvesafb.rst | 2 uvesafb - A Generic Driver for VBE2+ compliant video cards
8 uvesafb should work with any video card that has a Video BIOS compliant
12 v86d. v86d is used to run the x86 Video BIOS code in a simulated and
32 uvesafb is a _generic_ driver which supports a wide variety of video
33 cards, but which is ultimately limited by the Video BIOS interface.
37 - A strict and limited set of supported video modes. Often the native
39 with uvesafb, simply because the Video BIOS doesn't support the
40 video mode you want to use. This can be especially painful with
41 widescreen panels, where native video modes don't have the 4:3 aspect
44 Video BIOS. Note that many nVidia Video BIOS-es claim to be VBE 3.0
[all …]
|
| D | modedb.rst | 2 modedb default video mode support
6 Currently all frame buffer device drivers have their own video mode databases,
9 - one routine to probe for video modes, which can be used by all frame buffer
11 - one generic video mode database with a fair amount of standard videomodes
17 When a frame buffer device receives a video= option it doesn't know, it should
18 consider that to be a video mode option. If no frame buffer device is specified
19 in a video= option, fbmem considers that to be a global video mode option.
31 VESA(TM) Coordinated Video Timings instead of looking up the mode from a table.
50 video=VGA-1:1280x1024@60me
54 video=LVDS-1:d video=HDMI-1:D
[all …]
|
| /Documentation/media/v4l-drivers/ |
| D | ivtv.rst | 25 Open Source driver implementation for video capture cards based on the
31 * Hardware mpeg2 capture of broadcast video (and sound) via the tuner or
32 S-Video/Composite and audio line-in.
46 video signal)
47 * Provides a framebuffer (allowing X applications to appear on the video
71 Cards that don't have a video output capability (i.e. non PVR350 cards)
82 crw-rw---- 1 root video 81, 0 Jun 19 22:22 /dev/video0
83 crw-rw---- 1 root video 81, 16 Jun 19 22:22 /dev/video16
84 crw-rw---- 1 root video 81, 24 Jun 19 22:22 /dev/video24
85 crw-rw---- 1 root video 81, 32 Jun 19 22:22 /dev/video32
[all …]
|
| D | fimc.rst | 32 instance to any parallel video input or any MIPI-CSI front-end);
47 - camera capture video device driver
53 - video post-processor (mem-to-mem)
81 Memory-to-memory video node
84 V4L2 memory-to-memory interface at /dev/video? device node. This is standalone
85 video device, it has no media pads. However please note the mem-to-mem and
86 capture video node operation on same FIMC instance is not allowed. The driver
90 Capture video node
93 The driver supports V4L2 Video Capture Interface as defined at
96 At the capture and mem-to-mem video nodes only the multi-planar API is
[all …]
|
| D | vivid.rst | 3 The Virtual Video Test Driver (vivid)
6 This driver emulates video4linux hardware of various types: video capture, video
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
29 - Support for various pixel aspect ratios and video aspect ratios
45 By default the driver will create a single instance that has a video capture
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
50 The number of instances, devices, video inputs and outputs and their types are
64 - bit 0: Video Capture node
[all …]
|
| /Documentation/driver-api/ |
| D | frame-buffer.rst | 9 fb_info defines the current state of a particular video card. Inside
14 fb_var_screeninfo is used to describe the features of a video card
34 .. kernel-doc:: drivers/video/fbdev/core/fbmem.c
40 .. kernel-doc:: drivers/video/fbdev/core/fbcmap.c
43 Frame Buffer Video Mode Database
46 .. kernel-doc:: drivers/video/fbdev/core/modedb.c
49 .. kernel-doc:: drivers/video/fbdev/core/modedb.c
52 Frame Buffer Macintosh Video Mode Database
55 .. kernel-doc:: drivers/video/fbdev/macmodes.c
|
12345678910>>...21