| /Documentation/userspace-api/media/v4l/ |
| D | dev-decoder.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Memory-to-Memory Stateful Video Decoder Interface
9 A stateful video decoder takes complete chunks of the bytestream (e.g. Annex-B
34 5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
35 used interchangeably with multi-planar API, unless specified otherwise,
41 7. Given an ``OUTPUT`` buffer A, then A' represents a buffer on the ``CAPTURE``
44 .. _decoder-glossary:
49 CAPTURE
54 into ``CAPTURE`` buffers.
79 Good at sub-partitioning the picture into variable sized structures.
[all …]
|
| D | vidioc-enum-fmt.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_ENUM_FMT - Enumerate image formats
41 (that is, with lower ``index`` value) less-preferred formats.
43 Depending on the ``V4L2_CAP_IO_MC`` :ref:`capability <device-capabilities>`,
46 1) ``V4L2_CAP_IO_MC`` is not set (also known as a 'video-node-centric' driver)
58 2) ``V4L2_CAP_IO_MC`` is set (also known as an 'MC-centric' driver)
63 If the ``mbus_code`` field is initialized to a valid (non-zero)
64 :ref:`media bus format code <v4l2-mbus-pixelcode>`, then drivers
65 shall restrict enumeration to only the image formats that can produce
66 (for video output devices) or be produced from (for video capture
[all …]
|
| D | dev-encoder.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
6 Memory-to-Memory Stateful Video Encoder Interface
12 further post-processing by the client.
34 5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
35 used interchangeably with multi-planar API, unless specified otherwise,
41 7. Given an ``OUTPUT`` buffer A, then A' represents a buffer on the ``CAPTURE``
47 Refer to :ref:`decoder-glossary`.
52 .. kernel-render:: DOT
65 qi -> Initialization [ label = "open()" ];
67 Initialization -> Encoding [ label = "Both queues streaming" ];
[all …]
|
| D | dev-stateless-decoder.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Memory-to-memory Stateless Video Decoder Interface
18 This section describes how user-space ("the client") is expected to communicate
24 Stateless decoders make use of the :ref:`media-request-api`. A stateless
42 irrespective of the format currently set on the ``CAPTURE`` queue.
45 codec-specific capability controls (such as H.264 profiles) to the set
49 :c:func:`VIDIOC_ENUM_FMT` on the ``CAPTURE`` queue.
51 * The driver must return only the formats supported for the format currently
55 formats may depend on the value of some codec-dependent controls.
57 before querying the ``CAPTURE`` queue. Failure to do so will result in the
[all …]
|
| D | vidioc-g-parm.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_G_PARM - VIDIOC_S_PARM - Get or set streaming parameters
38 Applications can request a different frame interval. The capture or
63 .. flat-table:: struct v4l2_streamparm
64 :header-rows: 0
65 :stub-columns: 0
68 * - __u32
69 - ``type``
70 - The buffer (stream) type, same as struct
73 * - union {
[all …]
|
| D | vidioc-g-fmt.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_G_FMT - VIDIOC_S_FMT - VIDIOC_TRY_FMT - Get or set the data format, try a format
47 type. For example video capture devices use
51 the respective member of the ``fmt`` union. In case of video capture
62 first, and to modify only those parameters not suitable for the
94 .. flat-table:: struct v4l2_format
95 :header-rows: 0
96 :stub-columns: 0
98 * - __u32
99 - ``type``
[all …]
|
| D | pixfmt-v4l2.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 Single-planar format structure
13 .. flat-table:: struct v4l2_pix_format
14 :header-rows: 0
15 :stub-columns: 0
18 * - __u32
19 - ``width``
20 - Image width in pixels.
21 * - __u32
22 - ``height``
[all …]
|
| D | selection-api-configuration.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
12 limitations. It may only scale up or down, support only discrete scaling
20 :ref:`constraint flags <v4l2-selection-flags>`.
23 Configuration of video capture
26 See figure :ref:`sel-targets-capture` for examples of the selection
27 targets available for a video capture device. It is recommended to
39 active cropping area must lie completely inside the capture boundaries.
43 Each capture device has a default source rectangle, given by the
63 :ref:`constraint flags <v4l2-selection-flags>`.
65 For capture devices the default composing rectangle is queried using
[all …]
|
| D | vidioc-querycap.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_QUERYCAP - Query device capabilities
47 .. flat-table:: struct v4l2_capability
48 :header-rows: 0
49 :stub-columns: 0
52 * - __u8
53 - ``driver``\ [16]
54 - Name of the driver, a unique NUL-terminated ASCII string. For
62 sure the strings are properly NUL-terminated.
63 * - __u8
[all …]
|
| /Documentation/gpu/rfc/ |
| D | i915_small_bar.rst | 4 Starting from DG2 we will have resizable BAR support for device local-memory(i.e
6 smaller than the total probed_size. In such cases, only some subset of
8 while the remainder is only accessible via the GPU.
11 ----------------------------------------------
14 underneath the device has a small BAR, meaning only some portion of it is CPU
16 required, and prioritize using the non-CPU visible portion of
19 .. kernel-doc:: Documentation/gpu/rfc/i915_small_bar.h
23 ---------------------------------
25 CPU accessible portion, for the particular region. This should only be
34 .. kernel-doc:: Documentation/gpu/rfc/i915_small_bar.h
[all …]
|
| /Documentation/admin-guide/media/ |
| D | ivtv.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 The cx23415 can do both encoding and decoding, the cx23416 can only do MPEG
10 encoding. Currently the only card featuring full decoding support is the
11 Hauppauge PVR-350.
25 Open Source driver implementation for video capture cards based on the
29 --------
31 * Hardware mpeg2 capture of broadcast video (and sound) via the tuner or
32 S-Video/Composite and audio line-in.
33 * Hardware mpeg2 capture of FM radio where hardware support exists
41 Additional features for the PVR-350 (CX23415 based)
[all …]
|
| D | imx.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 i.MX Video Capture Driver
7 ------------
10 handles the flow of image frames to and from capture devices and
13 For image capture, the IPU contains the following internal subunits:
15 - Image DMA Controller (IDMAC)
16 - Camera Serial Interface (CSI)
17 - Image Converter (IC)
18 - Sensor Multi-FIFO Controller (SMFC)
19 - Image Rotator (IRT)
[all …]
|
| D | vivid.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 This driver emulates video4linux hardware of various types: video capture, video
7 output, vbi capture and output, metadata capture and output, radio receivers and
8 transmitters, touch capture and a software defined radio receiver. In addition a
9 simple framebuffer device is available for testing capture and output overlays.
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
[all …]
|
| D | fimc.rst | 1 .. 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 …]
|
| D | raspberrypi-pisp-be.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Raspberry Pi PiSP Back End Memory-to-Memory ISP (pisp-be)
10 The PiSP Back End is a memory-to-memory Image Signal Processor (ISP) which reads
19 tessellation and the computation of low-level configuration parameters is
24 an image sensor through a MIPI CSI-2 compatible capture interface, storing them
29 The pisp-be driver
32 The Raspberry Pi PiSP Back End (pisp-be) driver is located under
33 drivers/media/platform/raspberrypi/pisp-be. It uses the `V4L2 API` to register
34 a number of video capture and output devices, the `V4L2 subdev API` to register
38 The media topology registered by the `pisp-be` driver is represented below:
[all …]
|
| D | imx7.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 i.MX7 Video Capture Driver
7 ------------
11 manipulation of the capture frames are less feature rich.
13 For image capture the i.MX7 has three units:
14 - CMOS Sensor Interface (CSI)
15 - Video Multiplexer
16 - MIPI CSI-2 Receiver
18 .. code-block:: none
20 MIPI Camera Input ---> MIPI CSI-2 --- > |\
[all …]
|
| D | rkisp1.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 rkisp1 and uses the Media-Controller API.
27 - RKISP1_V10: used at least in rk3288 and rk3399
28 - RKISP1_V11: declared in the original vendor code, but not used
29 - RKISP1_V12: used at least in rk3326 and px30
30 - RKISP1_V13: used at least in rk1808
36 .. kernel-figure:: rkisp1.dot
43 - rkisp1_mainpath: capture device for retrieving images, usually in higher
45 - rkisp1_selfpath: capture device for retrieving images.
46 - rkisp1_stats: a metadata capture device that sends statistics.
[all …]
|
| /Documentation/devicetree/bindings/counter/ |
| D | ti,am62-ecap-capture.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/counter/ti,am62-ecap-capture.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Texas Instruments Enhanced Capture (eCAP) Module
10 - Julien Panis <jpanis@baylibre.com>
13 The eCAP module resources can be used to capture timestamps
18 const: ti,am62-ecap-capture
29 clock-names:
32 power-domains:
[all …]
|
| /Documentation/sound/designs/ |
| D | control-names.rst | 8 ---------------
17 Capture one direction
19 Bypass Capture one direction
68 Headset Mic mic part of combined headset jack - 4-pin
70 Headphone Mic mic part of either/or - 3-pin headphone or mic
71 Line input only, use "Line Out" for output
79 Analog Loopback D/A -> A/D loopback
80 Digital Loopback playback -> capture loopback -
91 SPDIF output only
98 -----------------------
[all …]
|
| /Documentation/admin-guide/kdump/ |
| D | kdump.rst | 2 Documentation for Kdump - The kexec-based Crash Dumping Solution
11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
14 the reboot and is accessible to the dump-capture kernel.
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
47 passed to the dump-capture kernel through the elfcorehdr= boot
51 With the dump-capture kernel, you can access the memory image through
52 /proc/vmcore. This exports the dump as an ELF-format file that you can
55 options, e.g with '-d 31' it will only write out kernel data. Further,
[all …]
|
| /Documentation/devicetree/bindings/timer/ |
| D | renesas,rz-mtu3.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/timer/renesas,rz-mtu3.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Renesas RZ/G2L Multi-Function Timer Pulse Unit 3 (MTU3a)
10 - Biju Das <biju.das.jz@bp.renesas.com>
13 This hardware block consists of eight 16-bit timer channels and one
14 32-bit timer channel. It supports the following specifications:
15 - Pulse input/output: 28 lines max
16 - Pulse input 3 lines
[all …]
|
| /Documentation/sound/cards/ |
| D | mixart.rst | 13 The miXart8AES/EBU is the same with a add-on card that offers further
15 Furthermore the add-on card offers external clock synchronisation
23 Use the mixartloader that can be found in the alsa-tools package.
30 stereo analog capture 'pcm0c' and 1 stereo analog playback 'pcm0p' device.
35 -------
37 Sample rates : 8000 - 48000 Hz continuously
40 --------
47 Capture section in VERSION 0.1.0
48 -------
49 There is one substream per capture device. For instance only stereo
[all …]
|
| D | sb-live-mixer.rst | 19 (index 0) for a given card) allows to forward 48kHz, stereo, 16-bit
22 to 8 raw PCM devices operating at 48kHz, 16-bit little endian. It would
24 but the conversion routines exist only for stereo (2-channel streams)
34 functionality. Only the default built-in code in the ALSA driver is described
48 one-way three wire serial bus for digital sound by Philips Semiconductors
56 FX-bus
63 ---------------------------------------
64 This control is used to attenuate samples from left and right PCM FX-bus
69 ------------------------------------------------
70 This control is used to attenuate samples from left and right PCM FX-bus
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | fsl,ssi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Shengjiu Wang <shengjiu.wang@nxp.com>
13 Notes on fsl,playback-dma and fsl,capture-dma
14 On SOCs that have an SSI, specific DMA channels are hard-wired for playback
15 and capture. On the MPC8610, for example, SSI1 must use DMA channel 0 for
16 playback and DMA channel 1 for capture. SSI2 must use DMA channel 2 for
17 playback and DMA channel 3 for capture. The developer can choose which
18 DMA controller to use, but the channels themselves are hard-wired. The
[all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
4 .. _media-request-api:
12 the same pipeline to reconfigure and collaborate closely on a per-frame basis.
14 to specific frames (aka 'per-frame controls') in order to be used efficiently.
16 While the initial use-case was V4L2, it can be extended to other subsystems
20 it is, it is terribly inefficient: user-space would have to flush all activity
24 buffer queues since in practice only one buffer would be queued at a time.
28 specific buffers. This allows user-space to schedule several tasks ("requests")
34 -------------
37 subsystem-specific APIs to support request usage. At the Media Controller
[all …]
|