Searched full:video (Results 1 – 25 of 567) sorted by relevance
12345678910>>...23
| /Documentation/userspace-api/media/dvb/ |
| D | video_function_calls.rst | 6 Video Function Calls
12 video-fopen
13 video-fclose
14 video-fwrite
15 video-stop
16 video-play
17 video-freeze
18 video-continue
19 video-select-source
20 video-set-blank
[all …]
|
| D | video.rst | 6 Digital TV Video Device
9 The Digital TV video device controls the MPEG2 video decoder of the Digital
12 **linux/dvb/video.h** in your application.
14 Note that the Digital TV video device only controls decoding of the MPEG video
17 **/dev/video**, which allows scaling and defining output windows.
20 omission of the audio and video device as well as the video4linux
|
| D | video_types.rst | 6 Video Data Types
30 about the display format of the current video stream.
38 In case the display format of the video stream and of the display
60 The video stream source is set through the VIDEO_SELECT_SOURCE call
75 frontend or the DVR device) as the source of the video stream. If
86 representing the state of video playback.
92 VIDEO_STOPPED, /* Video is stopped */
93 VIDEO_PLAYING, /* Video is currently playing */
94 VIDEO_FREEZED /* Video is freezed */
154 The following is the structure of a video event as it is returned by the
[all …]
|
| /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/userspace-api/media/mediactl/ |
| D | media-types.rst | 34 .. _MEDIA-ENT-F-PROC-VIDEO-COMPOSER:
35 .. _MEDIA-ENT-F-PROC-VIDEO-PIXEL-FORMATTER:
36 .. _MEDIA-ENT-F-PROC-VIDEO-PIXEL-ENC-CONV:
37 .. _MEDIA-ENT-F-PROC-VIDEO-LUT:
38 .. _MEDIA-ENT-F-PROC-VIDEO-SCALER:
39 .. _MEDIA-ENT-F-PROC-VIDEO-STATISTICS:
40 .. _MEDIA-ENT-F-PROC-VIDEO-ENCODER:
41 .. _MEDIA-ENT-F-PROC-VIDEO-DECODER:
88 - Connector for a S-Video signal.
94 - Camera video sensor entity.
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | allwinner,sun4i-a10-video-engine.yaml | 4 $id: http://devicetree.org/schemas/media/allwinner,sun4i-a10-video-engine.yaml#
7 title: Allwinner A10 Video Engine Device Tree Bindings
16 - allwinner,sun4i-a10-video-engine
17 - allwinner,sun5i-a13-video-engine
18 - allwinner,sun7i-a20-video-engine
19 - allwinner,sun8i-a33-video-engine
20 - allwinner,sun8i-h3-video-engine
21 - allwinner,sun50i-a64-video-engine
22 - allwinner,sun50i-h5-video-engine
23 - allwinner,sun50i-h6-video-engine
[all …]
|
| D | aspeed-video.txt | 1 * Device tree bindings for Aspeed Video Engine
3 The Video Engine (VE) embedded in the Aspeed AST2400/2500/2600 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" or
9 "aspeed,ast2600-video-engine"
25 video-engine@1e700000 {
26 compatible = "aspeed,ast2500-video-engine";
|
| D | qcom,msm8916-venus.yaml | 8 title: Qualcomm Venus video encode and decode accelerators
14 The Venus IP is a video encode and decode accelerator present
45 video-decoder:
57 video-encoder:
69 video-firmware:
92 - video-decoder
93 - video-encoder
102 video-codec@1d00000 {
114 video-decoder {
118 video-encoder {
|
| D | qcom,sc7180-venus.yaml | 8 title: Qualcomm Venus video encode and decode accelerators
14 The Venus IP is a video encode and decode accelerator present
61 - const: video-mem
64 video-decoder:
76 video-encoder:
88 video-firmware:
112 - video-decoder
113 - video-encoder
122 venus: video-codec@aa00000 {
139 video-decoder {
[all …]
|
| D | qcom,sdm845-venus-v2.yaml | 8 title: Qualcomm Venus video encode and decode accelerators
14 The Venus IP is a video encode and decode accelerator present
59 video-core0:
71 video-core1:
83 video-firmware:
107 - video-core0
108 - video-core1
117 video-codec@aa00000 {
139 video-core0 {
143 video-core1 {
|
| D | qcom,sdm845-venus.yaml | 8 title: Qualcomm Venus video encode and decode accelerators
14 The Venus IP is a video encode and decode accelerator present
45 video-core0:
71 video-core1:
97 video-firmware:
120 - video-core0
121 - video-core1
130 video-codec@aa00000 {
143 video-core0 {
151 video-core1 {
|
| /Documentation/userspace-api/media/v4l/ |
| D | dv-timings.rst | 6 Digital Video (DV) Timings
9 The video standards discussed so far have been dealing with Analog TV
10 and the corresponding video timings. Today there are many more different
12 DVI connectors etc., that carry video signals and there is a need to
13 extend the API to select the video timings for these interfaces. Since
16 set/get video timings at the input and output.
18 These ioctls deal with the detailed digital video timings that define
19 each video format. This includes parameters such as the active video
33 the DV timings as seen by the video receiver applications use the
38 video ioctls can be used with the given input or output.
|
| D | video.rst | 6 Video Inputs and Outputs
9 Video inputs and outputs are physical connectors of a device. These can
11 Video, S-Video and RGB connectors. Camera sensors are also considered to
12 be a video input. Video and VBI capture devices have inputs. Video and
14 no video inputs or outputs.
22 status information applicable when the current video input is queried.
26 the current video input or output. To select a different input or output
32 Example: Information about the current video input
56 Example: Switching to the first video input
|
| D | dev-capture.rst | 7 Video Capture Interface
10 Video capture devices sample an analog video signal and store the
15 Conventionally V4L2 video capture devices are accessed through character
16 device special files named ``/dev/video`` and ``/dev/video0`` to
18 ``/dev/video`` is typically a symbolic link to the preferred video
21 .. note:: The same device file names are used for video output devices.
26 Devices supporting the video capture interface set the
31 functions they may also support the :ref:`video overlay <overlay>`
40 Video capture devices shall support :ref:`audio input <audio>`,
44 :ref:`video input <video>` ioctls must be supported by all video
[all …]
|
| D | vidioc-g-fbuf.rst | 40 :ref:`Video Overlay <overlay>` or :ref:`Video Output Overlay <osd>`
47 destructive overlay copies captured video images into the video memory
48 of a graphics card. A non-destructive overlay blends video images into a
49 VGA signal or graphics into a video signal. *Video Output Overlays* are
57 To set the parameters for a *Video Output Overlay*, applications must
66 To set the parameters for a *non-destructive Video Overlay*,
72 For a *destructive Video Overlay* applications must additionally provide
76 destructive video overlay.
107 - This field is irrelevant to *non-destructive Video Overlays*. For
108 *destructive Video Overlays* applications must provide a base
[all …]
|
| D | dev-output.rst | 7 Video Output Interface
10 Video output devices encode stills or image sequences as analog video
14 Conventionally V4L2 video output devices are accessed through character
15 device special files named ``/dev/video`` and ``/dev/video0`` to
17 ``/dev/video`` is typically a symbolic link to the preferred video
20 .. note:: The same device file names are used also for video capture devices.
25 Devices supporting the video output interface set the
38 Video output devices shall support :ref:`audio output <audio>`,
42 :ref:`video output <video>` ioctls must be supported by all video
49 former select an area of the video picture where the image will appear,
[all …]
|
| D | tuner.rst | 13 Video input devices can have one or more tuners demodulating a RF
14 signal. Each tuner is associated with one or more video inputs,
21 Radio input devices have exactly one tuner with index zero, no video
29 current video or radio input is queried.
35 determined by the current video input. Drivers must support both ioctls
44 Video output devices can have one or more modulators, that modulate a
45 video signal for radiation or connection to the antenna input of a TV
46 set or video recorder. Each modulator is associated with one or more
47 video outputs, depending on the number of RF connectors on the
55 video outputs.
[all …]
|
| D | dev-osd.rst | 6 Video Output Overlay Interface
11 Some video output devices can overlay a framebuffer image onto the
12 outgoing video signal. Applications can set up such an overlay using
14 :ref:`Video Overlay <overlay>` interface.
17 as the :ref:`Video Output <capture>` function.
21 The default function of such a ``/dev/video`` device is video
29 Devices supporting the *Video Output Overlay* interface set the
38 Contrary to the *Video Overlay* interface the framebuffer is normally
51 The width and height of the framebuffer depends on the current video
52 standard. A V4L2 driver may reject attempts to change the video standard
[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/admin-guide/media/ |
| D | platform-cardlist.rst | 18 aspeed-video Aspeed AST2400 and AST2500
27 dm355_ccdc TI DM355 CCDC video capture
28 dm644x_ccdc TI DM6446 CCDC video capture
35 isdf TI DM365 ISIF video capture
39 mtk-vcodec-dec Mediatek Video Codec
40 mtk-vpu Mediatek Video Processor Unit
51 rcar-vin R-Car Video Input (VIN)
59 s5p-mfc Samsung S5P MFC Video Codec
60 sh_veu SuperH VEU mem2mem video processing
61 sh_vou SuperH VOU video output
[all …]
|
| 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 …]
|
| /Documentation/devicetree/bindings/display/ti/ |
| D | ti,j721e-dss.yaml | 16 four video planes. There is two full video planes and two "lite
17 planes" without scaling support. The video ports can be connected to
30 - description: VIDL1 light video plane 1
31 - description: VIDL2 light video plane 2
32 - description: VID1 video plane 1
33 - description: VID1 video plane 2
38 - description: VP1 video port 1
39 - description: VP2 video port 2
40 - description: VP3 video port 3
41 - description: VP4 video port 4
[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 …]
|
12345678910>>...23