Home
last modified time | relevance | path

Searched +full:video +full:- +full:receiver (Results 1 – 25 of 171) sorted by relevance

1234567

/openbmc/linux/Documentation/admin-guide/media/
H A Dvivid.rst1 .. SPDX-License-Identifier: GPL-2.0
3 The Virtual Video Test Driver (vivid)
6 This driver emulates video4linux hardware of various types: video capture, video
8 transmitters, touch capture and a software defined radio receiver. In addition a
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
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
26 - Support for the alpha color component
[all …]
H A Dplatform-cardlist.rst1 .. SPDX-License-Identifier: GPL-2.0
17 am437x-vpfe TI AM437x VPFE
18 aspeed-video Aspeed AST2400 and AST2500
19 atmel-isc ATMEL Image Sensor Controller (ISC)
20 atmel-isi ATMEL Image Sensor Interface (ISI)
24 cdns-csi2rx Cadence MIPI-CSI2 RX Controller
25 cdns-csi2tx Cadence MIPI-CSI2 TX Controller
26 coda-vpu Chips&Media Coda multi-standard codec IP
27 dm355_ccdc TI DM355 CCDC video capture
28 dm644x_ccdc TI DM6446 CCDC video capture
[all …]
H A Dimx.rst1 .. SPDX-License-Identifier: GPL-2.0
3 i.MX Video Capture Driver
7 ------------
15 - Image DMA Controller (IDMAC)
16 - Camera Serial Interface (CSI)
17 - Image Converter (IC)
18 - Sensor Multi-FIFO Controller (SMFC)
19 - Image Rotator (IRT)
20 - Video De-Interlacing or Combining Block (VDIC)
23 memory. Various dedicated DMA channels exist for both video capture and
[all …]
H A Dusb-cardlist.rst1 .. SPDX-License-Identifier: GPL-2.0
18 via USB Video Class. Those cameras are automatically supported by the
19 ``uvc-driver``.
23 card lists for such vendor-class devices.
35 some of the drivers have sub-drivers, not shown at this table.
36 In particular, gspca driver has lots of sub-drivers,
37 for cameras not supported by the USB Video Class (UVC) driver,
38 as shown at :doc:`gspca card list <gspca-cardlist>`.
45 b2c2-flexcop-usb Technisat/B2C2 Air/Sky/Cable2PC USB
46 cx231xx Conexant cx231xx USB video capture
[all …]
H A Dipu3.rst1 .. SPDX-License-Identifier: GPL-2.0
20 (ImgU) and the CIO2 device (MIPI CSI2 receiver).
24 ImgU). The CIO2 driver is available as drivers/media/pci/intel/ipu3/ipu3-cio2*
36 Both of the drivers implement V4L2, Media Controller and V4L2 sub-device
38 MIPI CSI-2 interfaces through V4L2 sub-device sensor drivers.
44 interface to the user space. There is a video node for each CSI-2 receiver,
47 The CIO2 contains four independent capture channel, each with its own MIPI CSI-2
48 receiver and DMA engine. Each channel is modelled as a V4L2 sub-device exposed
49 to userspace as a V4L2 sub-device node and has two pads:
53 .. flat-table::
[all …]
H A Dfimc.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
17 drivers/media/platform/samsung/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
31 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
[all …]
H A Dimx7.rst1 .. SPDX-License-Identifier: GPL-2.0
3 i.MX7 Video Capture Driver
7 ------------
14 - CMOS Sensor Interface (CSI)
15 - Video Multiplexer
16 - MIPI CSI-2 Receiver
18 .. code-block:: none
20 MIPI Camera Input ---> MIPI CSI-2 --- > |\
24 | U | ------> CSI ---> Capture
27 Parallel Camera Input ----------------> | /
[all …]
/openbmc/linux/Documentation/userspace-api/media/v4l/
H A Dext-ctrls-dv.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _dv-controls:
6 Digital Video Control Reference
9 The Digital Video control class is intended to control receivers and
14 the receiver or transmitter subdevice that implements them, so they are
15 only exposed on the ``/dev/v4l-subdev*`` device node.
21 receive or transmit video from/to only one of those pads, the other pads
23 Identification Data, :ref:`vesaedid`) and HDCP (High-bandwidth Digital
33 .. _dv-control-id:
35 Digital Video Control IDs
[all …]
H A Dvidioc-g-edid.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_G_EDID - VIDIOC_S_EDID - VIDIOC_SUBDEV_G_EDID - VIDIOC_SUBDEV_S_EDID - Get or set the EDID o…
47 from a receiver or an output of a transmitter device. They can be used
48 with subdevice nodes (/dev/v4l-subdevX) or with video nodes
51 When used with video nodes the ``pad`` field represents the input (for
52 video capture devices) or output (for video output devices) index as is
84 To set the EDID blocks of a receiver the application has to fill in the
105 .. flat-table:: struct v4l2_edid
106 :header-rows: 0
107 :stub-columns: 0
[all …]
H A Dvidioc-dv-timings-cap.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_DV_TIMINGS_CAP - VIDIOC_SUBDEV_DV_TIMINGS_CAP - The capabilities of the Digital Video receiv…
38 To query the capabilities of the DV receiver/transmitter applications
41 ``VIDIOC_DV_TIMINGS_CAP`` ioctl on a video node and the driver will fill
47 switching the video input or output.
62 .. flat-table:: struct v4l2_bt_timings_cap
63 :header-rows: 0
64 :stub-columns: 0
67 * - __u32
68 - ``min_width``
[all …]
H A Ddev-subdev.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
6 Sub-device Interface
13 components as software blocks called sub-devices.
15 V4L2 sub-devices are usually kernel-only objects. If the V4L2 driver
17 media entities. Applications will be able to enumerate the sub-devices
21 In addition to make sub-devices discoverable, drivers can also choose to
23 sub-device driver and the V4L2 device driver support this, sub-devices
26 - query, read and write sub-devices controls
28 - subscribe and unsubscribe to events and retrieve them
30 - negotiate image formats on individual pads
[all …]
H A Ddv-timings.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _dv-timings:
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
14 it is not possible to extend the :ref:`v4l2_std_id <v4l2-std-id>`
16 set/get video timings at the input and output.
18 These ioctls deal with the detailed digital video timings that define
[all …]
/openbmc/linux/Documentation/devicetree/bindings/media/xilinx/
H A Dxlnx,csi2rxss.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Xilinx MIPI CSI-2 Receiver Subsystem
10 - Vishal Sagar <vishal.sagar@amd.com>
13 The Xilinx MIPI CSI-2 Receiver Subsystem is used to capture MIPI CSI-2
15 video data for image processing.
16 The subsystem consists of a MIPI D-PHY in slave mode which captures the
17 data packets. This is passed along the MIPI CSI-2 Rx IP which extracts the
18 packet data. The optional Video Format Bridge (VFB) converts this data to
[all …]
/openbmc/linux/Documentation/devicetree/bindings/media/
H A Drenesas,rzg2l-csi2.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/media/renesas,rzg2l-csi2.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Renesas RZ/G2L (and alike SoC's) MIPI CSI-2 receiver
11 - Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
14 The CSI-2 receiver device provides MIPI CSI-2 capabilities for the Renesas RZ/G2L
15 (and alike SoCs). MIPI CSI-2 is part of the CRU block which is used in conjunction
16 with the Image Processing module, which provides the video capture capabilities.
21 - enum:
[all …]
H A Dimx.txt1 Freescale i.MX Media Video Device
4 Video Media Controller node
5 ---------------------------
7 This is the media controller node for video capture support. It is a
12 - compatible : "fsl,imx-capture-subsystem";
13 - ports : Should contain a list of phandles pointing to camera
18 capture-subsystem {
19 compatible = "fsl,imx-capture-subsystem";
25 --------------
27 This is the device node for the MIPI CSI-2 Receiver core in the i.MX
[all …]
H A Drenesas,csi2.yaml1 # SPDX-License-Identifier: GPL-2.0-only
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Renesas R-Car MIPI CSI-2 receiver
11 - Niklas Söderlund <niklas.soderlund@ragnatech.se>
14 The R-Car CSI-2 receiver device provides MIPI CSI-2 capabilities for the
15 Renesas R-Car and RZ/G2 family of devices. It is used in conjunction with the
16 R-Car VIN module, which provides the video capture capabilities.
21 - enum:
22 - renesas,r8a774a1-csi2 # RZ/G2M
[all …]
/openbmc/linux/Documentation/userspace-api/media/
H A Dintro.rst1 .. SPDX-License-Identifier: GPL-2.0
7 This document covers the Linux Kernel to Userspace API's used by video
8 and radio streaming devices, including video cameras, analog and digital
9 TV receiver cards, AM/FM receiver cards, Software Defined Radio (SDR),
16 .. kernel-figure:: typical_media_device.svg
25 1. The :ref:`first part <v4l2spec>` covers radio, video capture and output,
30 called as DVB API, in fact it covers several different video standards
31 including DVB-T/T2, DVB-S/S2, DVB-C, ATSC, ISDB-T, ISDB-S, DTMB, etc. The
46 Mailing List (LMML) <http://vger.kernel.org/vger-lists.html#linux-media>`__.
/openbmc/linux/drivers/media/platform/renesas/rcar-vin/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 tristate "R-Car MIPI CSI-2 Receiver"
12 Support for Renesas R-Car MIPI CSI-2 receiver.
13 Supports R-Car Gen3 and RZ/G2 SoCs.
16 module will be called rcar-csi2.
19 tristate "R-Car Video Input (VIN) Driver"
28 Support for Renesas R-Car Video Input (VIN) driver.
29 Supports R-Car Gen{2,3} and RZ/G{1,2} SoCs.
32 module will be called rcar-vin.
H A Drcar-vin.h1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * Driver for Renesas R-Car VIN
6 * Copyright (C) 2011-2013 Renesas Solutions Corp.
10 * Based on the soc-camera rcar_vin driver
18 #include <media/v4l2-async.h>
19 #include <media/v4l2-ctrls.h>
20 #include <media/v4l2-dev.h>
21 #include <media/v4l2-device.h>
22 #include <media/v4l2-fwnode.h>
23 #include <media/videobuf2-v4l2.h>
[all …]
/openbmc/linux/Documentation/devicetree/bindings/media/i2c/
H A Dtda1997x.txt1 Device-Tree bindings for the NXP TDA1997x HDMI receiver
3 The TDA19971/73 are HDMI video receivers.
5 The TDA19971 Video port output pins can be used as follows:
6 - RGB 8bit per color (24 bits total): R[11:4] B[11:4] G[11:4]
7 - YUV444 8bit per color (24 bits total): Y[11:4] Cr[11:4] Cb[11:4]
8 - YUV422 semi-planar 8bit per component (16 bits total): Y[11:4] CbCr[11:4]
9 - YUV422 semi-planar 10bit per component (20 bits total): Y[11:2] CbCr[11:2]
10 - YUV422 semi-planar 12bit per component (24 bits total): - Y[11:0] CbCr[11:0]
11 - YUV422 BT656 8bit per component (8 bits total): YCbCr[11:4] (2-cycles)
12 - YUV422 BT656 10bit per component (10 bits total): YCbCr[11:2] (2-cycles)
[all …]
H A Dadv748x.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Analog Devices ADV748X video decoder with HDMI receiver
10 - Kieran Bingham <kieran.bingham@ideasonboard.com>
11 - Niklas Söderlund <niklas.soderlund@ragnatech.se>
14 The ADV7481 and ADV7482 are multi format video decoders with an integrated
15 HDMI receiver. They can output CSI-2 on two independent outputs TXA and TXB
21 - enum:
22 - adi,adv7481
[all …]
H A Dov7740.txt7 The common video interfaces bindings (see video-interfaces.txt) should
8 be used to specify link to the image data receiver. The OV7740 device
12 - compatible: "ovti,ov7740".
13 - reg: I2C slave address of the sensor.
14 - clocks: Reference to the xvclk input clock.
15 - clock-names: "xvclk".
18 - reset-gpios: Rreference to the GPIO connected to the reset_b pin,
19 if any. Active low with pull-ip resistor.
20 - powerdown-gpios: Reference to the GPIO connected to the pwdn pin,
21 if any. Active high with pull-down resistor.
[all …]
/openbmc/linux/drivers/media/rc/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
8 needed in order to support several video capture adapters,
11 Enable this option if you have a video capture board even
52 receiver, or if you wish to use an encoder to transmit this IR.
69 a raw IR receiver in your system.
80 tristate "Enable IR raw decoder for the RC-5 protocol"
84 Enable this option if you have IR with RC-5 protocol, and
96 tristate "Enable IR raw decoder for the RC-MM protocol"
98 Enable this option when you have IR with RC-MM protocol, and
100 24 and 32 bits RC-MM variants. You can enable or disable the
[all …]
/openbmc/linux/drivers/media/platform/samsung/exynos4-is/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
30 interface and video postprocessor (FIMC) devices.
33 module will be called s5p-fimc.
36 tristate "S5P/EXYNOS MIPI-CSI2 receiver (MIPI-CSIS) driver"
41 This is a V4L2 driver for Samsung S5P and EXYNOS4 SoC MIPI-CSI2
42 receiver (MIPI-CSIS) devices.
45 module will be called s5p-csis.
48 tristate "EXYNOS FIMC-LITE camera interface driver"
55 This is a V4L2 driver for Samsung EXYNOS4/5 SoC FIMC-LITE camera
59 module will be called exynos-fimc-lite.
[all …]
/openbmc/linux/drivers/media/radio/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # Multimedia Video device configuration
25 that are compatible with the Video For Linux API. Information on
27 <file:Documentation/userspace-api/media/index.rst>.
30 module will be called radio-maxiradio.
45 tristate "Griffin radioSHARK USB radio receiver"
49 Choose Y here if you have this radio receiver.
55 that are compatible with the Video For Linux API. Information on
57 <file:Documentation/userspace-api/media/index.rst>.
60 module will be called radio-shark.
[all …]

1234567