Searched full:capture (Results 1 – 25 of 281) sorted by relevance
12345678910>>...12
| /Documentation/ABI/testing/ |
| D | configfs-usb-gadget-uac2 | 8 c_chmask capture channel mask
9 c_srate list of capture sampling rates (comma-separated)
10 c_ssize capture sample size (bytes)
11 c_hs_bint capture bInterval for HS/SS (1-4: fixed, 0: auto)
12 c_sync capture synchronization type
14 c_mute_present capture mute control enable
15 c_volume_present capture volume control enable
16 c_volume_min capture volume control min value
18 c_volume_max capture volume control max value
20 c_volume_res capture volume control resolution
[all …]
|
| D | configfs-usb-gadget-uac1 | 8 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
37 c_it_name capture input terminal name
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-decoder.rst | 41 7. Given an ``OUTPUT`` buffer A, then A' represents a buffer on the ``CAPTURE``
49 CAPTURE
54 into ``CAPTURE`` buffers.
85 encoders ``CAPTURE`` buffers must be returned by the encoder in decode order.
88 data resulting from the decode process; see ``CAPTURE``.
93 ``CAPTURE`` buffers must be returned by the decoder in display order.
178 node [shape = circle, label="Capture\nsetup"] CaptureSetup;
188 Initialization -> CaptureSetup [ label = "CAPTURE\nformat\nestablished" ];
190 CaptureSetup -> Stopped [ label = "CAPTURE\nbuffers\nready" ];
196 Decoding -> Stopped [ label = "VIDIOC_STREAMOFF(CAPTURE)" ];
[all …]
|
| D | dev-encoder.rst | 41 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 …]
|
| D | dev-stateless-decoder.rst | 42 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 …]
|
| D | dev-capture.rst | 7 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 …]
|
| D | vidioc-enum-fmt.rst | 66 (for video output devices) or be produced from (for video capture
181 - The hardware encoder supports setting the ``CAPTURE`` coded frame
184 also sets the ``CAPTURE`` coded frame interval to the same value.
185 If this flag is set, then the ``CAPTURE`` coded frame interval can be
188 a hint for reserving hardware encoder resources and the ``CAPTURE`` coded
198 colorspace. This flag is relevant only for capture devices.
199 The application can ask to configure the colorspace of the capture device
205 transfer function. This flag is relevant only for capture devices.
206 The application can ask to configure the transfer function of the capture
212 Y'CbCr encoding. This flag is relevant only for capture devices.
[all …]
|
| D | dev-meta.rst | 11 frame capture parameters supplied by the image source or device specific
23 Device nodes supporting the metadata capture interface set the
26 ioctl. That flag means the device can capture metadata to memory. Similarly,
38 The metadata device uses the :ref:`format` ioctls to select the capture format.
50 Devices that capture metadata by line have the struct v4l2_fmtdesc
52 devices can typically also :ref:`capture image data <capture>`. This primarily
|
| D | vidioc-g-fmt.rst | 47 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.
|
| D | vidioc-g-parm.rst | 38 Applications can request a different frame interval. The capture or
76 - ``capture``
77 - Parameters for capture devices, used when ``type`` is
228 .. flat-table:: Capture Parameters Flags
240 different mode from the regular motion video capture modes. In
243 - The driver may be able to capture higher resolutions than for
244 motion capture.
246 - The driver may support fewer pixel formats than motion capture
249 - The driver may capture and arithmetically combine multiple
253 - The driver may capture images in slices like a scanner in order
[all …]
|
| /Documentation/devicetree/bindings/timer/ |
| D | renesas,rz-mtu3.yaml | 23 - Input capture function (noise filter setting available)
27 - Simultaneous clearing on compare match or input capture
122 - description: MTU0.TGRA input capture/compare match
123 - description: MTU0.TGRB input capture/compare match
124 - description: MTU0.TGRC input capture/compare match
125 - description: MTU0.TGRD input capture/compare match
129 - description: MTU1.TGRA input capture/compare match
130 - description: MTU1.TGRB input capture/compare match
133 - description: MTU2.TGRA input capture/compare match
134 - description: MTU2.TGRB input capture/compare match
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | mt8173-rt5650.txt | 10 - 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 {
|
| /Documentation/admin-guide/kdump/ |
| D | kdump.rst | 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
106 Build the system and dump-capture kernels
110 1) Build a separate custom dump-capture kernel for capturing the
113 2) Or use the system kernel binary itself as dump-capture kernel and there is
[all …]
|
| /Documentation/devicetree/bindings/counter/ |
| D | ti,am62-ecap-capture.yaml | 4 $id: http://devicetree.org/schemas/counter/ti,am62-ecap-capture.yaml#
7 title: Texas Instruments Enhanced Capture (eCAP) Module
13 The eCAP module resources can be used to capture timestamps
18 const: ti,am62-ecap-capture
53 capture@23100000 { /* eCAP in capture mode on am62x */
54 compatible = "ti,am62-ecap-capture";
|
| /Documentation/admin-guide/media/ |
| D | imx.rst | 3 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 …]
|
| D | imx7.rst | 3 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 …]
|
| D | fimc.rst | 27 - 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 …]
|
| D | rkisp1.rst | 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.
53 mainpath capture device.
55 selfpath capture device.
60 rkisp1_mainpath, rkisp1_selfpath - Frames Capture Video Nodes
62 Those are the `mainpath` and `selfpath` capture devices to capture frames.
64 The selfpath video device can capture YUV/RGB formats. Its input is YUV encoded
66 capture bayer formats.
67 The mainpath can capture both bayer and YUV formats but it is not able to
[all …]
|
| 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
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 …]
|
| D | raspberrypi-pisp-be.rst | 24 an image sensor through a MIPI CSI-2 compatible capture interface, storing them
34 a number of video capture and output devices, the `V4L2 subdev API` to register
53 - pispbe-output0: first capture device for processed images.
54 - pispbe-output1: second capture device for processed images.
55 - pispbe-tdn_output: capture device for temporal denoise.
56 - pispbe-stitch_output: capture device for image stitching (HDR).
71 capture video device. Userspace is responsible for maintaining queues on both
88 The two capture devices write to memory the pixel data as processed by the ISP.
106 is the image format on the output and capture video devices for validation of
|
| /Documentation/sound/designs/ |
| D | control-names.rst | 17 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/ |
| D | img-spdif-in.rst | 8 * 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
|
| /Documentation/gpu/rfc/ |
| D | i915_small_bar.rst | 37 Error Capture restrictions
39 With error capture we have two new restrictions:
41 1) Error capture is best effort on small BAR systems; if the pages are not
42 CPU accessible, at the time of capture, then the kernel is free to skip
43 trying to capture them.
45 2) On discrete and newer integrated platforms we now reject error capture
47 error capture, when for example something is not currently CPU accessible.
|
| /Documentation/userspace-api/media/drivers/ |
| D | imx-uapi.rst | 4 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/ |
| D | pwm-st.txt | 16 - 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>>...12