| /linux/drivers/usb/gadget/function/ |
| H A D | uvc_video.c | 3 * uvc_video.c -- USB Video Class Gadget driver
14 #include <linux/usb/video.h>
25 * Video codecs
29 uvc_video_encode_header(struct uvc_video *video, struct uvc_buffer *buf, in uvc_video_encode_header() argument
32 struct uvc_device *uvc = container_of(video, struct uvc_device, video); in uvc_video_encode_header()
37 data[1] = UVC_STREAM_EOH | video->fid; in uvc_video_encode_header()
39 if (video->queue.flags & UVC_QUEUE_DROP_INCOMPLETE) in uvc_video_encode_header()
42 if (video->queue.buf_used == 0 && ts.tv_sec) { in uvc_video_encode_header()
66 if (buf->bytesused - video->queue.buf_used <= len - pos) in uvc_video_encode_header()
73 uvc_video_encode_data(struct uvc_video *video, struct uvc_buffer *buf, in uvc_video_encode_data() argument
[all …]
|
| /linux/drivers/acpi/ |
| H A D | acpi_video.c | 3 * video.c - ACPI Video Driver
10 #define pr_fmt(fmt) "ACPI: video: " fmt
28 #include <acpi/video.h>
32 #define ACPI_VIDEO_BUS_NAME "Video Bus"
33 #define ACPI_VIDEO_DEVICE_NAME "Video Device"
38 MODULE_DESCRIPTION("ACPI Video Driver");
45 * By default, we don't allow duplicate ACPI video bus devices
102 .name = "video",
112 u8 multihead:1; /* can switch video heads */
113 u8 rom:1; /* can retrieve a video rom */
[all …]
|
| /linux/drivers/staging/media/starfive/camss/ |
| H A D | stf-capture.c | 58 static inline struct stf_capture *to_stf_capture(struct stfcamss_video *video) in to_stf_capture() argument
60 return container_of(video, struct stf_capture, video); in to_stf_capture()
76 static void stf_init_addrs(struct stfcamss_video *video) in stf_init_addrs() argument
78 struct stf_capture *cap = to_stf_capture(video); in stf_init_addrs()
91 stf_set_raw_addr(video->stfcamss, addr0); in stf_init_addrs()
93 stf_set_yuv_addr(video->stfcamss, addr0, addr1); in stf_init_addrs()
110 static void stf_cap_s_cfg(struct stfcamss_video *video) in stf_cap_s_cfg() argument
112 struct stf_capture *cap = to_stf_capture(video); in stf_cap_s_cfg()
130 stf_init_addrs(video); in stf_cap_s_cfg()
135 static int stf_cap_s_cleanup(struct stfcamss_video *video) in stf_cap_s_cleanup() argument
[all …]
|
| /linux/Documentation/userspace-api/media/mediactl/ |
| H A 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:
42 .. _MEDIA-ENT-F-PROC-VIDEO-ISP:
89 - Connector for a S-Video signal.
[all …]
|
| /linux/Documentation/devicetree/bindings/phy/ |
| H A D | samsung,mipi-video-phy.yaml | 4 $id: http://devicetree.org/schemas/phy/samsung,mipi-video-phy.yaml#
15 For samsung,s5pv210-mipi-video-phy compatible PHYs the second cell in the
22 samsung,exynos5420-mipi-video-phy and samsung,exynos5433-mipi-video-phy
29 - samsung,s5pv210-mipi-video-phy
30 - samsung,exynos5420-mipi-video-phy
31 - samsung,exynos5433-mipi-video-phy
32 - samsung,exynos7870-mipi-video-phy
42 samsung,s5pv210-mipi-video-phy and samsung,exynos5420-mipi-video-phy (if
50 samsung,exynos5433-mipi-video-phy and samsung,exynos7870-mipi-video-phy
57 samsung,exynos5433-mipi-video-phy and samsung,exynos7870-mipi-video-phy.
[all …]
|
| /linux/Documentation/devicetree/bindings/media/xilinx/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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";
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | dv-timings.rst | 7 Digital Video (DV) Timings
10 The video standards discussed so far have been dealing with Analog TV
11 and the corresponding video timings. Today there are many more different
13 DVI connectors etc., that carry video signals and there is a need to
14 extend the API to select the video timings for these interfaces. Since
17 set/get video timings at the input and output.
19 These ioctls deal with the detailed digital video timings that define
20 each video format. This includes parameters such as the active video
34 the DV timings as seen by the video receiver applications use the
37 When the hardware detects a video source change (e.g. the video
[all …]
|
| H A 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
60 To set the parameters for a *Video Output Overlay*, applications must
69 To set the parameters for a *Video Capture Overlay*
103 For *Video Output Overlays*
106 :ref:`osd`). For *Video Capture Overlays* this field will always be
127 - For *non-destructive Video Overlays* this field only defines a
133 - For *Video Output Overlays* the driver must return a valid
[all …]
|
| H A 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 …]
|
| H A 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 …]
|
| H A D | dev-osd.rst | 7 Video Output Overlay Interface
12 Some video output devices can overlay a framebuffer image onto the
13 outgoing video signal. Applications can set up such an overlay using
15 :ref:`Video Overlay <overlay>` interface.
18 as the :ref:`Video Output <capture>` function.
22 The default function of such a ``/dev/video`` device is video
30 Devices supporting the *Video Output Overlay* interface set the
39 Contrary to the *Video Overlay* interface the framebuffer is normally
52 The width and height of the framebuffer depends on the current video
53 standard. A V4L2 driver may reject attempts to change the video standard
[all …]
|
| H A D | vidioc-querycap.rst | 67 models of video hardware. This information is intended for users,
115 applications to open just one of the devices (typically the video
116 device) and discover whether video, vbi and/or radio are also
124 capabilities and no video or vbi capabilities. This field is only
149 :ref:`Video Capture <capture>` interface.
153 through the :ref:`Video Capture <capture>` interface.
157 :ref:`Video Output <output>` interface.
161 through the :ref:`Video Output <output>` interface.
164 - The device supports the single-planar API through the Video
169 through the Video Memory-To-Memory interface.
[all …]
|
| H A D | video.rst | 7 Video Inputs and Outputs
10 Video inputs and outputs are physical connectors of a device. These can
12 Video, S-Video and RGB connectors. Camera sensors are also considered to
13 be a video input. Video and VBI capture devices have inputs. Video and
15 no video inputs or outputs.
23 status information applicable when the current video input is queried.
27 the current video input or output. To select a different input or output
33 Example: Information about the current video input
57 Example: Switching to the first video input
|
| H A D | dev-overlay.rst | 7 Video Overlay Interface
12 Video overlay devices have the ability to genlock (TV-)video into the
13 (VGA-)video signal of a graphics card, or to store captured images
14 directly in video memory of a graphics card, typically with clipping.
18 video into a window.
20 Video overlay devices are accessed through the same character special
21 files as :ref:`video capture <capture>` devices.
25 The default function of a ``/dev/video`` device is video
31 frame rate of the video standard is not guaranteed. Frames may be
43 While the X server controls video overlay, the application can take
[all …]
|
| H A D | standard.rst | 7 Video Standards
10 Video devices typically support one or more different video standards or
11 variations of standards. Each video input and output may support another
18 V4L2 defines one bit for each analog video standard currently in use
20 hybrid standards to watch NTSC video tapes on PAL TVs and vice versa.
39 To query and select the standard used by the current video input or
49 index into the standard enumeration. Drivers must implement all video
50 standard ioctls when the device has one or more video inputs or outputs.
53 video standards makes little sense. More generally for any capture or
57 video standard, or
[all …]
|
| /linux/Documentation/devicetree/bindings/media/ |
| H A 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
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,sun8i-v3s-video-engine
22 - allwinner,sun8i-r40-video-engine
23 - allwinner,sun20i-d1-video-engine
[all …]
|
| /linux/Documentation/fb/ |
| H A 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 …]
|
| H A 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.
39 VESA(TM) Coordinated Video Timings instead of looking up the mode from a table.
58 video=VGA-1:1280x1024@60me
62 video=LVDS-1:d video=HDMI-1:D
[all …]
|
| /linux/Documentation/admin-guide/media/ |
| H A 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
47 By default the driver will create a single instance that has a video capture
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
52 The number of instances, devices, video inputs and outputs and their types are
66 - bit 0: Video Capture node
[all …]
|
| H A D | fimc.rst | 32 instance to any parallel video input or any MIPI-CSI front-end);
62 Memory-to-memory video node
65 V4L2 memory-to-memory interface at /dev/video? device node. This is standalone
66 video device, it has no media pads. However please note the mem-to-mem and
67 capture video node operation on same FIMC instance is not allowed. The driver
71 Capture video node
74 The driver supports V4L2 Video Capture Interface as defined at
77 At the capture and mem-to-mem video nodes only the multi-planar API is
95 sensor subdev -> mipi-csi subdev -> fimc subdev -> video node
98 configuration flow must be from left to right, and the video node is
[all …]
|
| /linux/Documentation/gpu/ |
| H A 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 …]
|
| /linux/drivers/media/pci/mgb4/ |
| H A D | mgb4_sysfs_out.c | 30 config = mgb4_read_reg(&voutdev->mgbdev->video, in loopin_cnt()
66 u32 config = mgb4_read_reg(&voutdev->mgbdev->video, in video_source_show()
73 * Video source change may affect the buffer queue of ANY video input/output on
77 * As we do not want to lock all the video devices at the same time, a two-stage
78 * locking strategy is used. In addition to the video device locking there is
80 * the reconfiguration is running. All the video devices check the variable in
114 config = mgb4_read_reg(&mgbdev->video, voutdev->config->regs.config); in video_source_store()
123 mgb4_mask_reg(&mgbdev->video, loopin_old->config->regs.config, in video_source_store()
126 mgb4_mask_reg(&mgbdev->video, loopin_new->config->regs.config, in video_source_store()
130 mgb4_write_reg(&mgbdev->video, voutdev->config->regs.config, in video_source_store()
[all …]
|
| /linux/Documentation/devicetree/bindings/display/ti/ |
| H A 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 …]
|