/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/media/platform/qcom/camss/ |
H A D | camss-video.c | 3 * camss-video.c 18 #include "camss-video.h" 67 static struct v4l2_subdev *video_remote_subdev(struct camss_video *video, in video_remote_subdev() argument 72 remote = media_pad_remote_pad_first(&video->pad); in video_remote_subdev() 83 static int video_get_subdev_format(struct camss_video *video, in video_get_subdev_format() argument 93 subdev = video_remote_subdev(video, &pad); in video_get_subdev_format() 104 video->formats, video->nformats); in video_get_subdev_format() 108 format->type = video->type; in video_get_subdev_format() 111 &video->formats[ret], video->bpl_alignment); in video_get_subdev_format() 115 * Video queue operations [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/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 | 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 36 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 | 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 …]
|
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 …]
|
/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 41 samsung,s5pv210-mipi-video-phy and samsung,exynos5420-mipi-video-phy (if 49 samsung,exynos5433-mipi-video-phy (if not a child of PMU). 55 samsung,exynos5433-mipi-video-phy. 61 samsung,exynos5433-mipi-video-phy. [all …]
|
/linux/drivers/media/platform/ti/omap3isp/ |
H A D | ispvideo.h | 5 * TI OMAP3 ISP - Generic video node 60 /* The stream has been started on the input video node. */ 62 /* The stream has been started on the output video node. */ 64 /* At least one buffer is queued on the input video node. */ 66 /* At least one buffer is queued on the output video node. */ 123 * struct isp_buffer - ISP video buffer 143 #define isp_video_dmaqueue_flags_clr(video) \ argument 144 ({ (video)->dmaqueue_flags = 0; }) 147 * struct isp_video_operations - ISP video operations 152 int(*queue)(struct isp_video *video, struct isp_buffer *buffer); [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 …]
|
/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 | 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 34 isdf TI DM365 ISIF video capture 38 mtk-vcodec-dec Mediatek Video Codec 39 mtk-vpu Mediatek Video Processor Unit 50 rcar-vin R-Car Video Input (VIN) 58 s5p-mfc Samsung S5P MFC Video Codec 59 sh_veu SuperH VEU mem2mem video processing 60 sh_vou SuperH VOU video output [all …]
|
H A 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 …]
|
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/drivers/media/i2c/ |
H A D | Kconfig | 3 # Multimedia Video device configuration 17 some video boards have the IR connected via I2C bus. 880 comment "audio, video and radio I2C drivers auto-selected by 'Autoselect ancillary drivers'" 1066 menu "Video decoders" 1076 Support for the Analog Devices ADV7180 video decoder. 1086 ADV7183 video decoder. 1101 ADV7481 and ADV7482 HDMI/Analog video decoders. 1116 Support for the Analog Devices ADV7604 video decoder. 1139 Support for the Analog Devices ADV7842 video decoder. 1159 Support for BT819A video decoder. [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 …]
|