Home
last modified time | relevance | path

Searched full:capture (Results 1 – 25 of 227) sorted by relevance

12345678910

/Documentation/ABI/testing/
Dconfigfs-usb-gadget-uac28 c_chmask capture channel mask
9 c_srate list of capture sampling rates (comma-separated)
10 c_ssize capture sample size (bytes)
11 c_sync capture synchronization type
13 c_mute_present capture mute control enable
14 c_volume_present capture volume control enable
15 c_volume_min capture volume control min value
17 c_volume_max capture volume control max value
19 c_volume_res capture volume control resolution
34 for both capture and playback
Dconfigfs-usb-gadget-uac18 c_chmask capture channel mask
9 c_srate list of capture sampling rates (comma-separated)
10 c_ssize capture sample size (bytes)
11 c_mute_present capture mute control enable
12 c_volume_present capture volume control enable
13 c_volume_min capture volume control min value
15 c_volume_max capture volume control max value
17 c_volume_res capture volume control resolution
31 for both capture and playback
/Documentation/userspace-api/media/v4l/
Ddev-encoder.rst41 7. Given an ``OUTPUT`` buffer A, then A' represents a buffer on the ``CAPTURE``
70 Encoding -> Reset [ label = "VIDIOC_STREAMOFF(CAPTURE)" ];
74 Drain -> Stopped [ label = "All CAPTURE\nbuffers dequeued\nor\nVIDIOC_STREAMOFF(OUTPUT)" ];
75 Drain -> Reset [ label = "VIDIOC_STREAMOFF(CAPTURE)" ];
77 Reset -> Encoding [ label = "VIDIOC_STREAMON(CAPTURE)" ];
81 Stopped -> Reset [ label = "VIDIOC_STREAMOFF(CAPTURE)" ];
88 client may call :c:func:`VIDIOC_ENUM_FMT` on ``CAPTURE``.
96 * Only the formats supported for the format currently active on ``CAPTURE``
100 the client must first set that coded format on ``CAPTURE`` and then
114 ``CAPTURE``.
[all …]
Ddev-decoder.rst41 7. Given an ``OUTPUT`` buffer A, then A’ represents a buffer on the ``CAPTURE``
49 CAPTURE
54 into ``CAPTURE`` buffers.
79 encoders ``CAPTURE`` buffers must be returned by the encoder in decode order.
82 data resulting from the decode process; see ``CAPTURE``.
87 ``CAPTURE`` buffers must be returned by the decoder in display order.
171 node [shape = circle, label="Capture\nsetup"] CaptureSetup;
181 Initialization -> CaptureSetup [ label = "CAPTURE\nformat\nestablished" ];
183 CaptureSetup -> Stopped [ label = "CAPTURE\nbuffers\nready" ];
189 Decoding -> Stopped [ label = "VIDIOC_STREAMOFF(CAPTURE)" ];
[all …]
Ddev-stateless-decoder.rst42 irrespective of the format currently set on the ``CAPTURE`` queue.
49 :c:func:`VIDIOC_ENUM_FMT` on the ``CAPTURE`` queue.
57 before querying the ``CAPTURE`` queue. Failure to do so will result in the
90 Changing the ``OUTPUT`` format may change the currently set ``CAPTURE``
91 format. The driver will derive a new ``CAPTURE`` format from the
93 parameters, etc. If the client needs a specific ``CAPTURE`` format,
97 etc.) required by the ``OUTPUT`` format to enumerate the ``CAPTURE`` formats.
99 3. Call :c:func:`VIDIOC_G_FMT` for ``CAPTURE`` queue to get the format for the
105 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
129 4. *[optional]* Enumerate ``CAPTURE`` formats via :c:func:`VIDIOC_ENUM_FMT` on
[all …]
Ddev-capture.rst7 Video Capture Interface
10 Video capture devices sample an analog video signal and store the
11 digitized images in memory. Today nearly all devices can capture at full
13 capture process and move images from the driver into user space.
15 Conventionally V4L2 video capture devices are accessed through character
26 Devices supporting the video capture interface set the
32 (``V4L2_CAP_VIDEO_OVERLAY``) and the :ref:`raw VBI capture <raw-vbi>`
40 Video capture devices shall support :ref:`audio input <audio>`,
45 capture devices.
50 The result of a capture operation is determined by cropping and image
[all …]
Dvidioc-enum-fmt.rst66 (for video output devices) or be produced from (for video capture
177 - The hardware encoder supports setting the ``CAPTURE`` coded frame
180 also sets the ``CAPTURE`` coded frame interval to the same value.
181 If this flag is set, then the ``CAPTURE`` coded frame interval can be
184 a hint for reserving hardware encoder resources and the ``CAPTURE`` coded
194 colorspace. This flag is relevant only for capture devices.
195 The application can ask to configure the colorspace of the capture device
201 transfer function. This flag is relevant only for capture devices.
202 The application can ask to configure the transfer function of the capture
208 Y'CbCr encoding. This flag is relevant only for capture devices.
[all …]
Dvidioc-g-fmt.rst47 type. For example video capture devices use
51 the respective member of the ``fmt`` union. In case of video capture
106 capture and output devices.
110 capture and output devices that support the
118 - Raw VBI capture or output parameters. This is discussed in more
119 detail in :ref:`raw-vbi`. Used by raw VBI capture and output
123 - Sliced VBI capture or output parameters. See :ref:`sliced` for
124 details. Used by sliced VBI capture and output devices.
128 capture and output devices.
132 metadata capture devices.
Dvidioc-g-parm.rst38 Applications can request a different frame interval. The capture or
76 - ``capture``
77 - Parameters for capture devices, used when ``type`` is
229 .. flat-table:: Capture Parameters Flags
241 different mode from the regular motion video capture modes. In
244 - The driver may be able to capture higher resolutions than for
245 motion capture.
247 - The driver may support fewer pixel formats than motion capture
250 - The driver may capture and arithmetically combine multiple
254 - The driver may capture images in slices like a scanner in order
[all …]
/Documentation/admin-guide/kdump/
Dkdump.rst11 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
31 region just before rebooting into the dump-capture kernel.
45 passed to the dump-capture kernel through the elfcorehdr= boot
50 With the dump-capture kernel, you can access the memory image through
104 Build the system and dump-capture kernels
108 1) Build a separate custom dump-capture kernel for capturing the
[all …]
/Documentation/devicetree/bindings/sound/
Dmt8173-rt5650.txt10 - codec-capture : the subnode of rt5650 codec capture
11 Required codec-capture subnode properties:
12 - sound-dai: audio codec dai name on capture path
13 <&rt5650 0> : Default setting. Connect rt5650 I2S1 for capture. (dai_name = rt5645-aif1)
14 <&rt5650 1> : Connect rt5650 I2S2 for capture. (dai_name = rt5645-aif2)
27 codec-capture {
Dfsl,ssi.txt51 playback and capture to use different sample sizes and
60 - fsl,capture-dma: Phandle to a node for the DMA channel to use for
61 capture (recording) of audio. This is typically dictated
72 Notes on fsl,playback-dma and fsl,capture-dma:
75 and capture. On the MPC8610, for example, SSI1 must use DMA channel 0 for
76 playback and DMA channel 1 for capture. SSI2 must use DMA channel 2 for
77 playback and DMA channel 3 for capture. The developer can choose which
82 "fsl,playback-dma" and "fsl,capture-dma" must be marked as compatible with
/Documentation/admin-guide/media/
Dimx.rst3 i.MX Video Capture Driver
10 handles the flow of image frames to and from capture devices and
13 For image capture, the IPU contains the following internal subunits:
23 memory. Various dedicated DMA channels exist for both video capture and
31 The CSI is the backend capture unit that interfaces directly with
64 outside the IPU that are also involved in video capture on i.MX:
81 that correspond to the hardware video capture pipelines supported in
87 video capture interfaces using independent entities.
204 source pad is routed to a capture device node, with a node name of the
205 format "ipuX_csiY capture".
[all …]
Drkisp1.rst27 - rkisp1_mainpath: capture device for retrieving images, usually in higher
29 - rkisp1_selfpath: capture device for retrieving images.
30 - rkisp1_stats: a metadata capture device that sends statistics.
37 mainpath capture device.
39 selfpath capture device.
44 rkisp1_mainpath, rkisp1_selfpath - Frames Capture Video Nodes
46 Those are the `mainpath` and `selfpath` capture devices to capture frames.
48 The selfpath video device can capture YUV/RGB formats. Its input is YUV encoded
50 capture bayer formats.
51 The mainpath can capture both bayer and YUV formats but it is not able to
[all …]
Dimx7.rst3 i.MX7 Video Capture Driver
11 manipulation of the capture frames are less feature rich.
13 For image capture the i.MX7 has three units:
24 | U | ------> CSI ---> Capture
61 routed to a capture device node.
67 that access controls only from video device nodes, the capture device interfaces
69 can be accessed either directly from the subdev or from the active capture
71 sensor subdevs or from the active capture device.
77 CSI-2 receiver. The following example configures a video capture pipeline with
86 media-ctl -l "'csi':1 -> 'csi capture':0[1]"
[all …]
Dfimc.rst27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
56 viewfinder and still capture setup).
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
80 Camera capture subdevs
94 In typical use case there could be a following capture pipeline configuration:
103 The sysfs entry allows to instruct the capture node driver not to configure
[all …]
Divtv.rst25 Open Source driver implementation for video capture cards based on the
31 * Hardware mpeg2 capture of broadcast video (and sound) via the tuner or
33 * Hardware mpeg2 capture of FM radio where hardware support exists
96 /dev/video0 is listed as the 'base' encoding capture device so we have:
98 - /dev/video0 is the encoding capture device for the first card (card 0)
99 - /dev/video1 is the encoding capture device for the second card (card 1)
100 - /dev/video2 is the encoding capture device for the third card (card 2)
104 the card number to the base device number'. If you have other capture
113 The encoding capture device(s).
142 The raw audio capture device(s).
[all …]
Dvivid.rst6 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
35 - Raw and Sliced VBI capture and output support
38 - Capture and output overlay support
39 - Metadata capture and output support
40 - Touch capture support
[all …]
Dvimc.rst7 API. It has a capture device and three subdevices: sensor, debayer and scaler.
40 v4l2-ctl -z platform:vimc -d "RGB/YUV Capture" -v width=1920,height=1440
41 v4l2-ctl -z platform:vimc -d "Raw Capture 0" -v pixelformat=BA81
42 v4l2-ctl -z platform:vimc -d "Raw Capture 1" -v pixelformat=BA81
72 vimc-capture:
73 Exposes node /dev/videoX to allow userspace to capture the stream.
/Documentation/sound/designs/
Dcontrol-names.rst17 Capture one direction
19 Bypass Capture one direction
80 Digital Loopback playback -> capture loopback -
101 [Analogue|Digital] Capture Source
102 [Analogue|Digital] Capture Switch aka input gain switch
103 [Analogue|Digital] Capture Volume aka input gain volume
124 External Rate external capture rate
125 Capture Rate capture rate taken from external source
132 IEC958 [...] [Playback|Capture] Switch turn on/off the IEC958 interface
133 IEC958 [...] [Playback|Capture] Volume digital volume control
[all …]
/Documentation/sound/cards/
Dimg-spdif-in.rst8 * name='IEC958 Capture Mask',index=0
11 can be read using the 'IEC958 Capture Default' control.
13 * name='IEC958 Capture Default',index=0
16 is being received. The 'IEC958 Capture Mask' shows which bits can be read
29 will determine the single rate the block will capture. Else, the rate given to
30 hw_params will be ignored, and the block will attempt capture for each of the
38 This control returns the active capture rate, or 0 if a lock has not been
Dsb-live-mixer.rst89 ``name='Wave Capture Volume',index=0``, ``name='Wave Capture Switch',index=0``
93 The result is forwarded to the ADC capture FIFO (thus to the standard capture
102 ``name='Synth Capture Volume',index=0``, ``name='Synth Capture Switch',index=0``
106 The result is forwarded to the ADC capture FIFO (thus to the standard capture
116 ``name='Surround Capture Volume',index=0``, ``name='Surround Capture Switch',index=0``
120 The result is forwarded to the ADC capture FIFO (thus to the standard capture
146 ``name='AC97 Capture Volume',index=0``
149 of the AC97 codec. The result is forwarded to the ADC capture FIFO (thus to
150 the standard capture PCM device).
162 ``name='IEC958 TTL Capture Volume',index=0``
[all …]
Dmixart.rst30 stereo analog capture 'pcm0c' and 1 stereo analog playback 'pcm0p' device.
47 Capture section in VERSION 0.1.0
49 There is one substream per capture device. For instance only stereo
54 <Master> and <Master Capture>
55 analog volume control of playback and capture PCM.
56 <PCM 0-3> and <PCM Capture>
58 <AES 0-3> and <AES Capture>
/Documentation/userspace-api/media/drivers/
Dimx-uapi.rst4 i.MX Video Capture Driver
89 These controls will configure an input capture channel as the method
94 Input capture requires hardware support. A VSYNC signal must be routed
95 to one of the i.MX6 input capture channel pads.
97 V4L2_CID_IMX_FIM_ICAP_CHANNEL configures which i.MX6 input capture
101 input capture events. By default the input capture method is disabled
103 IRQ_TYPE_EDGE_FALLING, or IRQ_TYPE_EDGE_BOTH to enable input capture,
106 When input capture is disabled, frame intervals will be measured via
/Documentation/devicetree/bindings/pwm/
Dpwm-st.txt16 - clock-names: Valid entries are "pwm" and/or "capture".
19 - interrupts: IRQ for the Capture device
23 - st,capture-num-chan: Number of available Capture channels. Default is 0.
42 st,capture-num-chan = <2>;

12345678910